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)
I am unable to install The Windows 10 Feature update to OS version 1803(from version 1709) on my PC.
It is giving 0xc1900101 error. I have all the latest drivers on my PC. The current OS build of my PC is 16299.371.
After each failure, the update gets downloaded again and it has failed 5 times.
I would be grateful if someone could please help.
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.
SO - after about 1,000 attempts with Windows update and update assistant and a dozen or so other tools.. I FINALLY got windows to update from 1709 to the latest version (May 2019 update).
I found this link via an update page for a game on the Microsoft Store. Ran the update from here and it worked perfectly (no guarantee it will work for everyone.. but at least it has worked for me, so there's a chance!)
I 've had the same issues, and after many attempts and trying most suggestions I 've found online such as uninstall hyper v, remove antivirus, run windows update troubleshooter changing bios settings for virtualisation, and clearing windows>softwaredistribution folder, fixing Windows corruption errors with DISM & SFC tools and restarting bits and windows installer… and nothing seemed to do the trick. Until I thought to try decrypting the C drive I had encrypted with VeraCrypt… and bingo this fixed it for me… I then discovered it is a know (VeraCrypt related specific version) issue I was using and there is an updated version that addresses the issue. Worth mentioning that same version of VeraCrypt (1.21) was causing me issues with the win 1704 update too.
Well, I believe that this forum is made up primarily of users that are volunteers. They have limited knowledge and offer only generic solutions. As far as the engineers reading it, good luck with that, although it would offer them a great amount of insight. You must go to give feedback and post there in order to "possibly?" be heard. Good luck, i myself suffer the same problems, can[t upgrade from 1803 to 1809. I am waiting to see what happens with the April update. I use Windows for very little anyway.
I can only hope that the engineers at Microsoft who develop the updates do set aside some time to take note of the content of websites such as the current one, since it is the right thing to do, in order to provide a better service to its customers.
This is all you can do because in this forum you will find no real help. You need to be speaking to the engineers, but you can't. They may fix this in the next update in April, that is my hope. If it were Linux we could get the source and fix it ourselves.
