Upgrade to 1803 version fails with 0xc1900101-0x30017 error

The Windows upgrade failure code is related to driver problems.
Creating a stable computer environment is useful whether there is or is not an upgrade failure.
Once there are no more problematic drivers the computer will be better tuned up.
If there are any drivers that are problematic for the upgrade they may have been removed or replaced to permit the upgrade.
If there is a driver that is not misbehaving but is incompatible with the upgrade that should be able to be identified in the Panther logs after a recent failed upgrade.

Plan to run the memtest86+ when your computer requirements are reduced or when you plan another activity. This way the testing can be performed while sleeping and participating in other activities.

For Windows driver verifier the troubleshooting can be done for the next hour. Then I can continue the troubleshooting with you later this evening if you are available.

For all misbehaving drivers > use the Dell website to find the Dell tested drivers.
If Dell tested drivers are not available then use the component manufacturer website.
For all drivers then perform Windows updates to have the most up to date version.

The Windows upgrade failure code is related to driver problems.
Creating a stable computer environment is useful whether there is or is not an upgrade failure.
Once there are no more problematic drivers the computer will be better tuned up.
If there are any drivers that are problematic for the upgrade they may have been removed or replaced to permit the upgrade.

I do understand and very much appreciate this approach.

For Windows driver verifier the troubleshooting can be done for the next hour. Then I can continue the troubleshooting with you later this evening if you are available.

Actually, it's well past midnight here. So, would it be ok if I ran the memory test now and catch up with you when I'm done with it by tomorrow. We can then continue with the Driver verifier (when you're free) and do this:

For all misbehaving drivers > use the Dell website to find the Dell tested drivers.
If Dell tested drivers are not available then use the component manufacturer website.
For all drivers then perform Windows updates to have the most up to date version.

The Memtest86+ version 5.01 testing takes approximately 1 -2 hours /GB RAM.
The testing must be continuous.
The testing can be started anytime.
Plan to restart Windows driver verifier in 24 to 48 hours.
(It's 4:45 PM here so somehow we will figure out how to hook up for the debugging and continued troubleshooting.

That should be fine. It's not a must that you're available when I 'm doing the verifier. I'll post the logs as soon as I 'm done with verifier and wait for your response, as usual. I'll also try to get the most recent but one Dell drivers for all the misbehaving ones.

Thanks again

You are welcome.
Using Whocrashed analyze will display many misbehaving drivers.
The tool that we use (Windbg) enables us to run commands on the mini and memory dump files and to find drivers missed by Whocrashed or Bluescreenview.

I see. I do have the bluescreen view but never found it much useful since it only shows the driver name and evry thing else is in alien language.

Lol. Yeah lots of things in alien language.
Before I learned Windbg I had used both Whocrashed and Bluescreenview.
Sometimes one had info that is missed by the other.
Whocrashed has a feature for creating test dumps which is used in computer environments that BSOD and don't produce dump files.

Analyzing dumps can be quite daunting for the uninitiated non computer folks like me unless it's in plain English or has some semblance of it.:)

It takes time to learn the methodology.
Sometimes the displayed analyze driver is misleading and a deeper debugging needs to be performed.
Other times multiple mini dumps are needed to better appreciate the underlying problems.
And other times the mini dumps do not display misbehaving drivers and memory dumps need to be debugged.
Also at times malfunctioning hardware produce BSOD and there are no misbehaving drivers to fix.

That's true. But it's unfortunate that MS and their like expect the end user to do all the debugging when it's their responsibility to ensure rogue elements are detected prior to initiating major upgrades like they did with the GWX application back during release time. And then alert the user with suitable notifications regarding whatever that might interfere with the upgrade.
Moreover, the whole uninstallion process needs a rethink. An uninstall should do just that: remove all traces and not leave remnants be it in the registry or the driver dir or wherever else that's critical. As of now evry install /unistall tends to pile up unwanted electronic garbage. Or, at least flag them to be not used under any circumstances, if not remove them completely.

I think I'll get started with the memory test now.It's nearly 4 AM lol