The advice, which is specifically for virtual machines using Azure, shows that sometimes the solution to a catastrophic failure is turn it off and on again. And again.
  • Donut@leminal.spaceEnglish
    50·
    4 months ago

    “We have received feedback from customers that several reboots (as many as 15 have been reported) may be required, but overall feedback is that reboots are an effective troubleshooting step at this stage."

    A lot of liberties taken with that headline.

  • Vik@lemmy.worldEnglish
    12·
    4 months ago

    Is anyone able to read the full article? Is this a boot loop OS detection feature?

    • PineRune@lemmy.worldEnglish
      21·
      4 months ago

      I saw in another thread: sometimes upon booting, the updater has just enough time to grab the fixed update before BSOD so keep trying.

      I saw some SysAdmin threads as it was happening say to boot into safe mode, navigate to the affected file, and delete it.

      • MajorHavoc@programming.devEnglish
        13·
        4 months ago

        boot into safe mode, navigate to the affected file, and delete it.

        Yeah. That’s the easiest, unless the drive is encrypted.

        I imagine the folks going for the 15 reboots approach are doing so because it’s easier than waiting in line for their IT help desk to deliver them their boot encryption key.

        • Revan343@lemmy.caEnglish
          4·
          4 months ago

          it’s easier than waiting in line for their IT help desk to deliver them their boot encryption key

          Especially when the encryption keys are all stored on a Windows server that’s bootlooped

      • Vik@lemmy.worldEnglish
        1·
        4 months ago

        I haven’t been affected by this personally, just curious at this point what the variables are hah

    • mkwt@lemmy.worldEnglish
      20·
      4 months ago

      Sounds like a race condition in a kernel driver. Try it enough times and maybe you can get clear of it once without triggering.