Microsoft 'resolves' and 'mitigates' Windows Server 2025 update whoopsie
- Reference: 1731334690
- News link: https://www.theregister.co.uk/2024/11/11/microsoft_windows_2025_mitigated/
- Source link:
The company updated its Release Health Dashboard over the weekend to [1]confirm that some devices were indeed upgraded automatically. The Windows vendor said: "This was observed in environments that use third-party products to manage the update of clients and servers."
"Please verify whether third-party update software in your environment is configured not to deploy feature updates."
[2]
According to Microsoft: "The Windows Server 2025 feature update was released as an Optional update under the Upgrade Classification: 'DeploymentAction=OptionalInstallation'.
[3]
[4]
"Feature update metadata must be interpreted as Optional and not Recommended by patch management tools."
The company's explanation is slightly at odds with the [5]experience of some third parties and administrators. According to cybersecurity biz Heimdal last week, the update had been misclassified and was subsequently pulled back by Microsoft. Additionally, a Register reader reported that a standalone server not running any third-party update services was also subject to a surprise overnight update.
[6]When Windows Server 2025 is delivered like it's 1999, nobody gets to party
[7]Microsoft still not said anything about unexpected Windows Server 2025 installs
[8]Sysadmin shock as Windows Server 2025 installs itself after update labeling error
[9]Buckle up, admins – Windows Server 2025 officially hits GA
Others observered that apparently dropping something which demanded a license payment into an update channel was poor form on the part of Microsoft.
Microsoft described the problem as "mitigated" but has yet to provide tools to facilitate a rollback, meaning affected administrators will have to reach for their backups or potentially pay for Windows Server 2025 licensing.
[10]
The company also marked another issue as "resolved," where an update to Windows Server 2025 was offered via a banner in Windows Update. Microsoft said: "This message is intended for organizations that want to execute an in-place upgrade."
According to Microsoft, it is "working with third-party providers to streamline best practices and recommended procedures."
El Reg asked Microsoft if a rollback tool would be made available and Heimdal if it recognized the Windows vendor's explanation. We will update this article should either company respond. ®
Get our [11]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2025#3404msgdesc
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZzI4NyqfLBQIO550D_-dxAAAAQE&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZzI4NyqfLBQIO550D_-dxAAAAQE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZzI4NyqfLBQIO550D_-dxAAAAQE&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://www.theregister.com/2024/11/06/windows_server_2025_surprise/
[6] https://www.theregister.com/2024/11/11/windows_server_2025_opinion/
[7] https://www.theregister.com/2024/11/08/windows_2025_surprise_install/
[8] https://www.theregister.com/2024/11/06/windows_server_2025_surprise/
[9] https://www.theregister.com/2024/11/04/windows_server_2025_ga/
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZzI4NyqfLBQIO550D_-dxAAAAQE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[11] https://whitepapers.theregister.com/
"working with 3rd-party providers to streamline best practices and recommended procedures."
Best practice #1 : don't include full upgrades in patch updates.
Any reg readers affected?
How widely is this a problem? I saw the update appear on one of my servers but just ignored it. Seemed odd but it didn't auto install, so not affected.
Granted, I'm not using a 3rd party update service, so I'm not one of those who would expect to be affected.
Anybody on here?
Re: Any reg readers affected?
Yes.
I have about 40 2022 installs, mostly VMs but a few bare-metal installs. All are updated by WSUS except for one standalone server (i.e. bare-metal install), which updates direct from Windows Update. It's not domain joined and just has local accounts. There is no third-party update management software.
When I logged into it yesterday afternoon to check something it was perfectly normal. I was already wary of the 2025 upgrade and checked the updates in settings to check that it wasn't showing as pending - which it wasn't, and neither was it showing as optional. This morning I logged into the server again, and overnight it had updated to Server 2025, so is now not activated. I have checked with the supplier of the main software used on it, and that does not yet officially support Server 2025 (I've done some basic testing and found no issues so far). Still debating what to do - I could reinstall it (we don't have backups of the OS drive as there's no data on there other than the OS and software) - but it seems fairly likely that if I did that, it would just upgrade again.
The WSUS-managed ones are not affected (checked them all) - let's hope that remains the case!
Profitable update?
1) update something against your will, 2) send bill for updated version.
Or: a) update something against your will, b) require hired guns to clean up the mess.
Or: I) update something against your will, II) send lawyers to blame someone else.
Many wonderful ways to make boatloads of money.