Thankfully, I haven't been affected by this directly; the systems I manage in our cluster are almost entirely Linux, and the Windows systems managed by our central IT don't use CrowdStrike (think they use Cisco).
But it's a real mess they've made. It's reportedly fixable by booting in recovery mode and removing a particular file (
https://www.crowdstrike.com/blog/statement-on-falcon-content-update-for-windows-hosts/), but from what I hear, the problem some have with that (apart from the obvious practical issues, like potentially needing physical access, etc.,) is that if people are using bitlocker encryption, they need a recovery key, which makes things a bit more complex. And in some cases, apparently the admins can't access the recovery keys because they carefully stored them on a server that's now also inaccessible because of this problem. Whoops.