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

I have continued to have this exact issue since the early beta roll out of this build. Machine does not have VT-d enabled, I have disabled or disconnected everything except the monitor, keyboard, mouse and HHD-1. I've dropped the RAM expansion that was preformed over a year ago. This distinctly appears to be a problem with the update itself. I have booted to a minimal boot configuration and it still locks up at the splash screen on the update reboot. I have used the update repair tool and it locks up at the splash screen on the update reboot.

Microsoft, in it's infinite wisdom, no longer even allows us to disable updates from occurring. Now we can only delay it for a few days and then have to go through the entire process of download, install and lock up once again at that point.

There appears to be too many people having this problem for it to be anything other than an issue with this particular build.

It seems you're talking with some mental image.

Sorry, you lost me there, no idea what that means.

"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.

"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.

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).