• @[email protected]
    link
    fedilink
    English
    911 day ago

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

      • ditty
        link
        fedilink
        English
        271 day ago

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

        • @[email protected]OP
          link
          fedilink
          English
          361 day 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.

          • @[email protected]
            link
            fedilink
            English
            111 day ago

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

            • @[email protected]
              link
              fedilink
              English
              1023 hours 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.

              • @[email protected]
                link
                fedilink
                English
                116 hours ago

                Even security updates can be uncritical or supercritical. Conault the patch notes or get burned lol

            • @[email protected]
              link
              fedilink
              English
              10
              edit-2
              1 day 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.

      • @[email protected]
        link
        fedilink
        English
        -116 hours ago

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

          • @[email protected]
            link
            fedilink
            English
            15 hours ago

            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?