Tech Community Live: Windows edition
Jun 05 2024, 07:30 AM - 11:30 AM (PDT)
Microsoft Tech Community

Laptop failed to boot after insider preview 17074.1002 (rs_prerelease_flt) update, error 0xc1900101

Copper Contributor

I have two laptops, one (VAIO Pro 13) updated to preview 17074.1002 just fine. The other one (Toshiba Portege z30) failed to boot after installing the update.


The update was downloaded and installed, I restarted the laptop. It booted up to a green screen saying it was updating, and after 100% it restarted again, but this time it failed to start. The screen was stuck at the Toshiba logo and a spinning circle of dots. I went to do something else more than 30 minutes and the laptop still stuck at the same screen. I had to press and hold the power button to restart it. It booted up and stuck at the same screen.


Another one or two attempts of restart then it reverted back to the previous working update. Tried updating again for a few times and still got the same problem.


Suggestions would be appreciated.

5 Replies

On the failed laptop, is virtualization enabled in the BIOS/UEFI?

If so disable that and try the update again.

Sorry for a late reply and thanks for your suggestion. I disabled the virtualization and tried the update again but still got the same result.

Update: After trying a lot of different things, I finally found out the cause. It was Panda antivirus. After I uninstalled it, the insider preview installed just fine.

Advanced Computer User Solution (manual update):

1) Start your computer and log on as an administrator.

2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3) In the new window, select "Restore my computer to an earlier time" option and then click Next.

4) Select the most recent system restore point from the "On this list, click a restore point" list, and then click Next.

5) Click Next on the confirmation window.

6) Restarts the computer when the restoration is finished.

@P P 

Thank you for update, normally when you run into update failure, before doing anything check Windows Update log files and there you could find root cause of problem: