Unable to upgrade to Windows 10 build 1803 - Error 0xC19000101 - 0x4001E

%3CLINGO-SUB%20id%3D%22lingo-sub-237846%22%20slang%3D%22en-US%22%3EUnable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-237846%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20afternoon%20all%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20support%20referred%20me%20to%20the%20community%20because%20after%203%20remote%20support%20sessions%20not%20one%20support%20agent%20was%20able%20to%20resolve%20this%20issue.%3C%2FP%3E%3CP%3EI%20am%20experiencing%20problems%20updating%20from%20Windows%2010%20build%201709%20to%20Windows%2010%20build%201803.%3C%2FP%3E%3CP%3EThe%20following%20attempts%20have%20failed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*%20Using%20Windows%20Update%3C%2FP%3E%3CP%3E*%20Using%20the%20Windows%2010%20Upgrade%20Assistant%3C%2FP%3E%3CP%3E*Using%20the%20official%20Media%20Creation%20Tool%3C%2FP%3E%3CP%3E*Using%20the%20Official%20Microsoft%20Windows%2010%20ISO%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESFC%20reports%20no%20system%20file%20integrity%20violations.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESystem%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EASUS%20Sabertooth%20X99%20latest%203902%20BIOS%3C%2FP%3E%3CP%3EIntel%20core%20i7%20i5930k%3C%2FP%3E%3CP%3E16GB%20of%20RAM%3C%2FP%3E%3CP%3ESamsung%20SM951%20SSD%3C%2FP%3E%3CP%3EeVGA%20Geforce%20980Ti%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESetupDiag%20log%20files%20are%20attached.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20help%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJohn%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278781%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278781%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Morning%20all%3C%2FP%3E%3CP%3EI%20finally%20managed%20to%20update%20to%20Windows%2010%20v1803%20I%20did%20not%20have%20to%20lose%20any%20of%20my%20apps.%3C%2FP%3E%3CP%3EWith%20many%20thanks%20to%20the%20author%20of%20this%20blog%20here%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fjukkakohtala.blogspot.com%2F2018%2F08%2Fwindows-1709-upgrade-to-windows-1803.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fjukkakohtala.blogspot.com%2F2018%2F08%2Fwindows-1709-upgrade-to-windows-1803.html%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20followed%20his%20steps%20to%20import%20the%20new%20provisioning%20registry%20key%20and%20child%20objects%20and%20this%20resolved%20the%20issue.%3C%2FP%3E%3CP%3ESuch%20a%20shame%20that%20Microsoft%20themselves%20were%20unable%20to%20fix%20this%20with%20me%20months%20ago.%3C%2FP%3E%3CP%3EJohn%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238444%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238444%22%20slang%3D%22en-US%22%3E%3CP%3EOk!%3C%2FP%3E%3CP%3EGood%20luck!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238191%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238191%22%20slang%3D%22en-US%22%3E%3CP%3ESecureBoot%20and%20UEFI%20are%20not%20a%20must%20for%20realiable%20OS%20functioning.%20SecureBoot%20is%20for%20added%20OS%20security%2C%20which%20you%20probably%20won't%20ever%20need.%20UEFI%20is%20just%20more%20common%20and%20supported%20today%20and%20based%20on%20other%20components%20it%20can%20be%20needed%20sometimes%20for%20BitLocker%20encryption%20and%20similar%20features.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%20CCleaner%20after%20OS%20install%20is%20an%20overkill%20(personally%20i%20don't%20like%20all%20these%20%22helping%22%20tools%20at%20all%2C%20not%20needed%20fluff).%20Installing%20still%20rather%20fresh%201803%2C%20one%20Cumulative%20update%20(August)%20and%20a%20few%20other%20updates%20released%20since%20May%20should%20be%20quick%20and%20system's%20registry%20should%20be%20ok%20(Windows%20has%20already%20advanced%20a%20lot%20to%20make%20registry%20work%20ok%20without%20additional%20tweaks).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20agree%20about%20MS%20not%20being%20able%20to%20test%20every%20configuration%20though.%20They%20now%20collect%20lots%20of%20telemetry%20and%20still%20fail%20sometimes%20because%20of%20some%20obscure%20configs%20and%20also%20get%20complains%20about%20privacy.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238111%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238111%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%3CSPAN%3E%22Pretty%20sure%20Microsoft%20do%20not%20test%20these%20updates%20very%20rigorously%22.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMicrosoft%20can't%20behind%20all%20computers%20of%20world%20and%20all%20configurations.%20It%20is%20possible%20that%20you%20have%20some%20programs%20(e.g%20Antivirus%20tier)%20that%20corrupt%20your%20Upgrade.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%20in%20BIOS%2C%20enable%20'SecureBoot'%20and%20'UEFI'.%3C%2FP%3E%3CP%3EM%3CSPAN%3Eake%20a%20clean%20install%2C%20then%20leave%20your%20system%20work%20only%20for%20all%20Updates%20to%20do%20before%20using%20your%20PC.%20This%20can%20take%20some%20time.%20For%20my%20part%2C%20I%20leave%20my%20PC%20quiet%20at%20least%20a%20journey.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EAfter%20all%20Updates%20and%20Upgrade%20are%20installed.%3CSPAN%3E%20Install%20CCleaner%20(free%20version%20enough%2C%20disable%20the%20monitoring)%20and%20perform%20a%20scan%20on%20your%20registry%2C%20delete%20all%20keys%20obsoletes%20without%20saving.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ERestart%20your%20PC%20so%20your%20registry%20get%20up%20to%20Update.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ENext%2C%20you%20have%20to%20a%20folder%20%22windows.old%22%20here%20%22C%3A%5Cwindows.old%22%20that%20you%20can%20delete%20with%20the%20tool%20%22Disk%20Cleanup%22%20of%20Windows.%20Next%2C%20and%20it%20is%20very%20important%2C%20c%3CSPAN%3Ereate%20a%20%22Repair%20CD%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EGood%20luck!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238083%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238083%22%20slang%3D%22en-US%22%3E%3CP%3EBefore%20doing%20clean%20reinstall%20you%20can%20try%20Reset%20PC%20(leaving%20documents%20in%20place)%26nbsp%3B%20Although%20you%20would%20lose%20settings%20and%20win32%20apps%2C%20so%20it%20is%20close%20to%20reinstall.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238004%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238004%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Setup%20process%20failed%20again!%3C%2FP%3E%3CP%3EVery%20frustrating%20that%20this%20is%20now%20the%2010th%20or%2011th%20time%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPretty%20sure%20Microsoft%20do%20not%20test%20these%20updates%20very%20rigorously.%3C%2FP%3E%3CP%3EI%20had%20no%20problem%20whatsoever%20upgrading%20from%20the%20previous%20builds%20up%20to%201709%20via%20Windows%20update%20so%20surely%20something%20is%20fundamentally%20different%20in%20the%20process%20for%201803%20that%20renders%20it%20very%26nbsp%3B%3CEM%3Efussy%26nbsp%3B%3C%2FEM%3Ewith%20certain%20system%20configurations.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20help%2C%20at%20my%20wits%20end.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJohn%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-237993%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-237993%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Oleg%20K%3C%2FP%3E%3CP%3EI%20have%20given%20that%20a%20try%2C%20but%20now%20the%20update%20doe%20snot%20show%20as%20available%20within%26nbsp%3B%3CSTRONG%3ESettings%20%26gt%3B%20Update%20%26amp%3B%20Security%20%26gt%3B%20Windows%20Update%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPreviously%20the%20update%20would%20show%20as%20available%20%2C%20complete%20the%20first%20install%20routine%20in%20Windows%2C%20reboot%20install%20up%20to%2050%25%20%2C%20reboot%20then%20install%20up%20to%2075%25%20reboot%20and%20then%20install%20up%20to%2086%25%20%2C%20reboot%20and%20then%20immediately%20come%20up%20with%20the%20dreaded%20%22restoring%20previous%20version%20of%20Windows%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESadly%20the%20error%20code%20does%20not%20really%20give%20a%20lot%20to%20go%20on.%20Microsoft%20hinted%20that%20it%20could%20be%20because%20ASUS%20have%20not%20released%20any%20new%20drivers%20for%20my%20Sabertooth%20X99%20for%20the%20new%20version%20of%20Windows.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20I%20am%20sure%20(after%26nbsp%3B%20a%20quick%20google%20search)%20that%20other%20users%20of%20this%20motherboard%20are%20happily%20using%20Windows%2010%201803.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%20I%20have%20updated%20the%20firmware%20on%20my%20USB%203.1%20controller%20and%20installed%20the%20latest%20drivers%2C%20hopefully%20this%20will%20help%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20not%2C%20other%20than%20a%20clean%20install%20have%20you%20got%20any%20other%20suggestions%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJohn%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-237916%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20upgrade%20to%20Windows%2010%20build%201803%20-%20Error%200xC19000101%20-%200x4001E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-237916%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20try%20sropping%20Windows%20Update%20service%2C%20deleting%20C%3A%5CWindows%5CSoftwareDistribution%20folder%2C%20running%20the%20service%20again%20and%20checking%20for%20updates.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Good afternoon all

 

Microsoft support referred me to the community because after 3 remote support sessions not one support agent was able to resolve this issue.

I am experiencing problems updating from Windows 10 build 1709 to Windows 10 build 1803.

The following attempts have failed.

 

* Using Windows Update

* Using the Windows 10 Upgrade Assistant

*Using the official Media Creation Tool

*Using the Official Microsoft Windows 10 ISO

 

SFC reports no system file integrity violations.

 

System:

 

ASUS Sabertooth X99 latest 3902 BIOS

Intel core i7 i5930k

16GB of RAM

Samsung SM951 SSD

eVGA Geforce 980Ti

 

SetupDiag log files are attached.

 

Please help

 

John

 

 

8 Replies
Highlighted

You can try sropping Windows Update service, deleting C:\Windows\SoftwareDistribution folder, running the service again and checking for updates.

Highlighted

Thank you Oleg K

I have given that a try, but now the update doe snot show as available within Settings > Update & Security > Windows Update

 

Previously the update would show as available , complete the first install routine in Windows, reboot install up to 50% , reboot then install up to 75% reboot and then install up to 86% , reboot and then immediately come up with the dreaded "restoring previous version of Windows"

 

Sadly the error code does not really give a lot to go on. Microsoft hinted that it could be because ASUS have not released any new drivers for my Sabertooth X99 for the new version of Windows.

 

However I am sure (after  a quick google search) that other users of this motherboard are happily using Windows 10 1803.

 

Today I have updated the firmware on my USB 3.1 controller and installed the latest drivers, hopefully this will help?

 

If not, other than a clean install have you got any other suggestions?

 

Thanks

 

John

Highlighted

The Setup process failed again!

Very frustrating that this is now the 10th or 11th time now.

 

Pretty sure Microsoft do not test these updates very rigorously.

I had no problem whatsoever upgrading from the previous builds up to 1709 via Windows update so surely something is fundamentally different in the process for 1803 that renders it very fussy with certain system configurations.

 

Please help, at my wits end.

 

John

Highlighted

Before doing clean reinstall you can try Reset PC (leaving documents in place)  Although you would lose settings and win32 apps, so it is close to reinstall.

Highlighted

Hi,

"Pretty sure Microsoft do not test these updates very rigorously".

 

Microsoft can't behind all computers of world and all configurations. It is possible that you have some programs (e.g Antivirus tier) that corrupt your Upgrade.

 

First in BIOS, enable 'SecureBoot' and 'UEFI'.

Make a clean install, then leave your system work only for all Updates to do before using your PC. This can take some time. For my part, I leave my PC quiet at least a journey.

After all Updates and Upgrade are installed. Install CCleaner (free version enough, disable the monitoring) and perform a scan on your registry, delete all keys obsoletes without saving.

Restart your PC so your registry get up to Update.

Next, you have to a folder "windows.old" here "C:\windows.old" that you can delete with the tool "Disk Cleanup" of Windows. Next, and it is very important, create a "Repair CD".

 

Good luck!

Highlighted

SecureBoot and UEFI are not a must for realiable OS functioning. SecureBoot is for added OS security, which you probably won't ever need. UEFI is just more common and supported today and based on other components it can be needed sometimes for BitLocker encryption and similar features.

 

Running CCleaner after OS install is an overkill (personally i don't like all these "helping" tools at all, not needed fluff). Installing still rather fresh 1803, one Cumulative update (August) and a few other updates released since May should be quick and system's registry should be ok (Windows has already advanced a lot to make registry work ok without additional tweaks).

 

I would agree about MS not being able to test every configuration though. They now collect lots of telemetry and still fail sometimes because of some obscure configs and also get complains about privacy.

Highlighted
Highlighted

Good Morning all

I finally managed to update to Windows 10 v1803 I did not have to lose any of my apps.

With many thanks to the author of this blog here:

http://jukkakohtala.blogspot.com/2018/08/windows-1709-upgrade-to-windows-1803.html

I followed his steps to import the new provisioning registry key and child objects and this resolved the issue.

Such a shame that Microsoft themselves were unable to fix this with me months ago.

John