• Arcane2077@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    11 days ago

    You’re describing pretty much every used PC in existence. It’s hard not to come to the conclusion that there is no issue and that one guy’s SSD just failed like they do

    • Lvxferre [he/him]@mander.xyz
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      11 days ago

      and that one guy’s SSD just failed like they do

      As mentioned in the article, “others have also encountered the same issue”.

      It’s hard not to come to the conclusion that there is no issue

      This assumption would not explain the surge of complains about it.

      And my point is that Microsoft doesn’t fucking care. Regardless of if it’s its fault or not.

      • Arcane2077@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 days ago

        I’m not sure about that. There isn’t any evidence, that I know of, of a surge in complaints. Just a surge in reporting because one person blamed the update. storage fails all the time, so complaints are naturally constant.

        • Lvxferre [he/him]@mander.xyz
          link
          fedilink
          English
          arrow-up
          2
          ·
          10 days ago

          Here’s my hypothesis: from a quick websearch, a lot of people are getting error messages from this update (regardless of disk failure), it’s around 3GiB large, and classified as a security update. It’s possible that the system is trying to install it over and over and over, and this is unnecessarily stressing storage devices that would eventually fail anyway.

          If my guess is correct there is a higher amount of complains, not just reports, but Microsoft won’t find the cause.

          Of course, it’s just a guess - I don’t know if it’s correct.