It’s what happens when you put too many eggs in one basket. You see a similar house of cards when you look at package managers in the software dev space. Single point of failure.

The reality though is that Windows computers not running the CrowdStrike agent were not affected. This one falls on CS, but there is a much larger problem at play. Also, auto-updates are a plague, especially on a kernel level. That’s just insanity.

If you had a Samsung fridge, and you willingly put a bomb in the fridge, would you blame Samsung when your fridge explodes?

Microsoft gives you the freedom to install software that runs with the same level of privilege as the kernel itself. You're the one that chose to install defective software, and then give it kernel level permissions. You put a bomb in your computer and now you're blaming Microsoft after the bomb exploded.

Microsoft didn't make the decision to allow the faulty input, the person who installed the software did, when they gave it permission to run in kernel mode.

Most of who got hit though was people who contracted with crowd strike directly though. Its not like Microsoft pushed crowdstrike onto people.

Because Microsoft isn’t responsible for every program that runs on their OS.

CrowdStrike is an EDR that enterprises choose to install. The bug was caused by a dodgy content bundle update, which is something that’s meant to be 100% safe but evidently they found and triggered a bug.