• Infynis
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    5 months ago

    Two layers of popups before I even see the page is too many, but isn’t the issue resolved? Do they just mean it’ll take time before all the individuals hosts are rolled off the failed update?

    • Snot Flickerman@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      13
      ·
      5 months ago

      The purpose of those popups is a special “Fuck You” to Europe for enforcing privacy rules. They make it painful on purpose, out of spite.

      I’m so sick of these worthless fucking techbro responses to regulation.

      • theshatterstone54@feddit.uk
        link
        fedilink
        arrow-up
        3
        ·
        5 months ago

        Wait, wasn’t the “Reject” button supposed to be CLEARLY VISIBLE and NOT hidden or obfuscated under a “Manage options” button? If I’m wrong, the law should be changed imo

    • ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
      link
      fedilink
      arrow-up
      7
      ·
      5 months ago

      Updating individual machines is a long manual process:

      The file in question is a CrowdStrike driver located at Windows/System32/Drivers/CrowdStrike/C-00000291*.sys. Once it’s gone, the machine should boot normally and grab a non-broken version of the driver.

      Deleting that file on each and every one of your affected systems individually is time-consuming enough, but it’s even more time-consuming for customers using Microsoft’s BitLocker drive encryption to protect data at rest. Before you can delete the file on those systems, you’ll need the recovery key that unlocks those encrypted disks and makes them readable (normally, this process is invisible, because the system can just read the key stored in a physical or virtual TPM module).

      https://arstechnica.com/information-technology/2024/07/crowdstrike-fixes-start-at-reboot-up-to-15-times-and-get-more-complex-from-there/