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

I was able to fix the problem by disabling VT-d in my BIOS. As it stands, Windows 10 1803 will not boot if this is enabled.

I have the same problem. Windows 1803 will not boot and hangs at the splash screen.

I disconnected everything and even disconnected all the HDs in my computer and the disc will not boot either (also hangs at splash screen without the spinning circle). Computer is 100% frozen. CTRL+ALT+DEL won't work and pressing num lock will not toggle the light.

Hard rebooted the system and went into the bios to disable VT-d (as per Seth_N_Michel's post) and now Windows Spring Creators Update (1803) boots without freezing from the disc and from rebooting after installing through the existing Windows install.

Hope Microsoft will fix this issue soon! 

After 2 weeks trying everything (basically only left mb and graphics card) and about to give up and stay on old rev I found this solution which really works, thank you guys. My Asus P6T had always worked fine until this latest April update.

I booted my CPU with previous windows ISO and started just fine and with newest ISO stays on blue logo doing nothing so this really confirms it's an issue with the newest windows 1803 update.

Asus P6T Deluxe V2, latest (ehm) 1202 BIOS - I also confirm the issue and the workaround.

Thanks for posting, I wasn't looking forward to updating from 1108 to 1202 just to test that :)

so this really confirms it's an issue with the newest windows 1803 update.

I wouldn't make such conclusion.

It may confirm that there's some issue with legacy motherboards based on X58 chipset from ASUS, probably, in BIOS microcode (initializing North bridge registers/flags/whatever).

VT-d:

 1. I/O device assignment.

 2. DMA remapping.

 3. Interrupt remapping.

 4. Reliability features.

Probably 2 or 3 fail to be compatible with new OS version(s).

"so this really confirms it's an issue with the newest windows 1803 update."

I wouldn't make such conclusion.

...<snip>

Probably 2 or 3 fail to be compatible with new OS version(s).

You wouldn't conclude it's got anything to do with 1803 but probably some machines fail to be compatible with new OS versions...

Maybe I'm missing something, can you explain that contradiction? :)

It seems quite clear that 1803 causes instability in some scenarios where there were no issues before. Hence it's an issue with the 1803 update. It doesn't mean it's a bug, there could be a required change in the way these features are used which renders some machines incompatible. I think the thing most people would like is just an explanation from Microsoft to acknowledge the issue, the likely cause, and report on if it's going to be resolved.

Seems to mainly affect older boards from what I've been reading, so I think it'll be quietly swept under the rug and the noise will go away.

"so this really confirms it's an issue with the newest windows 1803 update."

I wouldn't make such conclusion.

...<snip>

Probably 2 or 3 fail to be compatible with new OS version(s).

You wouldn't conclude it's got anything to do with 1803 but probably some machines fail to be compatible with new OS versions...

Maybe I'm missing something, can you explain that contradiction? :)

It seems you're talking with some mental image.