For claiming back your controls over updates, as well as other 'telemetry' stuff, people use this https://www.oo-software.com/en/shutup10
Updating to Windows 10 version 1803 freezes on the Windows logo upon reboot
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-11-01T12:38:21+00:00 -
Anonymous
2018-11-25T04:20:48+00:00 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.
Seth_N_Michel Thank you for this amazing contribution. The time you took and the skills and experience you applied to come up with this amazing, simple and easy to do solution has just saved me $2000 for a new computer I didn't need. My ASUS P6TD Deluxe has been a "just-right" companion and now we can truck on without fear that our Windows 10 operating system would not become unsupportable. I turned on computer/tapped Delete key/searched in BIOS relative to processor/CHIPSET/found VT-d. The VT-d was ENABLED so changed to DISABLED and voila! Installation completed successfully as did the catch up updates. Thanks again to all for this great site and the help it gives through the generosity of the many contributors. E pluribus unum
-
Anonymous
2018-11-29T05:11:36+00:00 Hi
Just forget all pseudospecialist and microsoft too for this problem and search with old geek for a real solution to the **** micro have done in 1803 all about vt-d and or vt-x virtualisation.
For you the solution is to just go in your bios at start of machine and disable an internal option vt-x and or vt-d (sometime reported as intel virtualisation tech" or similar.
and the problem is gone after that.
and thanbk to all Specialist whoi just says all time youll have to restart pc or its your fault like just buy another crap.
good chance
-
Anonymous
2018-12-12T18:55:43+00:00 Good day, that solution will not work for me. I have done everything under the sun, and i am tech, and can not install the 1809 update. This update downloads, installs, then wants to reboot. You reboot now, there she goes, through the bios screen then on to the windows 10 logo. At that point everything stops-keyboard, mouse, everything except the hard drive which you can hear running at maximum velocity. You can leave the machine all night long, but when you awaken in the morning, it is still unchanged. Please do not suggest any of the generic solutions, as I have been through every suggestion on the web. I have now given up on updating for now, putting it off for 180 days, or until Microsoft comes out with a newer version. I have even tried a clean installation and can't do that either, not with the 1809, it simply boots to the logo and will not proceed to install. No, nothing at all. If anyone at Microsoft has figured this out. please let me know. Thanks. Oh, its an old Toshiba laptop with a dual-core processor and 2 gigs of memory, it qualifies for the updates and has always updated in the past without so much as a burp.
-
Anonymous
2018-12-16T17:27:21+00:00 Hi,
great thread here. I've got the same Problem. (Asus X58 Mainboard).
The facts are clear: Update works with vt-d disabled.
I don't know who's fault it is - maybe both, MS and Asus f****d up. (But it worked until the Update with vt-d, and I hardly think, that Asus will bring a new Update for the Board)
My main question is a bit different. So it's almost a year now. Does MS intend to fix the Problem ? Or do they want people to switch to Linux ?
The Pro in the Version Title sounds more and more like a joke ...
I WANT vt-d, that's why I bought such a CPU. So either there will be a fix, or I'll disable Updates, as this is totally annoying,
or I'll have to switch to another OS which is actually working with vt-d ...