Windows 10 Feature Update 2004 taking too long to install

Hi everyone, me again...with good news (for me anyways). I was FINALLY able to get my system to update to 2004. Unfortunately, I don't have a "step by step" details, but that's only because of the many, many attempts and iterations of attempts that I have made to get through this. I lost count, but I'd say I've invested 50+ attempts and failures, but finally, all is as it should be.

As with many others in this thread and others throughout the Microsoft Community, there's definitely something up with the update process and Microsoft should be ashamed for such garbage. Still, here we are...supporting ourselves.

Anyway, as part of my continued attempts to complete this update, I came to discover the CBS.log contains entries referencing the same files as this URL (https://answers.microsoft.com/en-us/windows/forum/all/srmscandll-and-srmclientdll-repeatedly-corrupted/8de9b202-d706-4e1f-8c2b-7e5419075d06). Even though this problem was happening with someone already using build 2004, I figured I'd give it some reading. While reviewing, I learned that this problem was caused by a utility within a toolset I use on a daily basis, so I figured it may be related to my troubles not being able to get to 2004. After removing the File Services Manager MSC from the RSAT toolset, I was able to complete the SFC /SCANNOW without problems. Previous to this, each time I attempted SFC, I was presented with the "found problems and corrected them"...I was under the impression this correction was the result of failed update attempts.

After resolving the srmscan.dll and srmclient.dll problems (entirely), I attempted another update via Windows Update (built into Windows 10). Wash, rinse, repeat...it failed (again). I completed DISM repairs, SFC and the removal of the SoftwareDistribution folder...nothing new there. I checked the setupact.log and setuperr.log and THERE IT IS...finally something in the setuperr.log file stood out. Other than the "normal" errors, there was now this mention of:

Failed to get driver info from driver package C:\Windows\System32\DriverStore\FileRepository\dellaudioextwaves.inf_amd64_b522e3d1357bfe2b\dellaudioextwaves.inf. Error: 0x800706BE[gle=0x0000007a]

This entry didn't exist in previous setuperr.log files, but I can't say why other than perhaps it had to do with the srmscan and srmclient files. I attempted to remove the Realtek (MaxxWave) audio drivers from my system and retry the 2004 update, it failed again. Once again, I repeated my "cleaning" procedures and see the setuperr.log file still included this entry, so I took ownership of and FULL CONTROL permissions of the entire C:\Windows\System32\DriverStore\FileRepository\dellaudioextwaves.inf_amd64_b522e3d1357bfe2b
folder, deleted everything from within as well as the folder itself and tried again...only this time I used the Update Assistant tool (instead of running Windows Update from within).

Oddly enough, my first attempt seemed to get stuck on 77% for what seemed like an eternity (maybe 45 mins)...I was about ready to throw in the towel for the day (try again tomorrow), when the the system successfully restarted. Twice. After the 2nd restart, I signed in and was met with "Hi". And this is where I experienced an "oh ****" moment...it just sat there, with a blank screen...it never advanced to the "we have updates for you" and I thought I was in BIG TROUBLE. After 30 minutes of nothing, I fat-fingered the system down, took a deep breath and powered it back on...I sign in, get the "hi" again, all the subsequent "notices" and make it to the desktop environment. I checked the OS version and see Build 2004. I conducted a manual Windows Update and applied the one related to .NET for build 2004, shut down and headed home.

Here I am, 2 hours later, typing this out (while it's still somewhat fresh in my mind). Hopefully this helps others partly or entirely...even with my rambling...if anyone reading this needs clarification, please don't hesitate to reach out.

Good luck.

I downloaded this update yesterday and it only took me 2 hours.

Sadly, when I rebooted my laptop to install the updates it stuck at 30%  more than 30hrs now.

I don't know should I cancel it or not because I use my laptop for studying and other important stuffs, and now I have done nothing these two days.

I think they should work on this because it doesn't make any sense to stop everything you need to do with your computer/laptop for more than 30hrs just to install a single update.

It seems apparent that something is wrong with the update process. I have had customers shut off their machines and start it up from power-up. One was able to restart, the other I had to do the update from a flash drive. This is mind-boggling. I have not had an update to take more than 25 minutes on my computer. On the customer that I used the flash drive, it took two hours! This is ridiculous! If you don't mind, do you know what update you are try to install? I ask because this thread was started June 13, and it was for the May 2020 update. I have not heard any flack from the August 2020 update..., yet. So are you installing the August update?

I downloaded this update yesterday and it only took me 2 hours.

Sadly, when I rebooted my laptop to install the updates it stuck at 30%  more than 30hrs now.

I don't know should I cancel it or not because I use my laptop for studying and other important stuffs, and now I have done nothing these two days.

I think they should work on this because it doesn't make any sense to stop everything you need to do with your computer/laptop for more than 30hrs just to install a single update.

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.

“still not even a spark of support from MS.”

I have submitted this question on my feedback pages at least 3 times, and I have not heard anything back. I thought that, being an Insider, I would be the one with the problems, but all of my updates go perfectly. I don’t believe in “jinxes”, but I sour hope I haven’t “jinxed” my future updates!!!

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