• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Worth the upgrade to SP3?

It's not an upgrade, so it isn't quite the same value comparison. It's a big maintenance patch, and if you're going to continue to run XP and want to get future updates and fixes, there isn't much choice.
 
Originally posted by: Markbnj
It's not an upgrade, so it isn't quite the same value comparison. It's a big maintenance patch, and if you're going to continue to run XP and want to get future updates and fixes, there isn't much choice.
Click to expand...

Yep, he's correct. There have been a ton of security and other update patches released since SP2 came out. SP3 rolls everything up into one convenient patch. That's why it's 320MB in size!

If you're building a new XP machine from scratch, loading up SP3 right off the bat will limit your Windows Update to two, maybe three download/reboot cycles before you're completely up-to-date/current.

I have SP3 slipstreamed into my XP CD. Makes loading up a new machine a breeze.
 
Yes, definitely. I've installed it on at least 50 machines including my own and no problems so far, its been great.
Someone even turned off the power while I was installing it remotely to a pc and after uninstalling the interrupted sp3 install, it worked fine after reinstallation!! i thought that was pretty amazing!
 
So far, every PC that I've patched to SP3 (mostly brand-new installations, going from SP1 to SP2 to SP3) have had failed Windows/Microsoft Updates after going to SP3. This is a well-known problem. For me, it's been a consistent problem. It's easy to fix, though, and I haven't seen any other specific SP3 problems.
 
Originally posted by: RebateMonger
So far, every PC that I've patched to SP3 (mostly brand-new installations, going from SP1 to SP2 to SP3) have had failed Windows/Microsoft Updates after going to SP3. This is a well-known problem. For me, it's been a consistent problem. It's easy to fix, though, and I haven't seen any other specific SP3 problems.
Click to expand...

What's the "easy fix"? I'm getting ready to replace a HD and load XP SP2 from scratch, and I plan to install SP3 via download right after that. What do I need to do to avoid the failed updates you mention above?

 
Originally posted by: Kazaam
I heard a few months ago it wasnt doing too well with AMD processors, is this still true?
Click to expand...

The issue wasn't directly AMD processors. It was with HP (and maybe some others?) machines that had AMD processors.

I've had no issues with about 20 home-rolled AMD-based PC's.
 
Originally posted by: Ken90630
What's the "easy fix"? I'm getting ready to replace a HD and load XP SP2 from scratch, and I plan to install SP3 via download right after that. What do I need to do to avoid the failed updates you mention above?
Click to expand...
While there are tougher ways, and some folks list a dozen DLL files to register, the following DOS command has fixed every "broken" SP3 PC I've encountered so far:

"Regsvr32 Wups2.dll"

No reboot needed.

Here's a TechNet Forum post that says the same thing.
 
Originally posted by: RebateMonger
Originally posted by: Ken90630
What's the "easy fix"? I'm getting ready to replace a HD and load XP SP2 from scratch, and I plan to install SP3 via download right after that. What do I need to do to avoid the failed updates you mention above?
Click to expand...
While there are tougher ways, and some folks list a dozen DLL files to register, the following DOS command has fixed every "broken" SP3 PC I've encountered so far:

"Regsvr32 Wups2.dll"

No reboot needed.

Here's a TechNet Forum post that says the same thing.
Click to expand...

Thanks. :beer:

As I understand the sitch as it applies to new installations of XP SP2, the problem only manifests itself if the user doesn't reboot the machine after installing the O.S. and then downloading the latest Window Update client. So long as the user reboots after installing the client -- before trying to install SP3 or other updates -- the new Wups2.dll file will be enabled (aka "registered") and all will be well. Correct?

If you don't mind me asking, where did you find the info about that command you mentioned above? I'm seeing several other commands in Microsoft's Article # 943144 (linked to in that TechNet thread), but I'm not seeing the specific one you mentioned. And is entering that DOS command only necessary if the user hasn't restarted their computer after installing the latest Windows Update client (before going back to the Update site)? Or does that command need to be entered anyway?
 
Originally posted by: Ken90630
[As I understand the sitch as it applies to new installations of XP SP2, the problem only manifests itself if the user doesn't reboot the machine after installing the O.S. and then downloading the latest Window Update client. So long as the user reboots after installing the client -- before trying to install SP3 or other updates -- the new Wups2.dll file will be enabled (aka "registered") and all will be well. Correct?
Click to expand...
I don't know for sure. I'm PRETTY sure that I had at least one PC that was rebooted several times after SP2 was installed.

At first, we weren't going to install SP3, and we installed a couple of rounds of updates for SP2. Then we had a change of heart and installed SP3 from the .MSI file....and Windows Updates quit working after the reboot. That's my recollection, anyway.

I really can't testify to exactly how to cause this failure. But I know that myself and many other IT consultants have seen it. And the "fix" I mentioned has worked each time for me and for others.
 
Okay, cool. That MS article on this subject isn't written very clearly IMHO, and I had to read it a couple times to fully grasp what they're trying to say. It seems to be kinda unnecessarily complicated if, like you say, all you have to do is open a command prompt and type in "Regsvr32 Wups2.dll." I think I like your way better. :thumbsup:

BTW, to your recollection, have you only experienced the issue when trying to install SP3 without having the latest Windows Update client installed on the machine? That article makes it sound like that's the only time it happens, but since the Windows Update site basically 'forces' people to have the latest client if they don't already, before they can install any Win Updates, you'd think the problem would only occur when the person is installing SP3 immediately after an XP2 installation (or repair) without having visited the Windows Update site and then rebooting. As I understand it, that's when the problem manifests itself. Would you guess that's been your experience? Just curious.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top