For Windows 10 1803 disable VT-d in the bios.
Updating to Windows 10 version 1803 freezes on the Windows logo upon reboot
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
102 answers
Sort by: Oldest
-
Anonymous
2018-08-31T21:42:43+00:00 -
Anonymous
2018-09-13T18:44:11+00:00 Same issue for me with an Asus P6T. Tried it out with VT-d disabled and was able to boot and install the update. Rolled it back since I do use VirtualBox for testing builds. Also tried installing a fresh install of Windows 10 and had the same issues with freezing on the boot screen. The frustrating thing is that you can no longer use the Media Creation Tool to create Windows 10 install media b/c it uses the latest build. Would love to see this fixed in future builds, but hate to have to test each update to see if I can finally migrate to 1803 with VT-d still enabled.
-
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
-
Anonymous
2018-09-21T03:58:22+00:00 @Seth_N_Michel. Thanks for saving me a ton of time troubleshooting this problem!
-
Anonymous
2018-10-03T18:11:33+00:00 Same Problem on Windows 10 , 1809