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 trying to install the new Windows 11 update from Windows Update, but I keep getting error 0xc1900101.
The installation starts, and after a couple restarts, it says:
" Attempting to recover installation "
" Undoing changes made to your computer "
And then I am greeted with error 0xc1900101 on Windows Update.
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.
That known issue is referring to 22504 with 0xc1900101-0x4001c error and has nothing to do with the OP concern. There is a specific -0x4001c extension for that error for this build only for some devices (Not related).
Hi Johnny,
MSFT issued the same warning for Build 22499 too, and recently I helped a user who faced the same error trying to update to it but with a different extension (0x30018).
Windows 11 Pre-release Updates are Failing
Regards
Problem is also that Paul gives no idea who he's
responding to in 16 pages of posts.
And yes, I do wish posters would give the build #
they're on!!!
Agree.
Maybe it's time to lock it up. 😉
What Known Issue are they fixing?
The OP's issue goes back to June.
Hi CK,
That's a problem with this tread, most posters don't list their build number.
We know this is a known issue updating Dev but can happen if they are trying to update from other builds.
Problem is also that Paul gives no idea who he's
responding to in 16 pages of posts.
And yes, I do wish posters would give the build #
they're on!!!
In there
Hello Paul,
That known issue is referring to 22504 with 0xc1900101-0x4001c error and has nothing to do with the OP concern. The error code 0xc1900101 can be a generic error code with many reasons for update error. Advising someone that is going to be fixed is incorrect as this thread dates back to June, not current Dev build. Please reread the known issues again. There is a specific -0x4001c extension for that error for this build only for some devices (Not related).
Regards,
