571
Sysadmin shock as Windows Server 2025 installs itself (www.theregister.com)
submitted 2 years ago by to c/technology@lemmy.world
94 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 95 points 2 years ago (12 children)

Misleading title. It was installed by a third-party updater, Heimdall, but MS labeled a Windows 11 update wrong.

  • permalink
  • fedilink
  • source
  • hideshow 12 child comments
    •
  • [–] [S] 119 points 2 years ago (7 children)

    They labelled an OS version upgrade as a security update.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 27 points 2 years ago (5 children)

    Yet another reason to not do auto-updates in an enterprise environment for mission-critical services.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 41 points 2 years ago (4 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 12 points 2 years ago (3 children)

    Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 11 points 2 years ago*

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 7 points 2 years ago (3 children)

    Wrong.

    Microsoft labelled the update as a security update

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] -3 points 2 years ago* (last edited 2 years ago) (2 children)

    Do you know that's not a mistake and done fully malicously knowing that? Please give me your source.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 2 years ago* (1 child)

    Read the fucking article.

    The patch id couldnt be any clearer.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] -3 points 2 years ago* (last edited 2 years ago)

    And you make absolutely no error?

    Besides that:
    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?

  • permalink
  • fedilink
  • source
  • parent