Updating to Windows 10 version 1803 freezes on the Windows logo upon reboot

Anonymous
2018-05-03T03:35:15+00:00

I've tried using Windows Update, repairing Windows update, using Windows Media Tool to create a bootable USB for a clean install, unplugging all peripherals including mouse and keyboard, reseting BIOS settings to defaults. No matter what I try, when booting to setup after installation through Windows Update, or when booting from the USB ISO the system hangs on the Windows logo for hours with no spinning dots and no hard drive activity. All I can do it hit the reset button. When trying to install via Windows Update and having to do a hard reset when it locks up, the resulting error code I find is 0xc1900101.

i7 965

ASUS P6T Deluxe

12GB RAM

310GB Free on OS drive

SoundBlaster Z

Nvidia GeForce GTX 970

Windows for home | Windows 10 | Install and upgrade

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.

0 comments

102 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-10-04T23:33:27+00:00

    Same Problem on Windows 10 , 1809

    Here here. 

    The weird thing for me is, ive had this issue since the 1703 build of Windows where when trying to do an upgrade within Windows, it hangs after the first reboot at the Windows startup screen.

    I tried disabling all of the virtualization features on my MSI X99A SLI Krait board, but i still have the same issues. Doing a clean install works fine; i dont have any issues booting. Its only the upgrade from within Windows that has hung on my system anytime i try to do a build upgrade. I've had to do a fresh install for each of the past three builds.

    Does ANY one have any advice?? Im getting tired of doing this every six months .

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-10-03T18:58:57+00:00

    Same Problem on Windows 10 , 1809

    Thanks, I was tempted to try 1809, but will save myself the effort.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-10-03T18:11:33+00:00

    Same Problem on Windows 10 , 1809

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-09-21T03:58:22+00:00

    @Seth_N_Michel.  Thanks for saving me a ton of time troubleshooting this problem!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-09-17T21:26:35+00:00

    Same problem here. I oftenly use virtual machines, so if it remains unfixed (tested also with 17760.1), I will continue to use Windows only for some applications and games that are incompatible to Debian.

    IF this error is indeed related to Core Isolation (not Memory Isolation), I haven't found any way to disable this delicate security feature by means of configuration, unless enforced by disabling the underlying BIOS option. Without my VM's, I would need to run unapproved software or websites directly on my host system, which certainly isn't more secure in any way - aside from the fact that some applications cannot be used at all anymore. It's a shame that Windows - so is my observation - diverges to an incontrollable, poorly documented patchwork. Have already departed from using Cupertino's products for the same reason.

    Anyway found this on feedback hub: https://aka.ms/AA2lo6r

    Was this answer helpful?

    0 comments