Solved Updating KB5015814

I installed KB5015882 on my Win11 Pro Notebook an hour ago and not seeing any issue with it. I had done KB5015814 the same day as on my Desktop.

However, the sound device on this Notebook decided to fail last week and OEM will be getting a call under the terms of the Warranty. Some diagnostics say it's hardware, Hiren's Boot CD, couple versions of Linux can't see the adapter.

x BlueRobot said:

Addendum: The SFCFix tool which I prompted to use before does take ownership and change the permissions of the WinSxS sub-folders, however, promptly and correctly restores the ownership back to the TrustedInstaller.

Click to expand...

SO you say "never modify the WinSxS folder permissions" but you're suggesting I run some software that does exactly that? Even without the other risks associated with running an unknown .exe file from an unknown source, there's too much damage that something like this can do. Please stop suggesting I use SFCFix.exe, it's not happening.

glasskuter said:

That is certainly true. But it has not been someone, but a lot of someones on 2 consecutive cumulatives. The web and feedback hub tell the tale....and it's only with cumulatives. With normal update problems usually a reset of WU components fixes it. Not with this. I would hazard to say there are probably more Windows Defender users than third party AV users. They wouldn't be affected if my theory is true. Yes, I know it's a theory and out in left field.

I have kb5015882 waiting to be downloaded. I'm going to make another backup and go through the same song and dance again to see what happens, the whole thing from sfc, dism, reset WU, everything up to disabling AV and letting WU do its thing.

Click to expand...

I'm glad you agree with me! If one or two users had similar issues then yes it could be a user problem, but with the unusual number of people with similar issues with more than one CU, it's a problem beyond the scope of user's systems, something bigger is afoot.

BrianInEngland said:

SO you say "never modify the WinSxS folder permissions" but you're suggesting I run some software that does exactly that?

Click to expand...

Read the paragraph you quoted properly and my prior paragraph which mentioned the following:

And please do not - under any circumstances - take ownership or change permissions in regards to the WinSxS folder or the registry. You will not be able to restore these back correctly unless you use the APIs exposed by Windows.

Click to expand...

My point was don't take change ownership or change permissions via the GUI or through batch scripts, especially when most people don't actually understand why they're deleting a folder to begin with.

BrianInEngland said:

Even without the other risks associated with running an unknown .exe file from an unknown source, there's too much damage that something like this can do. Please stop suggesting I use SFCFix.exe, it's not happening.

Click to expand...

I never asked you again to use SFCFix, please point out where I specifically asked you to do so? And to answer your other two assertions: one, SFCFix isn't some unknown tool from an unknown source; there are several members of this forum which can attest to that. The only damage it can cause is when it is used by users who don't understand how to write appropriate scripts for it, just like many other tools, including FRST.

I'm not going to argue about this any further, however, you're always going to be running around chasing after Windows Update issues until you start reading the logs properly or actually looking at the logs to begin with.

Followup to my previous posts 33 & 40. To test my theory about third party AV causing problems with cumulatives and some sort of erroneous flag (or bit or whatever) getting set I first made a backup. I then let WU attempt to install this update. As with last month's cumulative, it failed. I then turned off MWB, it failed again. From there I ran SFC, DISM, and reset WU components. It still failed. I restored my backup and downloaded the cumulative from MS. Turned of MWB and manually applied the update . It succeeded.

It's still a theory and I'm not saying this will work for everyone, but it has for me...three times...with a cumulative preview and 2 consecutive monthly cumulatives. I've set myself a reminder to make sure going forward I pause updates the night before the next update Tuesday. Surely to the gods above, with the number of people having issues with these updates, at some point MS will figure out what is happening and fix this.