Microsoft can and does do plenty wrong, there's no question on that. You are not alone, but - if you are going to quote articles, at least ensure they contain real unknown problems.

I clicked on every article on the page your provided and skimmed them. All but one were valid known issues. The Symantec thing was mentioned on all of them as an issue (which has been a known issue for months). The issues with the memory buffer are purely bad code on app developers that lead to buffer overflow security holes (of which Microsoft is quite guilty of in the past).

One issue I agree that they did FUBAR is the support for RAW sockets. I don't understand why they took it out when the attack surface there now is just as easy to break and only requires an extra step or two to get around. All it does is break the apps that use it.

Don't get me wrong, Microsoft does plenty of crap wrong, but I just don't think they screwed up SPXP2. I think for the vast majority of consumers that the pros of increased security are worth far more than the cons of updating software to adhere to good security practices. I do agree however that corporations need to excerise caution and test very thoroughly - but Microsoft even throughout the beta cycle (I was in the beta test group) has VERY clearly told IT profs that we need to test carefully.