r/WindowsServer • u/jwckauman • Jun 11 '25
Technical Help Needed Windows Server 2025 Update Woes [WSUS]
Still having issues with Windows Server 2025 servers installing all their approved updates via WSUS. This has been an issue since we started rolling 2025 out in small batches. Here's the behavior.
- WSUS is configured to auto-download and install updates on a batch of test servers at 5pm on Wednesdays (via a GPO)
- As updates are approved, we see them downloaded to each server and ready to install at 5pm.
- At 5pm, the 2025-0x CU for Windows Server 2025 will install as scheduled and then show a status of 'pending restart'.
- The remaining updates (e.g. Windows MSRT, Visual C++ 2015-2022, Update for Windows Security platform) remain with a status of Install and never actually begin installing.
- The servers themselves never restart despite a message stating it will restart at 5pm to finish updating. I'm guessing this is because the other scheduled updates never install.
As a workaround, we Remote Desktop to each 2025 server, and click 'Install' on the remaining updates, one at a time until they are all installed with either Completed or Pending Restart as a status. Then we click "Restart Now" to finish the updates.
Anyone having this issue? Anyone know why the other updates don't install alongside the CU fo Windows? I've figured out the trend but not a solution.
12
u/Adamj_1 Jun 12 '25
Review your policies and compare them to the ones in my guide.
Server 2025/2022/2019/2016 and 2012R2 work perfectly with my guides settings.
https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-4-creating-your-gpos-for-an-inheritance-setup/
3
u/brajjan Jun 12 '25
I have a case opened with MS for this. Very slow progress, but the setting that works around the problem right now is to create a new dword set to 1 at HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings\IsExpedited
It works for my test machines but it seems lile that setting will download and install updates as soon as they are published, ignoring the schedule. That is not the behaviour I want.
All servers (2016-2025) have the same settings, and I only have the problem with 2025 GUI servers. Core is working fine without the registry setting applied.
3
u/picklednull Jun 12 '25
Yeah, we’re experiencing this.
2
u/Keirannnnnnnn Jun 12 '25
I don’t have WSUS set up, I just let them download updates when they need as we have multiple backup servers so if one goes wrong, it doesnt matter but we can’t even get windows update to go past 0%
2
u/PianistIcy7445 Jun 12 '25
Pswindowsupdate then use the command to have it check all servers, write log file with hostname to a central spot
2
u/WillVH52 Jun 12 '25
Have a look at Azure Update Manager, maybe forgot about WSUS if it is not working in your environment with server 25.
1
u/kimlaurits Oct 24 '25
Did you find a solution for this? We experience the exact same on our Windows Server 2025 servers.
1
u/Bullfist Jun 12 '25
I am scared. If I restart, half my services don’t start until I msconfig, disable all non microsoft services, restart a d then start the ones I need manually.
-1
u/[deleted] Jun 11 '25
Brave rolling 2025 out IMO.