Originally Posted by mymiles2go

I disagree, I think if you dig down to those 4 or 5 you'll probably find known issues. Quite honestly Microsoft just can't solve every problem. You will have vendors who write crappy code that in order for items to be more secure you have to break. Microsoft even broke thier own code on the Great Plains crap with XPSP2 in order to make things more secure. I just as much as you would love Microsoft to release a product that's perfect every time. But by my count on this thread only two people had BSOD problems - of which it could very well be (and probably is) something as simple as a driver. Yes, that may be unacceptable but it's quite likely fixing one thing will only break another. You then have companies like IBM who very clearly decided to not participate within the development cycle like every other company - hence why you see them saying "Slow down folks", on the opposite end of the spectrum you have Symantec - who's software was broken by SP2. But they apparently worked with Microsoft for upwards of a year in preparation of this even to be sure that when SP2 was released that it could be remedied quickly and easily. And while the Symantec thing sucked, both parties were at least responsible about it.

Btw, you can disable the firewall in a single click after the XPSP2 install, and WMP10 isn't in XP2