Well, the Crowdstrike driver isn't (wasn't?) static. It loaded a file that Crowdstrike changed with an update.
Most drivers pass through rigorous verification on every change. But Crowdstrike is (was?) allowed to change their driver whenever they want by designing it to load a file.
MS tried to use the incident to get the regulators to waive the requirement.
Only because OP didn't give the full story. Microsoft wanted to close direct access to the kernel. AV companies complained to regulators in the EU. The EU asked Microsoft if they were willing to maintain access to replacement functionality and to stick to using that functionality for its own separately sold AV products. Microsoft said no, and instead of fighting, just let Windows wither on the vine with full kernel access for all the bozos. Crowdstrike was inevitable.
Do you like nanny states? How about nanny corporations?
So, it’s more like “you don’t get to improve your product if doing so would also stop random companies from forcing your customers to break the stuff you sold to them”
Microsoft has no right to prevent its customers from having full access to the things they bought.
Must human arms be braced at birth so they can only point level, lest someone try to point any object at their own foot?
In fact, I pay taxes to the police and they generally handle this sort of thing pretty well.
How did crowdstrike end up crashing windows though?