Windows 10 update 1803 error loop at 0xc1900101

Question

Yesterday I wanted to install the current large update 1803 on my Windows 10. The system is a pretty vanilla Windows 10 Pro that had been freshly set up just recently, all updates had been installed, all device drivers are present and there's no error or exclamation mark in the device manager. The PC is quite decent hardware (MSI X99A SLI PLUS Board, Intel 5820k, MSI Geforce GTX970, 32GB RAM, Samsung Pro 950 NVMe SSD). There's no additional or "exotic" hardware attached to it (other than generic USB mouse and keyboard).

When I start the update, it goes on until Windows wants to reboot. When it comes up again, the OS does not start or show anything other than a bright blue screen. Not the "oldschool" BSOD bluescreen blue, but some kind of light blue. No text, no mouse cursor. In situations like these, I usually press Num a few times to check if the LED on the keyboard still reacts, and it does. The harddrive is idle.

I also tried to reconnect my monitor (HDMI) and tried to switch the screen configuration (with Windows-P) because I thought that the OS might have gone into some ill-configured dual screen and there's just nothing to see on the screen that I got, but that did not help eiter.

I let it sit there like that for more than two hours but nothing happened, so I pressed CTRL-ALT-DEL and the system restarted.

Back up, the OS was back at 1709 and gave me the error 0xc1900101 in the update history. Now the system constantly wants to reinstall the update, which fails over and over again.

I have no clue what to do. The system used to work flawlessly. How can I resolve the issue and find out what is wrong?

Solution 1

Pause the updates for now You can do that in "Advanced options" in Updates section of settings

I read that the initial update of 1803 is very buggy and a much more stable version of 1803 will be released on 8th-May(today) so when the updates resume after 7 days(pause) you should be able to update to somewhat better version of 1803 update

edit: yes it is sad that these issues are there in windows, i think these are a issue of flexibility and variety available in windows and also lack of unified central framework/language, i dont know if framework is the right word but you get the idea.I think the recent updates and features hint that they are trying to make windows like Android or Mac OS in terms of stability but it is very far from the final thing.

Solution 2

It can also be that you need to go into the BIOS (in Advanced under chipset for my BIOS) and disable the Intel VT-D virtualization technology.

Comments

[magicandre1981]

"A result code of 0xC1900101 is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue. " use SetupDiag to analyze the cause

[Rob]

Thanks. Unfortunately " SetupDiag was unable to match to any known failure signatures.".

[magicandre1981]

analyze the log on your own: docs.microsoft.com/en-us/windows/deployment/upgrade/…

[Rob]

Thanks for the hint. I think I tried to pause updates (not at home atm), but they still showed up every day.. guess I'll just wait a few days and check again.

[Tinted]

oh, lol, i did not knew that windows updates are this persistent.I dont get that many problems so i dont worry about updates.The problems i get are because of the changes i make and i know exactly what is wrong and i fix it right away.

[fixer1234]

This is a long commentary that basically relates your own problem and says Brian Zumbahlen's answer worked for you. As a Q&A site rather than a forum, the intention is that each answer provide a solution to the original question that has not already been contributed.