Windows 10 Feature Update 2004 taking too long to install

Hey community,

I have read all 11 pages of this thread and second just about all the experiences the countless posters have echoed here. I'm responsible for roughly 120 client installations in our Windows 10 1809  and Server2016 environment. Using GPOs while it isn't worth keeping an SCCM. We managed to prevent automatic download and installation of newer versions post 1809. Now created an Active Directory OU for pilotgroup clients to test install WinX 2004. I have just spent the best part of three weeks trying to get the feature upgrade 2004 via on premises WSUS which is configured to distribute 2004 to said OU. After countless (9 to be honest) new installations that mirror our current client environment, I have gone as far as reinstalling the test machine yet another time, but this last time not even joining the company Domain, giving it nothing but a clean 1809 install and internet connectivity. Waited the usual days for the machine to finally say 'You're up to date.' The result being WinX 1909 (!) ****?!?

I have two questions:

1: Is there a known issue going from 1809 straight to 2004 i.e. skipping 1903 and 1909? I'm asking because in two instances where I actually managed to manually hammer 2004 into the client by directly applying the ISO downloaded from MS, after taking days I was finally present with 'Undoing changes made to your computer' <- that's worse than a BSOD, 'cause the undoing takes as long as the doing.

2: Has support for 1809 already been terminated or not?

Regards from Germany

Mat

I remember issues with 1903 that caused the update to be screwy, but honestly, that's the only one that I just couldn't get installed. But being an Insider, I was told to expect that, by someone in the "Community". I had to do what I described earlier, and use a flash drive and install it as a clean install. It just wouldn't install any other way. I'm still an Insider, and 2004 is still an issue, just like 1903. I know 120 clean installs is not what you're looking forward to. But your "test" group waiting days to finish, that's a bear. Wow....

Hey community,

I have read all 11 pages of this thread and second just about all the experiences the countless posters have echoed here. I'm responsible for roughly 120 client installations in our Windows 10 1809  and Server2016 environment. Using GPOs while it isn't worth keeping an SCCM. We managed to prevent automatic download and installation of newer versions post 1809. Now created an Active Directory OU for pilotgroup clients to test install WinX 2004. I have just spent the best part of three weeks trying to get the feature upgrade 2004 via on premises WSUS which is configured to distribute 2004 to said OU. After countless (9 to be honest) new installations that mirror our current client environment, I have gone as far as reinstalling the test machine yet another time, but this last time not even joining the company Domain, giving it nothing but a clean 1809 install and internet connectivity. Waited the usual days for the machine to finally say 'You're up to date.' The result being WinX 1909 (!) ****?!?

I have two questions:

1: Is there a known issue going from 1809 straight to 2004 i.e. skipping 1903 and 1909? I'm asking because in two instances where I actually managed to manually hammer 2004 into the client by directly applying the ISO downloaded from MS, after taking days I was finally present with 'Undoing changes made to your computer' <- that's worse than a BSOD, 'cause the undoing takes as long as the doing.

2: Has support for 1809 already been terminated or not?

Regards from Germany

Mat

I'm very sorry that his suggestions didn't help. I wish you success!

Hey Glenn, much appreciated, but I've been through all these steps (too many times) recommended by your friend, prior to searching for (and finding) others in the same boat (i.e., this forum). I only get an error code when attempting this via Windows Update...I don't have it at the moment, but per Microsoft, it suggests the error is based on WU component corruption, image corruption, activation problems (this was not upgraded from a previous OS), registry issues and/or related to the SoftwareDistribution folder (a good number of the recommendations you forwarded are the same). When I attempt the update manually, all I get as a result is a dialog box that reads "Update Failed" and an OK button. Nothing in the Event Viewer (as if the update attempt never even happened).

Hey Lance, I'm sorry you are still in the "bear cave" with this update. Remember the friend I mentioned earlier, that I told to unplug and I'll do the update for him later? Well, later was Saturday. I made an MCT flash drive, and took it to the computer. While it took 2 hours, it worked. The other friend who was able to just let the update run, after several hours, it worked. Both of these systems began their lives as something else, Win7, and Win8, and I upgraded them to Windows 10. They both functioned well until 2004 201xx.xx. Then we are in the "day", and I learned another tool to use to get this done. I wish it could work for you. Going into all of those other registry systems is always a danger. I do it as little as possible. Hope you get it fixed bro. If I come up with something else, I'll come back on and let you know.

Hey Glenn, much appreciated, but I've been through all these steps (too many times) recommended by your friend, prior to searching for (and finding) others in the same boat (i.e., this forum). I only get an error code when attempting this via Windows Update...I don't have it at the moment, but per Microsoft, it suggests the error is based on WU component corruption, image corruption, activation problems (this was not upgraded from a previous OS), registry issues and/or related to the SoftwareDistribution folder (a good number of the recommendations you forwarded are the same). When I attempt the update manually, all I get as a result is a dialog box that reads "Update Failed" and an OK button. Nothing in the Event Viewer (as if the update attempt never even happened).