• MonkderVierte@lemmy.ml
    link
    fedilink
    English
    arrow-up
    68
    arrow-down
    1
    ·
    11 hours ago

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

      • ditty@lemm.ee
        link
        fedilink
        English
        arrow-up
        20
        arrow-down
        1
        ·
        7 hours ago

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

        • superkret@feddit.orgOP
          link
          fedilink
          English
          arrow-up
          15
          ·
          7 hours ago

          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.

            • SomeGuy69@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              26 minutes ago

              For 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.

            • mosiacmango@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              1 hour 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.