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(192, 28.999999999999996%, 28%)' 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)
Hi!
I have an issue with receiving updates via SCCM on devices running Windows 10 1809 LTSC and Windows Server 1809 LTSC.
OS installed with clean image, SCCM agent installed.
Update KB5005112 (service stack) is installed via SCCM. But device does not receive any latest updates. Software Center is empty. According to the logs no updates are required.
At WSUS server these devices need updates. If I switch devices to WSUS, they easily find and install any updates.
If I manually install any update released after August 2021, device immediately begin to recieve latest updates.
Updates for MS Office and dot net installs with no problems. Other devices with different OS versions in our infrastructure receives updates with no problems.
We have problems with Windows 10 1809 LTSC and Windows Server 1809 LTSC only.
I tried to remove SUP role, WSUS server, reset site - it didn't help us. SCCM version 2403.
Can anyone help me?
Managing and deploying updates via Configuration Manager
Other Configuration Manager-related features and issues
Hi, @Alex
Thank you for posting in Microsoft Q&A forum.
Do you have other LTSC version of windows 10?
Like Sherry mentioned, do you have the latest CU for windows 10 1809 synced to SCCM console?
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
Yes, I have a lot of updates for LTSC version, like KB5046615.
I have windows 10 1809 LTSC only.
![](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(243.2, 88%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
Alex, did you get this issue resolved? I have the same problem.
I'm going to start by asking the extremely stoopid question...
In your CM Console, All Software Updates, if you search for (for example) 1809, you DO see something like "2024-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5046615)"
We have a few 1809 LTSC, and that is the specific update that those Windows 10 1809 LTSC boxes want in my environment. Asking because perhaps what you are missing in your CM environment is enabling the Product of "Windows 10 LTSB" within your Administration, Site Configuration, Sites, right-click / Configure Site Components, Software Update Point, the Products tab.
Hi!
Yes, I have a lot of updates for LTSC version, includes KB5046615, in my CM Console. And "Windows 10 LTSB" enabled in Products tab.
Hi!
Yes, I have a lot of updates for LTSC version, includes KB5046615, in my CM Console. And "Windows 10 LTSB" enabled in Products tab.
ok, sorry, that was my only idea; sure sounds like a scanning issue then. Do you have multiple SUPs in your environment? maybe 'the one' that your LTSC boxes scan against didn't (don't) sync in the LTSC updates? Could look at your SUSDB on that box, make sure the update is listed, and not listed as expired? One would think that wouldn't/couldn't happen, but if you have multiple SUPs, maybe the top level SUP is fine, but some 'forgot-about-it' WSUS Cleanup script is running on the down-level WSUS/SUSDBs, to expire those updates locally, so you wouldn't see that at the CM primary site level?
I could see that happening inadvertently--a cleanup script running on a susdb, since 'cleaning up' "anything 1809" could be happening, automatically expiring those, because they are '1809', and the cleanup script doesn't "oh, except when LTSB, those do not expire".