HP begs AMD PC owners to put XP SP3 on ice
sticky plaster patch
Hewlett-Packard has told customers not to install Windows XP service pack three (SP3) on AMD-based desktops until Microsoft and HP cough fixes to the endless reboot snafu that has wreaked havoc on PCs.
Microsoft confirmed yesterday that it was scurrying to patch the problem after hundreds of angry XP customers first grumbled about the sizeable cock-up last week.
"HP is working diligently with Microsoft on a software update and will be proactively distributing a patch this week through HP Update that will prevent this error from occurring," said the computer giant in a statement. "HP recommends consumers with AMD-based desktops wait until after HP's or Microsoft's updates have been deployed on their systems to install Service Pack 3."
Microsoft’s message board was, within hours of the firm pumping the operating system’s final service pack out to the masses, inundated with complaints about machines being crippled by the endless reboot cock-up.
On Wednesday HP, which is the world’s biggest computer vendor, posted advice on its website about its Pavilion and Compaq Presario desktop PCs:
“After installing the initial release of Service Pack 3 for Windows XP an error condition can occur. The Service Pack 3 update copies an Intel power management driver to the computer that was not on the computer before the update.
“During Windows startup, computers with AMD processors may experience a blue screen error,” it said.
That acknowledgement, which somewhat swerves any admission of guilt, follows Microsoft’s statement earlier this week in which it blamed OEMs for “improperly placing a Windows XP image created for an Intel-based computer onto machines with non-Intel chipsets”.
Notably, Microsoft avoided specifics on which computer manufacturers had been guilty of mistakenly loading the wrong Sysprep image on their machines.
Microsoft also confirmed – much to the chagrin of XP customers who have patiently awaited SP3 after its release was spurned by a Vista-centric Redmond several times – that the endless reboot problem first surfaced way back in 2004 when service pack two landed.
The error, it said, was brought on by an orphaned power management Intel-only driver (intelppm.sys) that remains in the Windows Registry when the wrong image has been loaded onto AMD-based machines.
However, customers have also complained that the glitch has occurred following the install of XP SP3 on PCs from Dell, Gateway and Lenovo, while others have suggested Asus chipsets have also been crippled by the reboot problems.
Unsurprisingly, AMD, HP and Microsoft have all claimed that the issues have been fairly limited to some desktop computers. But, as is often the case with this type of FAIL, no tech vendor has been brave enough to step forward to provide a definitive number of how many PCs have actually been affected by the issue.
HP said it hopes to push out a patch named SP37394 to customers within the next week. No word yet on when y’all can expect to see a fix from Microsoft, however. ®
SP3 adds drm that restricts DVD play back. I know this because when I tried to play ghost rider on my computer it bitched about copyright protection. I have a copy of sp2 on that same computer and it works fine.
Not so fast
The easy fix that you offered does not work. The intelppm driver was never active in my registry to begin with, so it doesn't have any effect on my Presario in enabling me to install SP3.
If it worked for you, then consider yourself extremely lucky. Most of us trying to get SP3 installed have already seen the BS about the intelppm driver and the quick fixes to disable it. There is more to the uninstallable SP3 issue than the intelppm driver alone.
I have seen other tech reports stating that this issue was raised by MS four years ago when the SP2 update was issued. However, it should be noted that a substantial number of XP users have long since had to reinstall XP on either a reformatted or replacement drive. I would wonder if this has any bearing on whether the SP3 update will take.
@Paul H, re "An intentional push to move from XP."
Well, Microsoft certainly succeeded in this case.
I finally gave up when the Windows update site claimed my HP OEM installed copy of XP was pirated.
You're telling me HP.com installs pirated copies of Windows on their Pavilion's, now?
I gave MS the Finger, popped in an Ubuntu cd, & rebooted.
Shrunk the MS partition down to almost nothing (~12Gigs on a 500Gig HD), let Ubuntu have the rest of the drive, and haven't rebooted to Windows since.
I have YET to find anything Ubuntu can't do that Windows can, besides running a few games I have no interest in playing.
Excel, Word, PowerPoint, Access? OpenOffice.
Outlook & IE? Thunderbird & Firefox.
Nero & MagicISO? Oh look, those functions are *built in* & accessible via a *right click* from the "File Explorer" (Nautilus).
Firewall, Antivirus, & Spybot were a *mandatory* constant-on with Windows.
In Linux, I don't need the firewall because the system doesn't leave those "doors" open for scum to enter.
Don't need an antivirus because you can't infect what you don't have permission to write to.
Don't need Spybot because you can't edit a Registry that doesn't exist.
Which means there's a few hundred MEGS of System RAM that gets dedicated to running what *I* want to run, and not what the OS "needs" to run in order to be secure.
My HP Pavilion a1132n (AMD 3500+ 2GHz, 2Gig RAM, ATI Radeon X600) runs MUCH faster now that Windows isn't my primary OS.
And I don't need MS screwing things up with a botched SP3, ThankYouVeryMuch...