This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Today I was notified by Windows Update that the 2004 update is finally ready to be downloaded and installed on my laptop. I pressed download and install and left the laptop plugged in idle as I did not have any laptop work to do at that time. Now it's been 4 hours since I left it on, and the Windows Update screen (in the Settings > Updates & Security) is still at 94% installing, which is the exact number I saw more than an hour ago. Is it stuck? Why is it taking so long to install? My internet is fast enough, I don't have many programs installed apart from a few essentials such as Office and Inkscape along with other credible software. I am afraid that if I close it and reset the Windows Update, it'll take 4+ hours again (not to mention the additional lengthy rebooting and installing the update again in the blue background screen which happens with every single update), plus it's already night here so I cannot leave it turned on while I go to sleep.
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.
You should return the PC this could mean it doesn't have an authentic Windows version.
No is does NOT mean the PC doesn't have an authentic Windows version. Tested that in specific.
I commend you on your PC response. I'm unsubscribing from this thread (I'm all laughed out). Unlike this thread, haven't given up on determining the root cause...if ever I discover the culprit for my roadblock, I'll try to remember to report my experience. Good luck!
Rod, I asume you've read about 2 pages of this thread at most.
Pointing us to the ISO-download and calling it an Update Tool, just doesn't cut it.
Not helpful.
Well, that's what Microsoft calls it. When you start the tool, it asks you if you want an .ISO, or a USB Flash Drive. Maybe that's what he was talking about, I didn't see the comment. But I KNOW that the nomenclature that MS uses in the Media Creation Tool for Windows update.
Just sayin'....
Rod, I asume you've read about 2 pages of this thread at most.
Pointing us to the ISO-download and calling it an Update Tool, just doesn't cut it.
Not helpful.
Well, that's what Microsoft calls it. When you start the tool, it asks you if you want an .ISO, or a USB Flash Drive. Maybe that's what he was talking about, I didn't see the comment. But I KNOW that the nomenclature that MS uses in the Media Creation Tool for Windows update.
Just sayin'....
And just in case you think I'm full of it too,
Don't shoot the messenger....
Rod, I asume you've read about 2 pages of this thread at most.
Pointing us to the ISO-download and calling it an Update Tool, just doesn't cut it.
Not helpful.
Well, that's what Microsoft calls it. When you start the tool, it asks you if you want an .ISO, or a USB Flash Drive. Maybe that's what he was talking about, I didn't see the comment. But I KNOW that the nomenclature that MS uses in the Media Creation Tool for Windows update.
Just sayin'....
And just in case you think I'm full of it too,
Don't shoot the messenger....
Oh heck - sorry guys. I didn't realize it's MS' nomenclature. My mistake.
I'm just quite p*ssed off comming back to this issue after 2 weeks vacation just to see that nothing has changed. Loads of users picking around in the dark and still not even a spark of support from MS. Gonna submit another post in a minute - we're testing a little more.
Gonna submit another post in a minute - we're testing a little more.
Well, after vacation, back in office, talked to my peers and decided to test the following:
Our WSUS in our domain feeds our clients select updates: Only critical updates and patches, no snazzy **** we don't need. Philosofized over this a bit and thought along the lines of 'what if one or another patch included something in preparation for upgrading from 1809 to 2004. We have had instances where MS would push out patches in preparartion for something to follow at a later stage.'
So we already have our test OU in Active Directory where we unlinked all GPOs that could enstrangle a Win10 client in any way. Starting out with the client at Win10 1809, it gets tons of updates: Cumulative, Servicings Stacks, and [watch:] Feature Update to Win10 1909, followed by Feature update to Win10 1903 (!) and is now spinning at 78% since 80 minutes and seems stuck once more.
Will post a follow up when I get there.
Update: 7 hours later winver shows Win10 1903 build 18362.1082. Rebooting and checking for updates yet again, gives me 'You're up to date'.
Gonna recheck for updates on a daily basis until I finally (hopefully) have a 2004 machine.
For heaven's sake MS get your f*cken act together!!!!!oneeleven
