“Labeling error”
Lol, okay.
Since rolling back to the previous configuration will present a challenge, affected users will be faced with finding out just how effective their backup strategy is or paying for the required license and dealing with all the changes that come with Windows Server 2025.
Accidentally force your customers to have to spend money to upgrade, how convenient.
Since MS forced the upgrade, you should get 2025 for free. That would probably be really easy to argue in court
Misleading title. It was installed by a third-party updater, Heimdall, but MS labeled a Windows 11 update wrong.
Wrong.
Microsoft labelled the update as a security update
Do you know that’s nor a mistake and done fully malicously knowing that? Please give me your source.
Read the fucking article.
The patch id couldnt be any clearer.
And you make absolutely no error?
Besides tbat:
Should MS have caught the errorenous ID (assuming it truly was errourneous and not knowingly falsely labeled)? Absolutely. Should the patch management team blindly release all updates that MS releases? No?
They labelled an OS version upgrade as a security update.
Yet another reason to not do auto-updates in an enterprise environment for mission-critical services.
In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates.
The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update.
Of all the people MS doesn’t want to piss off.
When the OS becomes the virus
When reading comprehension is limited to the title.
MS mislabeled the update
Heimdal (apparently a patchmanagement) auto-installed the falsely labeled update.If OP (this was reported by a Redditor on r/sysadmin) and their company is unable to properly set grace periods for windows updates I can’t help them either.
IMHO you are supposed to manually review and release updates either on a WSUS or the management interface of your patching solution.
Not just “Hehe, auto install and see what happens”.
And if you do that shit, set a timeout for 14 days at least for uncritical rated updates.They said they believe it was a mislabeled update. MS didn’t respond. Before criticizing others for their reading comprehension, I think you could work on yourself too.
There is a world, and it may be ours, where MS purposefully pushes this out. As the end of the article makes clear, this will be only a minor issue for those with good backup (which they probably all should but they don’t), but for those who don’t they’ll be stuck with the new version and have to pay for the license of it. This is a large benefit to MS while they also get to pretend like it’s just a mistake and not having backups makes it your issue, not theirs.
I’m truly, totally, completely shocked … that Windows is still being used on the server side.
We run a lot of Windows servers for specialized applications that don’t really have viable alternatives. It sucks, but it’s the same reason we use Windows clients.
You thought you were in control?
Our server, comrade.
