This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Windows 10 1803 update gives this message 0xc1900101. Then windows update starts the download again.
Then it's message 0x80070005.
How to escape from this.Win10 pro, 1709
*Modified title for accuracy*
*Original title: Windows 10 1803 update fails with message 0xc1900101.*
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hello,
0xC1900101 is generic error code and points to driver incompatibility while you opt to upgrade. You need to read the dialog, which likely came before this error message. There should be additional information with the detail. The dialog will tell you what devices are having a problem. That is the one you need to get a new driver for.
Once you fixed the driver(s) mentioned with detail, the error will no longer persist.
Hope this helps!
NO NO PLEASE DON'T GET A MAC PLEASE NO!
Good riddance. Please go bung up the Apple message boards and stay out of this one.
I have this error also 0xc1900101, I pressed the pause update for 35 days. Should be enough time to order a mac book pro.
this kind of trouble happen every damn time windows updates itself.
first update throttle my upload speed to 1mbps, i recovered
then second update the same thing happen, plus this 0xc1900101 error, now i can't recover.
i hope the man responsible to this get run over by bus, rushed to the hospital in time, and suffer the slow death because the device that needs to save him get compulsory updates for as long as it can get him killed.
Well, both problems happened because window itself cannot "take charge" to install the supposedly essential drivers, 1st time recover i've lost my previous windows image, but fixed 2/4 updates that needs to be done (the synapse driver and the antivirus thing)
after recover, i update the windows again, in hope for some of my driver settings get reset and fix (ethernet connection get throttled to 1mbps upload) but no, it doesnt fix the problem, i plan to reset my while pc now.... Dang ! The recover image is gone ! And i have no more windows 10 dvd lying around...
Tested other stuff, wifi is okay, file transfer to my NAS also in gigabit speed, that means the upload problem could be driver base. I dig up my driver cd, nope, nothing different. Download latest driver from the vendor, nope, it's the same authorization problem.... Until i found out at the corner on the driver webpage there is a specific 1803 driver.... Gosh... Windows updates really tests me my patience on every major updates.
KaseyChang,
Unless you use or create virtual machines or do resource sharing over the network, e.g. using a desktop with its more powerful processor to compile video over the network while working and doing the physical editing from a less powerful laptop, you don't and won't need the Intel Virtualization Technology feature turned back on.
Also, it's not just Dell computers with this issue; I built mine from all individual retail parts, so there's not a Dell, HP, or similar prefab component in my system. Hopefully others will see these posts and give it a whirl before trying that Russian novel sized solution above, lol.
Dell XPS 17 L series laptop. 1803 installs, reboots, then froze and shuts down (auto-power off) during the 2nd reboot.
Upon turning on, Windows rolled back the 1803 install, then we're back where we started.
Came here, learned that on the Dell's I need to turn off the virtualization. So went into the BIOS and turned it off. Then restarted. Forced the 1803 update to install. Took almost an hour, but that's all done. I didn't bother turning the virtualization thing back on.
S
