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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-06-23T21:35:53+00:00

    Non-Asus X58 PC affected.

    My 2-generation-old PC (now my wife's) had the same issue.  (As old as it is, it's surprising how good of a machine it still is.)

    i920 3.6 GHz OC

    ASRock X58 Extreme

    BIOS P2.90 (last update, 2011)

    Boot Device Adata SX900 (256 GB) SSD

    6GB Triple-Channel (remember that?) RAM 667 GHz XMP

    AMD R9 280

    Would hang on Windows logo on the 1803 update until VT-d switched off.  Since I'm not running any VMs on that system I can just leave it off.

    BTW, Hyper-V is disabled.  I thought at first that since VT-d is for VM and Hyper-V is enabled by default on a clean installation (I believe) that it might be an issue but this PC was upgraded and it wasn't on.

    I wasted several hours on this before discovering the VT-d fix.  Don't you love being a de facto Unpaid Windows Beta Tester?

    Microsoft needs to hot-fix this.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-07-02T14:09:18+00:00

    Same mobo, and same problem, thanks a lot for sharing, at least now I know not to bother trying a clean install!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-07-03T02:57:47+00:00

    I have the same problem with an HP z200 workstation. I watched my machine spin for 5 hours before looking around for a possible issue. Disabling VT-d did the trick immediately.

    I use VMWare quite a bit and am unsure if disabling this feature will slow down VM operation or make shared devices unusable; at present I find that networking continues to perform, but I have not tested printers or other external devices.

    usoft needs to get on this!!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-07-03T03:11:03+00:00

    May I ask how on earth you tracked this to VT-d?  Worked great for me as well, but that seems unguessable to me!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-07-03T03:45:30+00:00

    :-)

    I poured through discussion groups mentioning difficulty with VT-d. Are you using VMware too? That's probably the only reason to keep it on for higher performance virtualization, as far as I know.

    Tiran

    6FootMedia

    Was this answer helpful?

    0 comments