[2004, 20h2] Updates stopped - Servicing Stack Dependency

[CyBeRkId2002]

Hi all,

 

Just a quick sanity check and, hopefully, save someone the HOURS I have spent investigating this.

 

It seems that the cumulative Windows Updates, you know the ones that are supposed to be a bundle of all previous updates, are not exactly working that way. After finding a number of client had stopped updating recently - particularly those most recently imaged from our 20H2 base, I have spent hours trying to work out why. It seems that Microsoft have moved the Servicing Stack updates inside the Cumulative updates... but not made them cumulative. It seems that on our 20H2 clients if you don't have the May update (which by now will have automatically expired as superseded on SCCM/WSUS) then you cannot receive any future updates.

 

Has anyone come across this? I am just in the process of manually importing the May update back into WSUS to see if that kicks them back in to action but I do find it a strange move on Microsoft's part.

[Steve21]

Yep you're right. We've deployed it back out as a SCCM package to 20H2 machines so it'll force it down without having to leave them all unexpired/expired. Same issue if you want to upgrade them to 21H1 it stops it because of that issue

 

Steve

[CyBeRkId2002]

thanks for confirming!!! Glad I'm not going mad!

 

Was considering doing the pacakge and think it probably makes sense! How have you targeted clients? Created a group for those on a certain OS Build or put some kind of check in the application?

[Steve21]

thanks for confirming!!! Glad I'm not going mad!

 

Was considering doing the pacakge and think it probably makes sense! How have you targeted clients? Created a group for those on a certain OS Build or put some kind of check in the application?

 

I’ve got collections setup for win10 versions so I’ve just applied it direct to that collection. The application being a wusa.exe command etc to apply it

 

But no doubt you could script a check in if you don’t have any like that

 

Steve

[CHiLL]

Is this issue limited to just 21H1 or does it also affect 1909? I'm having issues doing in-place upgrades from 1909 to 21H1, where the TS fails instantaniously.

Looking at my servicing stack updates in SCCM, I can see that all of the monthly servicing stack updates are mared as "Is Deployed = Yes", though the actual numbers reported are odd, such as "Required" being 0, 1, 2,4, etc, and "Installed" also being low, such as 0, 3, etc (depending on the monthly update).

 

Actually, looking at the deployment summary - the Windows 10 Monthly ADR is reporting "Compliant = 4", "Non-compliant = 1" and "Unknown = 379". I don't know why it's showing all our clients as unknown, given that this ADR was updated in July, so should have pushed to our clients by now. On a client, there are no updates showing in the Software Center.

Edited August 10, 2021 by CHiLL

[1an]

Microsoft have released an update so you don't need the May update to be installed first.

 

For any missing the May or later updates install the standalone 10 August 2021 SSU - KB5005260. I've not tested this but the update is showing in my WSUS