It’s the first time that a number has been put on the glitch that is still causing problems around the world.

Microsoft says it estimates that 8.5m computers around the world were disabled by the global IT outage.

It’s the first time a figure has been put on the incident and suggests it could be the worst cyber event in history.

The glitch came from a security company called CrowdStrike which sent out a corrupted software update to its huge number of customers.

Microsoft, which is helping customers recover said in a blog post: “We currently estimate that CrowdStrike’s update affected 8.5 million Windows devices.”

  • magikmwEnglish
    14·
    2 months ago

    You need to boot into emergency mode and replace a file. Afaik it’s not very automatable.

    • Jtee@lemmy.worldEnglish
      12·
      2 months ago

      Especially if you have bitlocker enabled. Can’t boot to safe mode without entering the key, which typically only IT has access to.

      • magikmwEnglish
        7·
        2 months ago

        You can give up the key to user and force a replacement on next DC connection, but get people to enter a key that’s 32 characters long over the phone… Not automatable anyway.

    • HeyJoe@lemmy.worldEnglish
      6·
      2 months ago

      Servers would probably be way easier than workstations if you ask me. If they were virtual, just bring up the remote console and you can do it all remotely. Even if they were physical I would hope they have an IP KVM attached to each server so they can also remotely access them as well. 450 sucks but at least they theoretically could have done every one of them without going anywhere.

      There are also options to do workstations as well, but almost nobody ever uses those services so those probably need to be touched one by one.

    • prashanthvsdvn@lemmy.worldEnglish
      2·
      2 months ago

      I read this in a passing YouTube comment, but I think theoretically be possible to setup an ipxe boot server that sets up an Windows PE environment and can deploy the fix there and then all you have to do in the affected machines is to configure the boot option to the ipxe server you setup. Not fully sure though if it’s feasible or not.