Hi Alex008,
I know how frustrating it is when the new Insider build update keeps rolling back after reaching 100%, especially when the certificate is close to expire date. The AI answer has already covered the common troubleshooting steps for this situation, have you tried them out? If the situation hasn't improved, I think it's better to gather more information first:
- Check whether the failure generated Windows Setup logs, e.g.
-
C:\$WINDOWS.~BT\Sources\Panther\setupact.log -
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log -
C:\$WINDOWS.~BT\Sources\Rollback\setupact.log -
C:\Windows\Logs\MoSetup\BlueBox.log
-
- Download and run SetupDiag from Microsoft:
- Search
0xC1900101and note down other information linked to it. - The extended code may identify the phase and operation that failed.
- Search
- Visit the PC or motherboard manufacturer and install the latest:
- BIOS/UEFI firmware package
- Chipset, storage controller, GPU drivers.
Surprising number of Insider update failures are also linked to storage controller drivers. Even if you have removed all additional devices, their drivers can leave some leftovers, which are common contributors to 0xC1900101 rollback cases. Open Device Manager and uninstall any entries you don't recognize or not used anymore.
In addition, there's actually been reports from community members facing issues with updating the latest Insider builds. For example, Error 0x80070005 when updating Windows Insider to 29639.1000 for 7 consecutive times..., or My computer cannot update to the new preview experience system, and so on.
Disclaimer: The latter thread is in another language. It's referenced here only because it might be related to your issue. You may use a translation tool, but please be mindful that some meanings may be translated inaccurately.
Although the error codes in the issues above are not identical to what you're experiencing, the fact that multiple users are encountering upgrade failures / rollbacks with Insider builds makes it possible that this might not be solely a problem with your device. So besides trying to fix this yourself, consider:
- Report this to Microsoft engineering team via Feedback Hub (press Win + F)
- Describe the issue, and share the logs acquired above (if possible), especially:
-
setupact.logandsetuperr.log - Output from SetupDiag.
-
If you wish, you can share them with me too and I can help reviewing to see if we can find the specific components that caused the failure. To protect your personal information, please upload those files to OneDrive and share the link via Private Message.
If you think the answer is helpful to you, please mark this as accepted. If you have extra questions about this answer, feel free to click "Add Comment" and ask!
Note: Follow the steps in our documentation if you want to enable and receive the related email notifications for this thread.