Re: The fault's with Microsoft
Okay, here's a better explanation of why you are wrong...
An operating system would be pretty useless if it could only run software provided by the provider of the OS (although MS would probably love this, I shouldn't give them ideas).
So, third-party software is allowed. For obvious reasons, it can't go near OS functions.
Similarly, the OS should be able to run on a wide variety of hardware (unless you are Apple). It should not be incumbent on the maker of the OS to provide drivers for that hardware, so third-party drivers are needed.
Those drivers need to have low-level access to parts of the OS, so the OS needs to trust them. This applies equally well to any general-purpose OS, not just Windows.
Sadly, software flaws exist. Again, it would be poor form to not allow third parties to provide defence against these.
Low-level system and antivirus software needs to interact with OS functions at a low level, so the OS needs to trust them. Again, this applies to any general-purpose OS.
So, you have a situation where the OS doesn't normally allow access to, or interference with, some of its functions, except where it has to, in a limited way, for trusted third parties.
CrowdStrike is (was?) in this instance a trusted third party. Now, trust in computing is a whole PhD thesis topic of its own, but your argument essentially boils down to a claim that MS is in the wrong for trusting CrowdStrike, whereas the more nuanced argument would be that CrowdStrike is in the wrong for not living up to the terms of that trust.