There are new Windows 11 Insider Preview 24H2 Canary Edition Build 26080.1 release for your rigs everyone.
Microsoft teams had fixing many error on previous build including update error 0xc1900101.
Why don't you trying the lastest build ?
Windows 11 Insider Preview 10.0.26052.1100 (ge_release), Install error - 0xc1900101
![](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)
Anonymous
Hi
As per heading of question, my laptop is enlisted in Windows Insider Program for Windows 11 Home edition. I had been receiving insider updates and all installed smoothly. Bu the update as per subject line became available 2 days ago and i proceeded with download and install. After 100 % installation, restart prompt flashed. i promptly restarted but for some reason laptop was taking inordinately long time to apply all updates. After 1 or 2 restarts, laptop simply shut down instead of restarting. I started laptop using power button. And now i received message that last update failed and hence reverting to last known configuration. Laptop finally reverted to earlier state. But again update became available as i have enabled auto update. I downloaded and installed update once again. But this time before restarting, i checked all the drivers were upto date, UEFI and other boot options were enabled, and i removed all USB plugged peripherals. BUT when i clicked the restart again after 1 or 2 restart while applying updates, the laptop just shut down. And when i switched it on , again the process of reverting to last working configuration started. My laptop fulfils all requirement for Windows 11. It is Acer Predator G9-791.
I need to know why this update is failing to install and reverting to present configuration. Kindly advise , any and all inputs are welcome
here i am sharing link to feedback hub as suggested - https://aka.ms/AAp1vq4
So guys and gals, here i am posting a way to resolve it. If you are enlisted in Canary or Beta channel, then update is going to fail invariably. But if you are on Dev channel, then there are very good chances of the update going through. But for changing from Canary or Beta to Dev channel, you will have to install Windows Insider build 23165 from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso?wa=wsignin1.0.
Give it a shot and see whether it resolves it for you as it resolved this update error for me.
Windows Insider program | Windows Insider preview | Install, activate, and 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.
52 answers
Sort by: Most helpful
-
Anonymous
2024-03-14T04:41:47+00:00 -
Anonymous
2024-03-13T19:02:02+00:00 I don't have a loopback controller showing in device manager. Just the Microsoft Storage Spaces Controller and 2 NVM controllers.
-
Anonymous
2024-03-13T18:30:44+00:00 I uninstalled the 'Loopback controller' then restarted and finally the update went through :)
Just leave the Microsoft Storage Controller and the Standard NVM controller, and uninstall the rest
-
Anonymous
2024-03-12T01:23:09+00:00 Same issue.
Installation Failure: Windows failed to install the following update with error 0xC1900101: Windows 11 Insider Preview 10.0.26058.1100 (ge_release).
Hangs right after boot screen.
Can't find a solution.
-
Anonymous
2024-03-03T04:28:12+00:00 I am having the same issue and tried everything in this thread. I still can't update to 1100. The folder "*$Windows.~bt\Sources\Rollback*" exists for me but there is no .dmp file in there. I have plenty of other files in there such as setupact.log which tells me there was no crash experienced, but it is rolling back the installation for some unknown reason. I assume that .dmp file only gets created when the installation experiences a crash.
Also, the 2/22 update on the MS Insider Preview blog seems to indicate there are compatibility issues with Virtualization Based Security (VBS) if you have it enabled. I tried disabling VBS, but I still can't update.