Who hates sp2?

I hate it! >
6,128 views 23 replies
Reply #2 Top
I haven't had any problems. I even made a Windows cd with SP2 slipstreamed into it, and unattended install. Works great.
Reply #3 Top
It's working well for me too.
Reply #4 Top
No problems here either. FWIW



Powered by SkinBrowser!
Reply #5 Top
I have no service packs installed, at all - so I guess I cant give an opinion...
Reply #6 Top
No Problems.....I disabled WB, Logon and got out of Litestep....installed it and restarted everything as usual.....zero drama....
Reply #7 Top
No problems, in least till my laptop started acting out. I'm still waiting for my laptop.
Reply #8 Top
No problems for me personally... Had to sort out a laptop which was taking 10mins to logon to the network today though. Soon sorted...
Reply #9 Top
I installed it and I had a few issues with XP behaving differently. So I uninstalled it.
Reply #10 Top
Works fine here... no issues whatsoever....
Reply #11 Top
It worked fine for me too.
Reply #12 Top
Ditto on the zero problems... Actually have installed in on a few small networks (my clients') and no problems whatsoever.
Reply #13 Top
No problems at all...didn't install it
Reply #16 Top
2 months here every thing as smooth as a babys bottom



Powered by SkinBrowser!
Reply #17 Top
No problems for me personally... Had to sort out a laptop which was taking 10mins to logon to the network today though. Soon sorted...


Fuzzy Logic, here is a tip I ran across for that issue..

You may experience extremely long delays (up to 5 minutes) when logging into domains using Windows XP Pro. This is caused by the asyncronous loading of networking during the boot up process.

This speeds up the login process in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready.

To disable this "feature" and restore your domain logons to their normal speed, open the MMC and add the group policy snap-in.

Under Computer Configuration> Administrative Templates> System>Logon, change "Always wait for the network at computer startup and logon" to ENABLED.

This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template.

Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.


As for me and SP2, no issues at all once the WB downloading as .zip file worked itself out.
Reply #18 Top
Works great....no issues
Reply #19 Top
Just installed it, Booted-up....everythings good so far
Reply #20 Top
....you use to say the same about me...
Reply #21 Top
Well! I don't fratinize with the citizens

WTH? where you demoted?
Reply #22 Top
I was a little nervous about trying it, since I'd heard some negative opinions on it, but I went ahead and bit the bullet about a month ago, downloaded it, and installed it. It's been working fine for me, I've had no problems whatsoever.
Reply #23 Top
No problems on my machine, in fact, everything works even better. The in many cases dreaded Internet explorer is faster, and I find myself using it a lot more now than I did before.

The main problem while upgrading to SP2 for most people, seems to be all the programs that are running during the process. To make the upgrade in less time and save yourself problems afterwards, unload Windowblinds, DesktopX, ObjectDock, virusprograms, firewall and whatever you can. I have done the SP2 upgrade on about twenty PCs or so, without major problems. After all, you can't blame Microsoft for not supporting old SCSI- & Legacy cards, network adapters and such, but for those with the time, knowledge and patience, even most of those issues can be overcome.

Hate SP2? I love it!