Windows 10 Feature Update 2004 taking too long to install

So I got back from holiday, and realised this update was automatically running as soon as I switched on.  Wow!  I thought there was something wrong with the laptop.  Every click on the mouse took ages to get a response.  The installation was soooo slow, it brought the machine almost to a standstill.  I did all the usual housekeeping things to clean it up, and then got fed up and a bit scared (I am not as computer literate as many of the subscribers are).  So now I've paused the update until the end of Oct in the hope the 2004 update may have become more user friendly.  Is that okay?  Does it matter if I'm still running on 1903?

It was an update for May 2020 (Windows 10 version 2004). Actually, I stopped the process and it rolled back to its' previous version.  I also checked if there is enough space before upgrading. Lastly, I used Windows 10 update assistant and everything went smoothly and easily in less than two hours. 

Glad you got it done.

It was an update for May 2020 (Windows 10 version 2004). Actually, I stopped the process and it rolled back to its' previous version.  I also checked if there is enough space before upgrading. Lastly, I used Windows 10 update assistant and everything went smoothly and easily in less than two hours.

Wow. I find your situation unique, and I'm sure everyone else hopes it's unique too! But your determination, and ability to relate this information is invaluable. 

In looking through your solution, and something stuck out to me. "DELL" was referenced in your streams about uninstalling the audio. It made me wonder if the issue may be related to prebuilt systems. HMJunior also referenced a laptop, almost assuredly prebuilt. The customers that I referenced were both prebuilt. My system,Ibuilt, and no update has failed. My second system, I built, and no issues. My two laptops, I rebuilt, and they both updated smoothly. Now, I'm gonna be bata$$ crazy until I figure out if this is a prebuilt issue. I'm sure not ALL prebuilds had issues, but I'm not sure if I saw any who explicitly stated DIY systems having this issue.

Lance, I'm glad you got it done, and hopefully, others with these issues can benefit from your detailed diagnostics.

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.