Yes, MS uses many standards. But all too often, they ignore an existing standard, and go off to their own little world and create their own rules. They create their own nonconforming, proprietary standards that are more-or-less similar to existing worldwide standards - but they're owned and controlled by MS. It's the "Not Invented Here" syndrome. Somebody else invented it, so we don't want it.
Last year, when the government insisted on compliance with published, available standards, we had the ISO OOXML debacle in Norway. XML already existed as a standard, but MS went their own noncompliant way, and then used their power and influence to badger an approval for an incomplete, ambiguous, inconsistent mess.
"Don't believe the hype?"
Ask yourself a question - why do web designers need to check the browser, and adapt the page rendering based on the browser? Then ask the REALLY important question - WHICH browsers need special accommodations? Answer: MSIE lives in its own little world, and there are even differences now between IE6, IE7, and IE8; if a developer wants to have the page render correctly, extensive processing is required to satisfy IE's version-specific peculiarities.
Safari, Opera, Firefox, Chrome and many more all play by one set of rules. IE plays by a different set of rules.
Microsoft Office lives in ITS own peculiar world, and each version of that suite creates files incompatible with the previous versions - 95/97/2K, or 2003, or 2007 are all different. Again, there are worldwide standards available, but MS doesn't work and play well with others.
Yes, some standards become better as they grow. But there is a civilized way to do it. And going off into your own little corner, and trying to badger the rest of the world play by your rules, is not the way to accomplish it.
"Get along with others." Not "MY way or the highway."