Windows 10 Feature Update 2004 taking too long to install

I miss Windows 7 (as an IT weenie), but love Windows 10 (as a user). I had very little exposure to Windows 8...and when 8.1 came out with marginal response, I figured it's best to stay with 7 and wait for 10 (in the past, every other OS was a dud). It also didn't hurt that our in-house software wasn't "compatible" with 8/8.1.

While I can't say for sure, this plan to introduce Windows 10 as a service and further extend the UWP/MSIX model into the equation is the root of all Microsoft evil. Heck, I can appreciate that, at some point, a smartphone will be a computer and a computer will be a smartphone, but lets get real -- how about baby steps instead of jumping in with both feet? Nah, Microsoft as never been known to do such things. Hit 'em hard and hit 'em fast.

Relieved to hear that.

I tried the same, but am still stuck in the loop -- "You need an update" --> "Failed" --> "You need an update" --> "Failed". You can now add the following to my list (above and beyond everything else I've attempted)...uninstalled VMware, disabled Bitlocker, removed endpoint protection components, disabled firewall, removed VPN and still the same thing.

I'll keep trying/failing (this is true science) until I find a solution. One thing for sure, I'm happy this update isn't forcibly running each day (resulting in the "we'll restart your system after hours" notification) -- that would be an aggravation I can live without.

Love all the recommendations (re: "DISM prolly fixing corruption" and "let it run")...obviously nobody reads the previous 11 pages (before stating what's "obvious").

It is probably doing some fixes to corrupted system files with DISM-tool during the update process.

Press CTRL+SHIFT+ESCAPE and check if DISM Host Servicing Process is there and under some load.

It is recommended to let the update take it's time and don't interrupt.

DISM process during 2004 update has been known to take long when some corruption is found.

Hi Sumit,

2 comments:

1. Although yes, these sorts of updates aren't "automatically" installed, this update is shown a "something to be done" by WU and expecting users to not do the update because of how old it may or may not be is inappropriate. Either the update is ready for the install base or it isn't and generally a user should be able to apply any update without fear delivered via that mechanism.
2. "if the data and apps are in large amounts, the update may take time"  If windows is moving all of my apps and data to do an update then it is doing something wrong. Since this is a basically new install of Windows I can understand if your Windows folder is large it may take time to replicate it BUT if you're moving ANY of my files outside of that folder that is SO not appreciated (except *maybe stuff in the /Users folder). I have many TB of data which takes time to move no matter how fast my hardware is. 

Update on my current situation: My work laptop which is the one I spoken on previously in this thread took a full day to update (like 24+ hours).  My personal laptop took 1.5hours. In literally every way my Work laptop is newer and faster yet it took 18 times longer to install. The only meaningful differences being 1) Work laptop only has a single hard drive so my "system disk" has more data on it (about 700GB vs. 250GB) 2) My work laptop is on the work VPN and has Windows Update proxied.  Otherwise both are on exactly the same raw internet connection right now.  In-theory the latter should only show up when the update is "downloading" which the 2 were quite similar in their "download duration".  *INSTEAD the bulk of the time occurred during the "Installing" phase where internet connection should be irrelevant which brings us back to the System Disk.  Is the install really moving around ALL of my data?!  That's super poor if it is. Is it sending my data over the internet during "Installing"?!  If so also super poor.  ???