question

ACScot-9161 avatar image
0 Votes"
ACScot-9161 asked Jason-MSFT commented

KB5004424 July Servicing Stack Missing in SCCM

The latest servicing stack for Windows Server 2019 doesn't seem to be coming through to SCCM.

https://support.microsoft.com/en-us/topic/kb5004424-servicing-stack-update-for-windows-10-version-1809-july-20-2021-7806589c-e612-4ca2-a4f9-766f4c8098cd

Does anyone else have this issue? Other servicing stacks and updates are pulling through as normal, i have run multiple software update syncs and checked that the correct update types are selected against the site settings.

mem-cm-updates
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jason-MSFT avatar image
1 Vote"
Jason-MSFT answered Jason-MSFT commented

Per the KB you linked to, this update is not published to the WSUS catalog. Since 1809 is well past its end of life, this makes sense.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Windows Server 2019 is still supported until 2029

0 Votes 0 ·

Sorry, you are correct, I was focusing on Win 1809 from the title of the KB article. Either way though, the update isn't published to the WSUS catalog.

0 Votes 0 ·
ACScot-9161 avatar image
0 Votes"
ACScot-9161 answered Jason-MSFT commented

Thanks, I missed that it wasn't listed as available on WSUS.

It's strange because the patch it superseded (KB5003711) is showing in SCCM (via WSUS) and it shows as superseded so that's what led me down the path looking for this. Perhaps MS will be address in due course.

Thanks again

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

That I don't know as it's at the discretion of the team that owns and publishes the update. On occasion, things do get published incorrectly, in this case though my guess is that they chose this because of the EOL of 1809.

You can manually inject updates from WU into WSUS which will then carry over to ConfigMgr so this isn't really a show-stopper.

0 Votes 0 ·