SP2… Great for security and protecting users but at what cost?
So I just installed Build **** of XP SP2 and I honestly can say that the improvements Microsoft have made for security and protecting users is great. I think it’ll help my Mom from getting herself into trouble. But at the same time it’s more than safe to say that Microsoft got way way ahead of itself in even thinking they had a post RC1 interim build on their hands. At best RC1 is more like Beta 1 and **** is like an interim build leading to Beta 2. It’s truly pathetic, and I’m glad that SP2 has been delayed since these crappy issues need to be resolved otherwise SP2 will soon be SP2a. First thing I did after I did a clean install of XP Pro a week or so ago on my Inspiron 8600 was install SP2 RC1… What happened? Well only two of my 6 system tray icons would load. I’d get service errors, My Network Places and Network Connections would never come up, and loads of other BS problems. So I immediately uninstalled it. I’m happy to say that **** seems to be working okay on the laptop now… But of course all isn’t Bliss with SP2… I installed it on my 2004 MCE. On first boot some of my system tray icons were missing. Quick Launch was missing and every other toolbar was turned off. That was a bitch because I had to rearrange all the icons I keep in my quick launch. Then I noticed Synergy wasn’t working even though I did get the prompt to unblock it and did. So I tried pulling up the settings for ICF but what do you think happens?
—————————
Windows Firewall
—————————
Due to an unidentified problem, Windows cannot display Windows Firewall settings.
—————————
OK
—————————
Great… What a pile of cow dung. I’m going to reboot right now and hopefully I’ll actually get to change my firewall settings, otherwise screw it, who needs security when I can’t even control that security I’ll just uninstall SP2 (note: I’m being facetious and I don’t actually mean that). 
[UPDATE: Well as I expected but hoped wouldn't be the case, the Windows Firewall settings still cannot be displayed. And the problem really is unidentifiable since the error doesn't even show up in the Event Viewer. 
]