Windows 10 Feature Update 2004 taking too long to install

Anonymous
2020-06-13T15:35:11+00:00

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.

Windows for home | Windows 10 | Windows update

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.

0 comments

183 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-09-17T16:17:00+00:00

    Agreed - totally digging the execution and existence of Windows 10, but I'm certainly not loving the servicing/update aspects of it. Like I've said before, it seems with each build/update, there's a whole new world of hurt that coincides with it. It was never, ever, that I can recall, anywhere close to this madness when dealing with tried and true service packs. LOL.

    Maybe it's time to consider what my coding friends have done (historically)...complete employee work on a standard config and install/use my needed tools in a virtual environment on a system that doesn't need to "keep up with the joneses".  :0)   I have access to the LTSB versions of Windows 10, but never gave it much of a thought (until now).

    I started attempt 29 a few hours ago...running "setup" via 2004.2 build...keeping nothing...jumped to and through the blue screen...

    Installing Windows 10

    Your PC will restart several times. This might take a while.

    <spinning dots> 64% complete

    [ Cancel ]

    It took 3 minutes to get to 64% and now it's been "spinning" for just about 2 hours now. Tap. tap. tap.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-17T17:45:21+00:00

    It's mind boggling! Truly mind boggling. They will either dazzle you with brilliance, or baffle you with BS! No neutral zone. No middle of the road. Either, or. That's it. 

    Considering all that you've tried, I've run out of "help". All I can do now is just feel your pain. If I come up with anything, I'll be sure to post it. But right now, I'm clueless....

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-23T04:17:55+00:00

    just waited for THREE HOURS on my laptop for the Windows 10 update 2004's phase of just "getting things ready" which was mainly due to an hour stuck  @ 70% ... after SIX HOURS i'm up to 34% of the "downloading" feature .... then, the "biggie" revamp install of Windows 10 awaits (that's waiting on this FIRST install) that occurs twice a year ... but I understand that actually goes faster.  

    WHAT THE HECK WINDOWS ??  I don't remember any previous versions taking TWELVE HOURS to "get ready" then "sort" then "install" updates. thanks a lot .... MEE

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-28T13:10:30+00:00

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-09-28T13:12:59+00:00

    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.

    Was this answer helpful?

    0 comments