Windows 10: Upgrade to 1803 version fails with 0xc1900101-0x30017 error

Windows driver verifer is a tool that produces BSOD.
Each time there is a BSOD you will need to recover from BSOD and turn off the tool.
In order to turn off the tool you will need to use the windows advanced troubleshooting menu.
There are methods to turn off and recover from using the tool.
Once you have turned off the tool you then will be able to return to the desktop.
On the desktop you will then uninstall misbehaving drivers.
You can keep using the tool to find more misbehaving drivers.
The custom test settings must be reset to turn on the tool to find the next misbehaving driver.
Then the next misbehaving driver will be uninstalled.
Whenever there is a misbehaving driver you have choices: uninstall and reinstall immediately, uninstall and do not reinstall, or uninstall and reinstall after all misbehaving drivers are uninstalled.
Once all misbehaving drivers are fixed you will then use the tool under typical conditions to check again for misbehaving drivers.
So there is a testing period while only using windows driver verifier and there is a testing period after drivers were fixed while using the computer under typical use.
There were two links that were posted. One is a Microsoft link and has approximately 19 customized simultaneous tests. The other is Ten Forums and has 3 customized tests. You will start with the Microsoft method and if there are problems you can move to the Ten Forums method. Then you will add 3 drivers every 1 - 2 hours so that all drivers are exposed to all 19 tests. Some tests may need to added while others not used depending upon computer sluggishness and problems booting.

Another method to get to the Windows advanced troubleshooting menu is to hold down the shift key while clicking reset on the power settings.

Before using Windows driver verifier you must:
1) Make a brand new restore point
2) Make sure that you have files backed up to another drive or to the cloud
3) Make sure that you have a backup image using Macrium

These are the multiple layers of protection for the files.

And before using the tool you must understand how to turn it off or recover from using the tool.

Once you are comfortable with the above you can turn on the tool.
If there are no BSOD then it will be easy to use the tool unless there is computer sluggishness or slow boot.
It there are BSOD then you must turn off or recover from using the tool, then fix the misbehaving driver, then restart the tool to find the next misbehaving driver.

My ComputerYou need to have JavaScript enabled so that you can use this ...

Made the mistake of practising the advanced cmd commands and had to do a restart. Lesson learned. lol

You will start with the Microsoft method and if there are problems you can move to the Ten Forums method. Then you will add 3 drivers every 1 - 2 hours so that all drivers are exposed to all 19 tests.

Sorry to be bothering you again with this. You say, in the 10Forums test, all drivers need to be exposed to all 19 tests 3 drivers at a time but you also only get to pick 3 tests at a time, is that correct? But there's no mention of what 3 tests to pick (other than the ones already checked) and in what order.

Not trying to play clever here , say I first pick the three tests already checked, then test all drivers thrown 3 at a time. When done choose a different set of three tests and repeat the process until all tests are accounted for?

That's a minimum of 6*(no of drivers /3) at 1-2 hrs per 3 driver set. Hope I'm right. Again only for my understanding lol

Some tests may need to added while others not used depending upon computer sluggishness and problems booting.

How does one know what tests to pick or not depending upon computer sluggishness?

My ComputerYou need to have JavaScript enabled so that you can use this ...

All non-Microsoft drivers will be tested simultaneously.
The tests that are used while stressing the drivers can be customized.
You will start with the Microsoft settings.
This is approximately 19 simultaneous tests.
If there are problems you will start again with the 3 customized tests displayed in the Ten Forums link.
Then throughout the testing you will maintain these 3 test and will be adding or removing others.
The goal is to perform the best testing and the more simultaneous tests the better the testing.
So again start with the Microsoft customized settings.
Make sure that you understand how to turn off or recover from using the tool before turning it on.
Using system restore often leads to a loss of the dump file and little progress is made in the troubleshooting.
Using startup options > restart > select #6 safe mode with command prompt > type: verifier /reset is the optimal method to turn off the tool. The other methods are backup alternatives.

My ComputerYou need to have JavaScript enabled so that you can use this ...

When using Windows driver verifier it has customized settings.
Testing methods impact test results.
So when using the tool it depends on how the testing was performed.
Ideally you can run all tests simultaneously.
If there is too much computer sluggishness or if the boots are extremely slow then the customized test settings need to be modified.

My ComputerYou need to have JavaScript enabled so that you can use this ...

Made my first Driver Verifer attempt. It BSODed right away and the % counter went rather quickly to 100%. But there was no mention of the actual driver causing the crash. Tried stopping the verifier via CMD (both commands) and Disable driver signature - didn't work . It repeatedly crashed. Was worried I'd have to do a restore but could finally reset the verifier by booting into safe mode>CMD>Verifier>Delete settings.

As expected the rogue driver seems to be LUMDriver.sys as found from Whocrashedme (thanks to @bbinnard). I"ll leave you to do the investigation. The crash dump also contains references to older crashes. Maybe you can shed some light on them too.

The concerned software was CATIA which I have since uniinstalled. But the driver itself had to be manually removed in safemode. I ran the verifier again. This time it's Intel HD graphics driver that caused the crash. The logs are below. Not sure what would happen if I unistalled that . So, I'll wait for your advice. Can't seem to find any updates either through auto update or their site.

Can I just go ahead and remove the driver and continue with the Verifier to see what's next. Or would it cause unintended behavior. Also, could this have played a part in the upgrade failure? It doesn't show up in the logs right?

Trying to update an existing Win10 1703 to 1709. It fails consistenly with the following error messages:
=======================
We couldn't install Windows 10
We've set your PC back to the way it was right before you started installing Windows...

Windows 10 1511 will not update to 1607 by any method. Updates always complete to 100% then revert. Computer is a Dell Vostro 1720.
Background: The computer never appeared to update automatically, but there was never any error code. I tried to...

I have had 4 failures attempting to upgrade my Dell Inspiron 660s to Windows 10. I have successfully updated my Optiplex 380 and my Inspiron 1545. I mention this because all three machines were running Windows 7 Home Premium, all were up to the...

I am running Samsung Series 5 AIO DP500A2D-K01UB PC running Winows 10 TP build 9841.
I could not install lastest Windows 10 TP build 9926.
Upgrading itself appeared to work fine. Upon reboot, I had no display after setting up 100%. After several...

About Us
Windows 10 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 10" and related materials are trademarks of Microsoft Corp.