• MonkderVierte@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 days ago

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

      • Appoxo@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 days ago

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

          • Appoxo@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            0
            ·
            6 days 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?

      • ditty@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 days 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
          0
          ·
          7 days 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.