• 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.

      • 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.

      • 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.