superkretSysadmin shock as Windows Server 2025 installs itself
Misleading title. It was installed by a third-party updater, Heimdall, but MS labeled a Windows 11 update wrong.
They labelled an OS version upgrade as a security update.
ddittyYet 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.
The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update.
Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first.
Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod.
We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues.
SomeGuy69For security updates in critical infrastructure, no. You want that right away, in best case instant. You can’t risk a zero day being used to kill people.
AppoxoEven security updates can be uncritical or supercritical. Conault the patch notes or get burned lol
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.
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?