thier botched patch caused BSODs everywhere. Desktops, servers, ( and embedded devices?  donno ).  Talking to our server guys, the fix is reboot in safe mode, login with local admin, remove a file, reboot.     Not hard but requires touching .. and time..   so remote users, are f-ed and  have to come in. And if you dont have remote KVM switches, VMs, or whatever on your servers, people are going to be digging out crash carts and spending the weekend in the data center..

And ya non-windows OSs were exempt from this.  Or if your machine was off during the update window. ( which apparently saved my VM at home, and my VDI session, tho we couldn't access our PDCs from AWS for most of the day, so they were still in effect, dead. )

Sat Jul 20 2024 07:17:27 EDT from darknetuser Subject: Re: Happy "Global Blue Screen Of Death" day, everyone!

What happened?

And speaking of windows and VMs

Seems this apple i have from the shop and running a win10 VM. its only a gen 6 CPU so no win11 VM for me ( its only a couple of years old... the last of the Intel powerbooks .  Intel was shipping past gen 10 .. what is up with that, Apple? )

and trusting a cloud service for something so critical 

Sat Jul 20 2024 12:39:54 EDT from IGnatius T Foobar Subject: Re: Happy "Global Blue Screen Of Death" day, everyone!

Can we agree to blame both?

We can blame Crowdstrike for pushing bad code without proper testing and staging. We can blame Microsoft for publishing an operating system so fragile that it crashes at the drop of an electron. And we can blame IT consumers for continuing to accept the worst operating system ever built.

Reports are estimating 8.5 to 9 million machines cloudstrike directly hosed.  No way to count indirect effects due to services being down.

If they still exist in 6 months, ill be surprised.

LoL. M$ is now blaming the EU regulations.

"the forced us to allow 3rd parties to integrate with windows. If we could just force everyone to use MSDefender this would never have happened, so its their fault"