• digdilem@lemmy.ml
    link
    fedilink
    English
    arrow-up
    31
    ·
    edit-2
    4 months ago

    It seems to be crowdstrike reacting to the new update.

    We have got ours up by the very manual process of:

    1 Boot into safe mode.

    1. Navigate to C:\windows\system32\drivers\crowdstrike

    2. Delete C-00000291*.sys

    3. Reboot normally

    • Potatisen@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      4 months ago

      Maybe a stupid question but why would not reaching an online service (?) blue screen your computer?

      • Ooops@feddit.org
        link
        fedilink
        arrow-up
        8
        ·
        4 months ago

        It’s the other way around. All those PCs are bluescreening at boot. So that prevents fixing the system remotely and on a large scale. Now poor IT guys have to fix evey single one by hand.

      • digdilem@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months ago

        It has a privileged service running locally - csagent.sys - that was crashing causing the BSOD.

      • Destide@feddit.uk
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        4 months ago

        Missing data in the boot sequence if that data is stored as a cloud init or a key is needed for auth during boot. So if you’re running thin clients and rely on something like Ansible, but now the thin client can’t get to the service it can’t boot, so critical error.

      • lmaydev@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        4 months ago

        I guess if the code acted as if it got a valid response without checking it could get into a very weird state. Or the code just fails hard.

        At the driver level it’s very easy to kill things.

  • DeltaTangoLima@reddrefuge.com
    link
    fedilink
    English
    arrow-up
    12
    ·
    4 months ago

    This has been a fun end to the week - still sitting on a call about the widespread outages and impacts from this.

    At which point do we acknowledge the cure is as bad as the problem?

    • Roopappy@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      ·
      4 months ago

      At which point do we acknowledge the cure is as bad as the problem?

      Didn’t we all do that when we stopped using Norton Anti-virus?

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    12
    ·
    4 months ago

    As a developer, man do people not realize how brittle modern computing is. It’s all built in popsicle sticks and Elmer’s glue. One small config or bad file as we see can cripple entire industries.

    I do love that windows is still like “something slightly wrong? Might as well crash”

  • qprimed@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    so it got backdoored, or QA is trash or both at the same time. hate it when CI builds come so fast you cant verify the latest shipping rootkit

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    This is the best summary I could come up with:


    There are reports of IT outages affecting major institutions in Australia and internationally.

    The ABC is experiencing a major network outage, along with several other media outlets.

    Crowd-sourced website Downdetector is listing outages for Foxtel, National Australia Bank and Bendigo Bank.

    Follow our live blog as we bring you the latest updates.


    The original article contains 52 words, the summary contains 52 words. Saved 0%. I’m a bot and I’m open source!