This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 40%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The latest servicing stack for Windows Server 2019 doesn't seem to be coming through to SCCM.
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.
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 83%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Windows Server 2019 is still supported until 2029
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.
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
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.