• henfredemars
    link
    fedilink
    English
    arrow-up
    71
    arrow-down
    1
    ·
    11 months ago

    Just to provide another data point: I’ve had bad Windows updates render my machine unbootable too.

    • emptiestplace@lemmy.ml
      link
      fedilink
      arrow-up
      45
      arrow-down
      1
      ·
      11 months ago

      And then you’re left searching for bullshit error messages and potentially unable to fix the problem regardless of your level of expertise.

      • Siegfried@lemmy.world
        link
        fedilink
        arrow-up
        12
        ·
        11 months ago

        I’m sorry, something went wrong. Here is all the information we can give you about it: “:(”

        • Riskable@programming.dev
          link
          fedilink
          English
          arrow-up
          10
          ·
          edit-2
          11 months ago

          Hah! Can someone here chime in and tell me when the slow AF (as in, it can take hours) rollback feature actually worked

          Who TF is that patient‽ You can reinstall Windows and all your apps in half the time required.

        • verdigris@lemmy.ml
          link
          fedilink
          arrow-up
          10
          ·
          11 months ago

          Windows recovery fails in plenty of circumstances, it’s not a magic bullet. Snapshots are like you can do with btrfs, but that’s not exactly how Windows recovery works.

        • AlphaAutist@lemmy.world
          link
          fedilink
          arrow-up
          5
          ·
          11 months ago

          Sure if it fails completely it will, but it doesn’t catch everything. Here’s a related story I have:

          At work we had a bunch of Lenovo X1 Carbons running windows that would have the usb-c ports die seemingly randomly on users which was a big problem since that’s also the charging port. There never seemed to be any similar root cause connecting the incidents and Lenovo’s support wasn’t any help. Our entire company is remote but luckily we had onsite support so for a while they would just come by and replace the whole motherboard each time.

          Finally one day while scheduling a repair the support guy I was talking to just said, “Oh I’ve seen this before. It’s just a bad update and resetting the CMOS battery by putting a paper clip in this hidden hole fixes it.” We had the user try it out and the ports worked fine again. Apparently they had run some windows updates that failed silently and were causing the hardware issues.

          From then on any time a user has had a hardware issue we can’t figure out we just have them try the reset and it has worked every time. This only happens probably 3-4 times a year but we only have less than 40 of these machines so not an insignificant amount.

    • viking
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      Yep, same. Last time that was under Windows 7 though. I believe it was some .NET update. I managed to uninstall it in safe mode, spared me the fresh install.