Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
About an hour. Was I being impatient? I've seen this problem before though. The rest of the install was done in a few minutes. It's the last bit that's taking ages. I've got Windows on a SATA SSD.
It's an i7 8700. Sitting at 32c
Mine also seemed to be stuck at 93%, but moving the mouse woke it up
The media tool would possibly be a sure fire solution, but i didnt feel like goin through that
All in all the update installed just fine
Also keep in mind, a number of your settings will be reset such as speaker config and so forth after install.
And if you have it so that Windows wont auto install drivers you'll have to re disable that as well. (Found that out myself after DDU'ing and it auto installed an old ass driver after reboot)
> wipe all Displays
> wipe geforce experience
> allow safe mode option
Once these are all ticked ON, X out the options screen and close the ddu app, then relaunch it. Then select safe mode, restart options. Once in safe mode, allow ddu to run. Or run it manually if it for some reason does not auto launch on its own. Then select each brand for audio and gpu. After you select a brand, click "clean but do not restart" and do each brand one at a time until all have been done. This will in the end have wiped out any installed audio devices, motherboard chipset, gpus and displays from the system. Also click the option to Disable Windows Auto Driver Installer, which will stop Windows from auto applying drivers from Windows Updates.
When all done, reboot normally.
Once back to normal mode desktop, first launch Disk Cleanup via Run as admin. Tick all boxes except for Downloads. Click OK, once it is done, reboot and then proceed with the 2004 Feature Update.
If you feel the need, as it may help to have for any update, clean install, or repair purposes; go ahead and make a fresh Win10 64bit usb flash drive (or simply wipe out an existing one you've made before) using the latest download for media creation tool from official MS Win10 website.
After 2004 is fully installed and it's at the Desktop, first do a manual Check for Updates to see if any further updates are pending and need applying. If so do all those til no more are left. Multiple reboots may be required in order to complete the whole process. Once no more updates are left and you have done a fresh reboot, go ahead and download all latest drivers for; chipset, gpus, audio, lan, wifi, bt; etc. And install them one by one, rebooting after each install completes. As latest drivers should be Win10 2004 compatible.
If you are running an Intel 8th gen or later spec system, or anything AMD Ryzen/ThreadRipper, update to the latest bios prior to the Win10 2004 update
If you run into a problem where Windows can't finish an Update,
you are probably better off not Updating... Windows Updates are
not great at all... Getting stuck at 93% is just one of those issues...
There are some even far worst then that... The problem isn't the
Updates... It's that the problem is with the Auto-Update feature...
Not being able to Permanently turn it off without some form of major Editing...
I meant Windows 10 Updates...
Ya, you need it for Security (But Unless you know 0 about Security, i'd rather handle it myself)
It doesn't mean that at all. I've seen plenty of machines not update properly and it was usually due to two simple and common reasons.
A) the currently installed drivers caused unforseen issues.
B) there was simply an issue with how the updating process functioned based on getting the updates (usually never all at once but over time as the user was in the middle of using the machine, rebooting it over the course of many days, etc) via Windows Updates Service.
If a user experiences an issue where they can't get the update to work from WU, but are able to revert the stuck update process. Also keep in mind Feature Updates have gotten better, to where it can detect various problems and revert the entire process all on its own... the user CAN do an in-place OS upgrade instead, using a USB flash drive that contains the latest ISO via media creation tool. Once they have that latest version Win10 on their usb, you can simply run setup.exe off the usb drive while at your Win10 desktop. This would run a similar, but much more stable updating process.
get the correct mobo/chipset drivers from the oem or mobo site
then gpu drivers from the gpu mfg (amd/nvidia/intel)
(correct and old drivers is better than the wrong ones)
But yes always best to hold of on ANY updates from MS regardless of what it is, or claims to do.
As we have seen on many occasions updates have released as a quick fix and turned out to be much more of a problem then a fix or more of a problem then the fix was worth, amd then pulled from MS servers and released at a latest time after much further testing and problem solving was done.
It's one reason why everyone should just install Win10 64bit Pro if you are going to be using Win10, period. This way you have Group Policy and much better control over the OS, ability to Disable Windows Updates for a lengthy period, etc. With Win10 Home you can't do this easily except with apps like ShutUp10 or similar type of app.
You can see which updates release and when, etc via Google > Win10 update history. The listing on the MS site will break down the KB# of each update and list updates based on OS version (i.e. 1903, 1909, 2004)
To get a better break-down of what any OS update does, changes, etc. Simply Google the full KB#
But that also should just be common sense. Every WinOS user should know this, espeecially in this day and age, unless maybe Windows PC is somehow all brand new to you as a user. Windows OS has always been this way since it's creation and that has never changed. All that has changed regarding that is built in compatibles that allow proper detection and use of hardware, such as Win7 SP1 and later ability to properly see most Drives without Floppy/USB drivers needed to apply a proper ahci, raid... or in Win10 case, nvme. But again what the OS uses by default are always basic, generic, aka compatible slim drivers. Which allows the os to see and ID hardware to a certain degree. But again most of those drivers built into any Windows OS lack detailed defining within. This is where official drivers come into play, and are a must.