Microsoft has a great technical breakdown of the CrowdStrike incident. The root cause is an access violation in CrowdStrike’s kernel mode driver.

There are valid reasons for security software to run in the kernel but it causes such bugs to be fatal. Key takeaways

1. It’s unlikely Microsoft will make OS changes to prevent this from happening as it also restricts CrowdStrike’s security product.

2. There were inadequate testing and deployment practices at CrowdStrike.

https://www.microsoft.com/en-us/security/blog/2024/07/27/windows-security-best-practices-for-integrating-and-managing-security-tools/

Windows Security best practices for integrating and managing security tools | Microsoft Security Blog

We examine the recent CrowdStrike outage and provide a technical overview of the root cause.

Microsoft Security Blog
@carnage4life
Wild to me that Microsoft is either too lazy to create a safe and effective solution and/or is too scared of complaints from CrowdStrike et al, and (allegedly) the EU regulation body if they do so
It seems some product decisions at MS are driven by what is effectively customer lobbying.
“Don’t do X, that will mean we have to spend money to change our product”
MS: “ok sure”
@drewpickard @carnage4life You can still generally run Windows 1.0 programs on modern Windows. Microsoft spends an ungodly amount of money ensuring that anyone who has ever developed for a MSFT developed OS will never have to update their software again if they don't want to.

@foxxtrot
I swear they spend more resources on that then making it better.

I know for a fact that they also take A LOT of money via service agreements form certain enterprise companies to ‘maintain' old software, which also includes compatibility.
I wouldn't be surprised if their “we'll pay you to make it not change" money was larger than every other Windows revenue source
(why do you think IE was around so long?)