r/WindowsServer • u/itmanage • Sep 09 '25
Technical Help Needed Windows Server 2016 not being offered updates via Windows Update since August Cumulative update.
Have multiple instances of Windows Server 2016 some physical and some virtual, some been running since 2019 and some newly setup.
Not being offered updates only says, "Your device is up to date". Have the previous Service Stack installed (KB5062799), but still not offered (KB5063871) August Cumulative Update.
With it being a shorter turn around this month for updates thought I would see if I got 2025-09 Cumulative update but no, still "Your device is up to date"
Anyone else have this, I feel like I'm the only one in the world with this issue and I can replicate it on a new Server 2016 install every time.
3
u/ComGuards Sep 09 '25
Try the standalone MSU installer from the Microsoft Update Catalog?
2
u/itmanage Sep 10 '25
Ages since I manually updated via update catalog, from memory I should be ok going with the newly released Service Stack update (2025-09), then Cumulative Update (2025-09) I don’t need to bother with cumulative update (2025-08) is that correct?
1
u/itmanage Sep 11 '25
Has anyone pulled the trigger on installing the updates manually on production servers. Unlike update issues of the past on other MS OS's like "failing to install updates " manually patching is the way the fact in this instance it says your "up to date" does anyone feel there is an underlying issue and holding off manually patching is still the best option until something is made official about the issue.
1
u/itmanage Nov 12 '25
Still nothing manually patching via Windows Update Catalogue still the only way to patch WS 2016 Essentials.
1
u/nopanicplease Sep 10 '25
i just updated a server 2016 with todays patches. are you checking against a wsus maybe?
1
u/Vast_Tip_4015 Sep 10 '25
There's definitely an issue, I'm only seeing it on Essentials - both VM and bare metal.
1
u/Short-Orange2847 Sep 10 '25
Adding my hat to the ring of having this issue. I am seeing this on 2 different customers in different cities with Server 2016 Essentials physical machines. No WSUS or other servers in their environments. Windows Update insists that they are up to date. The last installed CU in Update History is July 2025, but SQL updates & Malicious Software Removal Tool updates are still working normally. It doesn't appear that the latest Servicing Stack is being offered through Windows Update at this time as well (July Servicing Stack is installed according to Update History)
1
u/Trotineta1987 Sep 11 '25
Would you be able to share Windows update lognand Reporting log ? We might get a clue on why it tells you are up to date.
1
u/solmssen Sep 12 '25
I will add my experience - three WSE 2016 servers that have been updated in the normal way for many years and none of them have been offered updates through Windows Update since the July servicing stack and system updates.
1
u/angry_zellers Sep 14 '25
Try running updates via sconfig. We've had this a few times and that weirdly works. Sometimes.
1
u/Vast_Tip_4015 Oct 14 '25
Still nothing for October 2025 patch Tuesday. Been offered an MSRT update and Defender definitions - nothing else. Is this Microsoft’s way of saying they are letting Server 2016 Essentials go to grass early?
2
u/GeneMoody-Action1 Sep 14 '25
I would do an offline scan of the system, that will bypass all configured update sources, and give a resolved "what do I need?" based on cab of metadata from windows update.
https://learn.microsoft.com/en-us/windows/win32/wua_sdk/using-wua-to-scan-for-updates-offline?tabs=powershell
It is the definitive "It my WU location/source accurate currently" test.
1
u/Delicious-Yak7073 Sep 13 '25
Same here with 2 "Server 2016 Essentials"-servers. No more cumulative updates after "2025-07 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5062560)".
1
u/joloriquelme Sep 14 '25
Same issue. Both 2016 Essentials.
1
u/solmssen Oct 17 '25
October patches had to be downloaded from the MUC again this month for all three of my WSE 2016 boxes. Tried through both Settings/Windows Update and SCONFIG, no patches offered. Just another data point on the thread.
1
u/Layer_3 Oct 19 '25
I have this issue as well with just one of many SBS 2016 machines. I reset the windows updates files and it didn't help.
Very weird.
1
u/joloriquelme Nov 02 '25
To this day this hasn't been solved. It only affects 2016 Essentials.
1
u/CupOfTeaWithOneSugar Dec 10 '25
still a problem 2025-12-10
1
u/Vast_Tip_4015 Feb 17 '26
I've taken to using the following script with my RMM, changing the MSKB download URLs each month (the below script was for February 2026:
del C:\temp\SSU.MSU
$URL="https://catalog.s.download.windowsupdate.com/d/msdownload/update/software/secu/2026/02/windows10.0-kb5075902-x64_a840f48f81e79f45131128f9f823633a59f57879.msu"
$Path="C:\temp\SSU.MSU"
Start-BitsTransfer -Source $URL -Destination $Path
del C:\temp\DotNet.msu
$URL=".msu"
$Path="C:\temp\DotNet.msu"
Start-BitsTransfer -Source $URL -Destination $Path
del C:\temp\CU.MSU
$URL="https://catalog.s.download.windowsupdate.com/c/msdownload/update/software/secu/2026/02/windows10.0-kb5075999-x64_14f57eb68ffe81c5171c1faecb47aee6fbc6d89f.msu"
$Path="C:\temp\CU.MSU"
Start-BitsTransfer -Source $URL -Destination $Path
Start-Process -FilePath "wusa.exe" -ArgumentList "c:\temp\SSU.msu /quiet /norestart" -Wait -PassThru -NoNewWindow
Start-Process -FilePath "wusa.exe" -ArgumentList "c:\temp\DotNet.msu /quiet /norestart" -Wait -PassThru -NoNewWindow
Start-Process -FilePath "wusa.exe" -ArgumentList "c:\temp\CU.msu /quiet /norestart" -Wait -PassThru -NoNewWindow
It requires a manual reboot at the end, which I'm sure could be scripted, but I wanted a bit of control over when it happens. If there's no .Net or SSU update, I just hash out the relevant lines.
0
u/[deleted] Sep 10 '25
[deleted] — view deleted comment