Not getting much by Googling.
If not, what’s the ETA?
They are still waiting to receive a properly formatted ticket through official channels before they will start working on it.
- there are currently two (?) fixes
- “You memorized your BitLocker key, right?” – physical access to the computer to boot into safe mode, delete a file, and reboot
- “Thoughts and prayers” – let the computer keep rebooting until it manages (somehow) to grab the fix in the lag or delays between reboots
Everyone in my very large company shares the same bitlocker key for some reason. I guess for today is the reason
It’s really up to the individual organizations to fix. There’s not going to be some global “congrats, we pushed and update and now everything is fine” patch, because the crash is preventing a patch from being loaded. It requires manual intervention on every single affected machine. If it’s a large organization with a lean IT team, that could mean days or weeks until every single machine is actually fixed; They’ll be prioritizing the mission-critical systems, so they’ll triage. Start with the wide reaching systems, then the most important employees. The intern will just have to wait.
It’s ok, it was just Windows machines. Nobody in their right mind would run anything critical on a Windows machine.
Omg… I hate Microsoft and windows as much as the next guy but for the last time this isn’t a windows problem ffs. Read any of the thousands of articles published on the matter and you’ll find that this theoretically could just as easily happen to Linux machines if they were managed by Crowdstrike - which is the problem.
This never ending Linux elitism on Lemmy is making me tired, boss
I don’t know if I could have made it more obvious that what I said was a joke. But also, it was a Windows problem in that it only affected Windows machines, and that was the premise of my joke (which is why I phrased it that way).
