It seems the architecture of Windows and its backward compatibility are a growing burden on Microsoft's shoulders.
The sad truth in software business is that you don't have to make your product robust enough to last forever, just long enough for you to pocket your bonus and retire.
I also have a problem with the idea that security bugs are not ordinary bugs. Bugs are parts of the program that don't do what should be done, be it about crashing, corrupting data or handing over the keys to your kingdom, they are still bugs and should be detected and corrected.
You just said absolutely nothing about security flaws OR QA. You want to try again? Because I think all you've got here is, "bugs should get fixed". Yeah, you got me there.
If their QA can't find security bugs, then, perhaps, they should rethink what software quality means to them. Remember: even if bugs costs them millions of dollars, they cost even more to their customers.
Your claims about QA and security are so wildly outside my own experience and the general understanding of my field that I'm wondering where you get the confidence to make them so forcefully. I've never met a QA team anywhere that could reasonably be left responsible for testing software security.
Still, none of the security problems I wrote into my code could be blamed on highly adversarial conditions - all of them were plain bugs, places I forgot to do something or when I trusted something one should never trust.
The fact you never met a QA team that could uncover security problems possibly stem from them not looking into the code itself and never having the responsibility of finding such problems. Validating compliance, correctness of observed behavior and even user overall experience is also called quality assurance, but it is, by no means, defining of the whole software quality concept.
Because I'm telling you that you're wrong about the relationship between QA and security in the real world.