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.
  • bamboo@lemmy.blahaj.zoneEnglish
    41·
    4 months ago

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

    Have you tried turning it off and back on again?

      • EtzBetz@feddit.de
        7·
        4 months ago

        Hey I rebooted 14 times now, just as you told me, but it’s still not working.*

        :D

    • Kissaki@beehaw.orgEnglish
      7·
      4 months ago

      No no.

      Have you tried turning it off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on again?

  • MagicShel@programming.dev
    39·
    4 months ago

    If this somehow works, good on Microsoft, but what the fuck are they doing on boot cycles 2-14? Can they be configured to do it in maybe 5? 3? Some computers have very long boot cycles.

    • vinniep@beehaw.orgEnglish
      58·
      4 months ago

      There’s nothing magical about the 15th reboot - Crowdstrike runs an update check during the boot process, and depending on your setup and network speeds, it can often take multiple reboots for that update to get picked up and applied. If it fails to apply the update before the boot cycle hits the point that crashes, you just have to try again.

      One thing that can help, if anyone reads this and is having this problem, is to hard wire the machine to the network. Wifi is enabled later in the startup sequence which leaves little (or no) time for the update to get picked up an applied before the boot crashes. The wired network stack starts up much earlier in the cycle and will maximize the odds of the fix getting applied in time.

      • MagicShel@programming.dev
        26·
        4 months ago

        That makes sense with how the article said “up to 15 times” which does sort of indicate it’s not a counter or strictly controllable process. Thank you!

      • EtzBetz@feddit.de
        6·
        4 months ago

        I was thinking (from reading the headline) that if one specific component fails 15 times during boot or so, it will just automatically get disabled by the system, so that you don’t run into an unavoidable boot loop.

        But this makes sense as well, if they did write “up to” in the article (as others have stated). Even though I find the confidence weird. Imagine you have some weird dial-up or satellite internet solution for your system, which just needs time to connect, and then maybe also just provide a few bytes/kilobytes per second. This must be rare, but I’m 100% confident that there exists a system like this :D

        Edit: okay, I should read first. The 15 times thing is said for azure machines.

        • darkpanda@lemmy.ca
          5·
          4 months ago

          macOS has something to this effect where if it detects too many kernel panics in a row on boot it will disable all kernel extensions on the next reboot and it pops up a message explaining this. I’ve had this happen to me when my GPU was slowly dying. It eventually did bite the dust on me, but it did let me get into the system a few times to get what I needed before it was kaput.

    • azerial@lemmy.dbzer0.comEnglish
      5·
      4 months ago

      Just imagine if it’s a build farm with hundreds of machines. Jesus. That’s a hell I wouldn’t even wish on my worst enemy.

  • 30p87@feddit.de
    18·
    4 months ago

    Well in the time until Windows rebooted 15 times Windows 12 will be out.

  • zephorah@lemm.ee
    8·
    4 months ago

    We did get 7 computers back by 1am last night just by constantly rebooting.

    That said, 40 out of 47 never came back. So clearly something more is needed.

  • gwindli@lemy.lol
    6·
    4 months ago

    there’s an easy fix. it could be done with a single boot attempt if M$ hadnt made it so needlessly difficult to enter safe mode

    • Norgur@fedia.io
      6·
      4 months ago

      Many of the machines in question will have safe mode walled off for security reasons anyway.

      • gwindli@lemy.lol
        1·
        4 months ago

        fair enough. i can see that disabling safe mode would be a decent security measure. but by the time that kind of exploit is used, you’ve already got bad actors inside your network and there are much easier methods available to pivot to other devices and accounts.

          • Scary le Poo@beehaw.org
            2·
            4 months ago

            Well then obviously you could opt to restrict safe mode on laptops only, or laptops and desktops allowing you to get your server infrastructure up quickly so at least the back end is running properly.

            Ffs.

  • Jimmybander@champserver.net
    4·
    4 months ago

    Most of our machines at my office run Win 10 or 11 and we haven’t had the blue screen. I was wondering why we hadn’t experienced this. Still don’t know.

    • zabadoh@ani.social
      4·
      4 months ago

      Azure is MS’s cloud computing. As long as you weren’t using MS OneDrive, or 365 Office, or something else that relied on MS cloud, you’re good.

      • Midnitte@beehaw.orgEnglish
        21·
        4 months ago

        Actually it’s due to whether your company uses CrowdStrike or not.

        The issue is not being caused by Microsoft but by third-party CrowdStrike software that’s widely used by many businesses worldwide for managing the security of Windows PCs and servers.

        Supposedly, one of the fixes (aside from rebooting and hoping it grabs the update fire) is to delete a single file in the CrowdStrike directory after booting into safe mode.

        • nutlink@beehaw.orgEnglish
          5·
          4 months ago

          I just spent the morning doing this with my help desk team, although we just do it via command prompt at the recovery screen. We’ve had a 100% success rate so far at 93 devices and counting. I’m glad our organization practices read only Friday, at least.

          • EtzBetz@feddit.de
            2·
            4 months ago

            Tbh, I would then also not update anything on Thursdays (which does maybe do overnight procedures) since it may be breaking over night then, leaving you just little time to fix before the weekend :D

            This kinda can be extended up until Monday, I know, but, at least in Germany, on Fridays people go home way sooner than other days.

        • Saik0@lemmy.saik0.comEnglish
          1·
          4 months ago

          Yes, but Azure platform itself was using it. So many of those systems were down overnight (and there’s probably still stragglers). The guy you responded to specifically called out Azure-based services.

          • Kissaki@beehaw.orgEnglish
            3·
            4 months ago

            Microsoft services were, in a seemingly terrible coincidence, also down overnight Thursday into Friday. […]

            A spokesperson for Microsoft told Ars in a statement Friday that the CrowdStrike update was not related to its July 18 Azure outage. “That issue has fully recovered,” the statement read.

            from https://arstechnica.com/information-technology/2024/07/major-outages-at-crowdstrike-microsoft-leave-the-world-with-bsods-and-confusion/

            They were not “using it”. And there’s no “stragglers still”.

          • Midnitte@beehaw.orgEnglish
            2·
            4 months ago

            Sure, but the OP of the thread didn’t.

            Most of our machines at my office run Win 10 or 11 and we haven’t had the blue screen. I was wondering why we hadn’t experienced this. Still don’t know.

            So it isn’t whether you’re using Azure, it’s whether you’re using CrowdStrike (Azure related or not)

            • Saik0@lemmy.saik0.comEnglish
              2·
              4 months ago

              So it isn’t whether you’re using Azure, it’s whether you’re using CrowdStrike (Azure related or not)

              No. Azure platform is using Crowdstrike on their hypervisors. So simply using Azure could be sufficient to hurt you in this case even if your Azure host isn’t using Crowdstrike itself. But yes, otherwise it’s a mix of Windows+Crowdstrike.

    • Flax@feddit.ukEnglish
      2·
      4 months ago

      Why bother encrypting passwords? Just store them in plaintext, preferably on a web server that’s publicly accessible so other services can easily access them.