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!
Been going through this with multiple PCs w/varying configurations ever since Mocrosoft's feature updates have become a thing, it's getting downright tiring now especially when the fail rate for me has been in the 90% range. Since 1987 haven't "fresh installed" the OS on so many computers, so much for advancement in technology... I'd be rich if we could recoup the costs associated with the hours/days spent going the motions in attempts to resolve. A means to suspend feature updates indefinitely would be nice yet doubt that will be an option if MS has their way. As with many others here were on our way to dumping Windows 10 altogether, already have in some instances been using Linux/Mac OS and/or, reverting some of my computers to Win7. Maybe one day MS will figure it out yet doubtful if the past three years are any indication.
I tried all the suggestions in this and other threads without success in updating a VM (virtual machine) with W10 to 1803. In my mind I am furious. Why must we, the end-users try all these tricks to let MS install an update ??!? Surely they should cater for this and their software should automatically sort out the crap !
I tried all the suggestions in this and other threads without success in updating a VM (virtual machine) with W10 to 1803.
In my case the problem that caused the failing Update was a network share, where I did not save the credentials.
After removing the network share the update/upgrade 1803 worked flawlessly.
I decided to bite the bullet and do a clean install; this worked. I will find out whether the next major update will have the same problem or that I escaped from this Windows Update catch 22.
My PC with the 1803 problem only does one thing: play music and send it to a receiver via the HDMI port. So I had very little to reinstall.
But if one has a lot installed this is an unacceptable workaround. It is almost a "Car runs out of gas, replace the engine" type of solution. Microsoft should clean up its act on Windows update.
One thing that comes to mind is better error reporting that points out more than the error code.
