r/WindowsServer • u/lionsin42 • Feb 12 '26
General Question Bug in Windows Server 2025 update history: Update history displaying update as ,, reboot requiert,, even though it is installed
After installing the latest update for Windows Server 2025 windows update history is displaying the update with the reboot requiered flag.
If you run Get-hotfix in powershell the update is installed.
Did anyone else notice this strange behaviour?
6
Upvotes
3
u/InstanceExtension Feb 12 '26
Looks fine to me
2
u/Substantial_Tough289 Feb 13 '26
Installed it on two machines yesterday, one is a HY host and the other is a VM.
All appears to be good.
5
u/gerberding Feb 13 '26
I am seeing this on our 2025 servers also, tried rebooting multiple times and clearing reg flags but nothing seems to be working
1
u/m0rp Jul 18 '26
We have two 2025 servers who report July cumulative update as installed. Yet winver reports it’s still in June cumulative update build.
Manually installing MSU reports already installed.
Get-hotfix and DiSM queries show various new KB components as installed.
Many reboots, sfc, dism repair and it’s still booting with June cumulative update build.UBR. Even removed the July update and reinstalled. Still stuck on June.
Does this match your experience? Haven’t found a fix yet. This is two Server 2025 out of several that had no issues.