Global IT issue strikes Windows machines, cause now linked to CrowdStrike software update

BSoD
(Image credit: Tom's Hardware)

Here's a quick explanation of what is going on.

In the late hours of July 18, CrowdStrike released an update which saw Windows machines BSoD (Blue Screen of Death) across the world. Initially this was reported as a Microsoft centric issue, with Azure and Office365 being impacted, but it later transpired that CrowdStrike's update of its Falcon Sensor which detects and reacts to threats to systems, was the cause. Official confirmation of CrowdStrike being the root cause has been made, and a workaround fix has been issued. Things are slowly returning to normal, but as each time zone wakes up, more cases are being reported.

Latest Videos FromTom's Hardware
Les Pounder
Associate Editor

Les Pounder is an associate editor at Tom's Hardware. He is a creative technologist and for seven years has created projects to educate and inspire minds both young and old. He has worked with the Raspberry Pi Foundation to write and deliver their teacher training program "Picademy".

  • Colif
    Its not always fun being first country in world to noitce

    Glad I went out this morning before all the banks stopped working.

    An update has been pushed out to fix the broken update.

    https://www.abc.net.au/news/2024-07-19/global-it-outage-crowdstrike-microsoft-banks-airlines-australia/104119960
    wonder what BSOD it causes.

    CrowdStrike CEO George Kurtz says the defect in the recent content update for Windows hosts causing the computing outages has been "identified, isolated and a fix has been deployed".

    Microsoft & Crowdstrike combo caused it.

    Internet was meant to be better than this.

    Hate to be flying as its effected airports worldwide.
    Reply
  • nogames
    What a great day :mad: First waiting to get my own company issued machine working (5 hours) and now I can see, that around 35 of our 60 Azure VMs are unreachable due to this. It seems like I will be working all weekend.
    Reply
  • bill001g
    It will never happen but a photo of the group who had primary responsibility for the update would be nice. They always post photos when things are good maybe some public shaming on twitter would good.

    Even if this company would pay for all the costs, and I bet the fine print says they pay nothing, this just causes the stock price to drop. Maybe that to a tiny extent hurts the top executives but they really need to do more so the end employees start to feel if they do a poor job there will be consequences.

    Just a sign of things to come with all the forced updates. Just wait until every pc in the world is down because microsoft just had to patch in their latest update to the mircosoft xbox client pretending it was a critical security update.
    Reply
  • yoji
    I am not a security expert, but is it time for Microsoft to be allowed to harden the kernel? There is no way any external program should be able to crash the machine. I know many of the security companies insist on hooks into core system components and antitrust rules obliged MS to comply/provide... but is it time to revisit?
    It wont protect us from MS messing up... but would be overall "better"?
    Reply
  • Pierce2623
    bill001g said:
    It will never happen but a photo of the group who had primary responsibility for the update would be nice. They always post photos when things are good maybe some public shaming on twitter would good.

    Even if this company would pay for all the costs, and I bet the fine print says they pay nothing, this just causes the stock price to drop. Maybe that to a tiny extent hurts the top executives but they really need to do more so the end employees start to feel if they do a poor job there will be consequences.

    Just a sign of things to come with all the forced updates. Just wait until every pc in the world is down because microsoft just had to patch in their latest update to the mircosoft xbox client pretending it was a critical security update.
    In the modern world, that’s the sort of thing that gets people killed. Let’s not post a picture.
    Reply
  • James Roach
    This was a really, really well written article. Covered all the bases of good journalism that are consistently missing across mainstream media. Well done.
    Reply
  • das_stig
    "By the time Crowdshite became self-aware it had spread into millions of computer servers across the planet. Ordinary computers in office buildings, dorm rooms, everywhere. It was software in cyberspace. There was no system core. It could not be shut down" psst Microsoft here our systems just BSOD, so we're OK.
    Reply
  • Vanderlindemedia
    And nobody in their right mind would even test before pushing an update?
    Reply
  • brandonjclark
    The fact is, SOMEONE signed off on a change ticket, and they should be fired, at the least.
    Reply
  • Makaveli
    Thankfully we don't use this in our environment. I woke up to my teams chat going crazy this morning and had to remind everyone we are good.
    Reply