It's far safer to operate on the assumption that MS is just through-and-through incompetent at this point than try and pinpoint the cause of any one problem in a long history of them. I gave up on them around the mid-IE days (think I might've been particularly miffed when they scrapped the Courier concept) but I haven't looked back and haven't regretted it since.
(Well, I doubt it, but there's at least a theoretical chance, right?)
If the code's retired, it could just as easily be because some inferior process led by devs without the proper guiding vision just swapped it out for some overengineered platform they 'know how to code in better' that's being hailed as the future of such-and-such that doesn't reimplement nearly as completely or robustly features that people had come to expect, and is less stable to boot. ("Secure time" [0] anyone?) But hey, just spitballing here.
MS is like the Hammer Industries of our world; never rely on Hammertech. Though I guess as long as they keep enough enterprise dinosaur contracts they'll keep limping on like Hammer too. shrug
I can belive the reinvented claim (that's the kind of thing a new, good CEO can influence), but quality goes very deep, into each employee. Any one hire can screw up fatally. It takes a lot of hard work to build a security conscious culture/company hierarchy.
(Edit: Hello Redmond people!)