Great!
I have an issue with HP using the same image for AMD and Intel PC's
That's a little lame...I love the HP products though!

I just ran into this problem on an HP Media Center PC with an AMD processor. You can avoid the problem by changing a simple registry value before starting the install. Here's how to do so:

1. Go to Start > Run and type regedit, then click OK

2. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm

3. Double-click on the "Start" value and change the number from 1 (or whatever number it's on) to 4, and click OK

4. Close regedit, and proceed with the service pack installation

If you already installed the service pack and are stuck in an endless reboot, try to boot into safe mode and do the same steps listed above, and you should be up and running again after another reboot. I was able to boot into safe mode on mine, but I'm told some people can't even get that far. If you can't get into safe mode, you will either have to run HP's recovery program on your PC (which by default is supposed to leave your data files intact) or find a computer geek who knows how to modify the registry by other methods. The latter would be preferable since the restoration methods HP provides generally cause far more problems then they solve.

Whoa, slow down there. First of all, I do agree that this should have been an easily-detectable problem, and the fix is also super-easy. However, if you're looking for somebody to point fingers at, point them at the OEMs who are too lazy to use separate images on their systems. It is common knowledge that OEM systems come overloaded with bloat that almost nobody wants or uses. This includes boatloads of hardware drivers, in addition to applications. There is no reason whatsoever why an Intel processor driver should be running on a PC with an AMD processor. Even if they wanted to use one image, there should have been a way to run a startup script that activated or deactivated the drivers based on what CPU it detects in the system. All those unnecessary processes loading at startup take memory and other resources that bog down your PC's performance. It's for this reason that I refuse to recommend any OEM systems unless I know that they have an option to come without all the unnecessary bloat. But regardless of that, this has absolutely NOTHING to do with playing CPU manufacturer favorites, or anything of the sort.

Ultimately, I'm not sure who's to blame: Microsoft, the OEMs, or both. All I know is that the fix is easy, and could be released via a windows update patch that is flagged as a required prerequisite for installing the service pack on the affected systems. I imagine something like this will happen soon, as this is certain to affect quite a large number of PCs. In case you missed it, be aware that HP is not the only OEM that is affected by this bug.

Be aware of the fact that even though I run a hp machine, that this is a not a OEM problem. I got my hp as a doa, I installed a new disk and installed a oem version of windows xp home on this machine. It only knowns it is a hp machine by the start window. I run 3 hp machines the same way. Without a doubt hp runs a amazing amount of bloat ware with its own software. My machines were originally me, and anybody that has used me will tell you the issues that the software had. I am currently running a recovered emachine with its original version of xp. It is painfully slow and the simple reason is the emachine bloat ware with ghost. I intend to remove the ghost with a clean install of xp oem to cleanse the vermon that infest it. One cannot blame hp for the processor they chose or the mother board to a degree, when running microjoke software the issue stops at home. Microjoke did not do their homework again. I clean machines for relatives all the time. I have spent 100's of hours on all types of machines. I will admit that 20% of the time bloatware and unneeded software can be to blame for slowness of xp, but I consider microjoke update to be little more than a virus until I see it work. This is not the first update that has caused problems, and it will not be the last. One should consider ANY update as a cause for issues. Microjoke is not alone when it comes to bad updates. I pay for software with problem updates. Microjoke should be testing this software before they release it on the general public. I have always set up problem computers to download microjoke updates auto. Thursday I had to call all those people and tell them to change their settings. I have lost complete faith in the very company that created the software that I use. One can only use good judgement in any download update. Burn me once shame on me. Microjoke has burnt me many times.

Yes I got the problem and I had to restore my computer to its factory state.I will not download SP3 nless microsoft fixes the problem.

I had the problem with the HP/AMD combo. I was able to boot into Safe Mode and restore to the point set before the installation.

NEVAH be a Crash Dummy for a Service Pack! Read the forums first!

Those who do not remember the past are doomed to repeat it!

I even check on individual ''Critical'' updates to see of known issues or if it even applies!