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!
Good going, glad that turned out well for you. Especially good to hear a manufacturer unsupported machine still might work with 1803. Excellent staying power on your part.
Good luck, & keep us informed.
Also after a few (4-5) failed attempts while attempting to update from 1703 to 1803 in an HP 530 Notebook PC I've done the following adjustments based on this and a couple other similar threads:
After the adjustments, the following attempt worked. Coincidence? Maybe, maybe not!
I was preparing myself to crawl through the extensive/hard to interpret CBS logs but (fortunately) it wasn't necessary.
Good luck for those still having problems and hope this helps!
P.S.: HP doesn't formally support this model in Windows 10 (not included in HP Products Tested with Windows 10) but my preliminary testing says it works reasonably well (mind it's a 2012 laptop).
If the error is : 0xC1900101-0x4001Ethen the problem is probably not with the drivers but Windows 10 provisioning. I finally got mine updated after months of several failed updates. I hope this helps at least some of you. Microsoft should figure out why their provisioning gets broken and how to bypass that in setup.
At least the utility allows one to "stay" the update process pushing it beyond Microsoft's one month limitations.
Majority of the times when Feature Update fails (or even Cumulative ones) a total refresh is a success. Total PITA though going this route especially since I'm finding it's an all to frequent occurrence.
Updating to 1803 on my work PC always timed out in the 80% range in the 3rd stage (pretty much my experiences w/every failed update), also several freeze ups getting there requiring manual shutdowns / reboots. IMO sooner or later those attempts to install updates that fail and induce freezing and forced shutdowns, are going to take their toll and wreak havoc, this is usually what happens to me - it has gotten to a point, because of the frequency it has occurred, that I can almost predict when we've reached our final destination and it's game over.
