Seems like MS could have worked the bugs out before releasing it...
And thereby change corporate policy on releases ...in our dreams! The new "patch" ( damn near anew OS in the way it works ) generally wreaks havoc with all "objects" ...I was talking to a guy at a major security company ( size of s*mantec ) who is responsible for the roll out of the installation at his place ...the list of what it breaks is humungous ...but for most home users they will not notice until they try to use something that Redmond didn't make ...like Martini busters list ...
Not much point in being a partner developer ( adobe , macromedia et al ) with M$ if they trash your app very time they patch their code ..
There was a vicious article in the Times (of London, the "real" one :)) about XP SP2, and how it can cause your computer to crash. According to the author, MS response was that "it was a simple manual port opening", but couldn't tell him what that meant!
...(Microsoft) has already begun releasing fixes for problems that the mammoth update can cause, however inadvertently. The company has issued what is likely the first of several "hotfix" patches, which developers and analysts say are just a fact of PC life.
Security researchers inspecting a new update to Microsoft's Windows XP found two software flaws that could allow virus writers and malicious hackers to sidestep new security features in the operating system.
My dad always told me never to buy the first iteration of a vehicle, as they always seem to have problems. Same seems to hold for the first version of MS patches.
Most of the problems listed are caused by the XP firewall being turned on by default. Any other firewall or program that uses a non-standard port will have problems. The fix is simple as MS puts a temporary icon in the task bar for adjusting the security features. The first thing I did on all five installs was to shut off the XP firewall. It's only half of a firewall anyway. The next thing I did was to shut down and rename the old MSN messenger. I did the updates on the 10th and 11th and have not had a single problem with any of the programs on any of the machines. Of course I don't have AOL of any of the machines.
<Knock on Wood> no errors for me w/ my SP2 test machine. It's doing a lot better than when I tested it with a beta release. Still... I just can't believe that they are having problems with such prominent applications! Looks like a BIG lack of planning.