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

i have enabled VT-d in my BIOS, 1809  boots  fine , eventhough i upgraded  from 1803  by   installing  setup.exe in windows dvd  10 iso

Hp x360 and Lenovo T470s with Core i5-7200U

Lenvo T480S Core i5-8250U

HP Pro x2 with Core i5 7Y54

We are running Win 10 enterprise, I don't know if that make any diffrence, but for us a offline patched media solves the in-place upgrade problem we had.

We didn't have any problem doing a fresh install of 1803.

Our environment most probably is different from what you're using since we using SCCM to deploy the update to the users, and have a fully patched VIM.

I want to update my windows. I have a product key

The latest servicing stack update and the latest cumulative update solved the VT-d problem for us in 1803.

After the install and a reboot we could enable VT-d without any problem.

We also update a machine from 1709 to 1803 after KB4486996 and KB4485448 without deactivating VT-d with success.

So, for 1709 you need KB4486996 and KB4485448.

For 1803 you need KB4485449 and KB4487017

I tried to install 1803 fresh new on my system, disabling vt-d first, then I tried to install KB4485449 and KB4487017 and reenabling vt-d: no avail, the system hangs at bootscreen and the loading icon was not showing.

So I tried to install 1709 fresh new**** the system hanged at bootscreen without the loading icon, so hard resetting the computer made it restore 1709 and boot again, showing then an error on Windows update.

So, you sir, either are a liar or you're using a system not affected by the bug, but until you answer my question, both options are potentially true.

It is not the solution for Microsoft, they can't even figure that out. But migrating to GNU/Linux and using different software or in most cases the same software is easy peasy for anyone with a rudimentary understanding of the computer. You must be one of those die hard Microsoft fans. Well, good luck to you with all this "upgrading". Every time Microsoft tries to make "improvements" to the system, they end up setting it back. They hardly ever advance in anything except for the difficulty in getting you pc upgraded. You have to jump through hoops and bend over backwards to get it working. They should just stop and make what they have function, and then leave it alone when and if they ever get ahead. If Linux is so bad, then perhaps you can tell me why all the Supercomputers in the world, the banks, and the government computers, actually all computers that are of importance, use Linux instead of Windows?? The reasons are many, as you probably know. Give up on the worthless Microsoft products. Use you time to enjoy computing instead of the pc giving you a headache.

First of all don't make assumptions out of nowhere, I'm not a die hard Microsoft fan, i'm actually a Microsoft user, as much as an Android user. I'm not against GNU/Linux, but this is not the place to discuss or suggest to switch to another OS Platform: we're here to find a solution to an apparently not considered bug of the latest versions of the Microsoft main OS.

Also I've already heard and/or read your harangue about Linux universally used on important systems: well, as much as I can agree on that, MY system (also many of my friends' and customers') aren't of much importance, and Linux isn't the best OS on desktop computers for many many reasons I will not and want not explain, besides I don't want to face a hard time on migration of my data (or of anyone else).

So, if you're done with your Linux advertising, we can now move on and get focus on the main issue.

Thanks.

P.s.: by the way, it's not a solution for US, not for Microsoft.