“We’ve the same problem here. All my physical machines updated ok, but on a virtual machine running either Hyper-V, VMWare, or VirtualBox, it almost gets to the end of the update, and then rolls back. Worse, on VMWare and VirtualBox, the virtual machine software crashes at the end of the update,” one user noted in the Feedback Hub.
“Mine has the same problem. The first time I update the pc to the latest build it showed an error about my graphics driver so it rolled back I was suspecting that the windows update corrupted my graphic driver as after rolling back my graphics card was not working, it just works after I reinstall driver. I reinstall the update later and it was a success,” another user added.
Microsoft has now confirmed that some users have encountered this trouble. Unfortunately, Microsoft does not know the specific reasons and can only continue to collect data and then check. “Thanks for taking the time to report this – error code 0xc1900101 is a generic error displayed when an update fails and rolls back for some reason. This is an area we monitor closely and can have different root causes depending on which build you were attempting to upgrade to and your setup,” Microsoft said.
“If you were attempting to update to a previous Insider build, please try the latest one, as it may address your issue”.
If the user has determined that the disk space is sufficient and that the latest builds or preview builds version is not installed, they can try to completely remove the remnants of the previous build.If you’ve tried everything and nothing works, you can try these steps:
- (Works on preview builds like Windows 11 Build 22593 only)
- Open File Explorer and navigate to the system drive.
- Locate and open ‘system32’.
- Remove SecretFilterAP.dll from system32 as it is a leftover from older builds.
- Reboot and check for updates again.