| Follow us on Twitter |
Microsoft identified the problem in a KB article as being created when an OEM uses an OS image for an AMD PC which should in fact be used on an Intel-based PC.
The problem that is described in the "Symptoms" section may occur if the original Windows XP Service Pack 1 (SP1) Sysprep image is created on an Intel-processor-based computer and if the Sysprep image is then deployed on a non-Intel-processor-based computer. Under this configuration, after the computer is upgraded to Windows XP SP2 or SP3, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image.
In an emailed statement, HP said the following:
The affected HP systems do not have an Intel driver loaded onto them, but there is a services registry entry that SP3 appears to be recognizing as an instruction to load the Intel driver, subsequently causing the failure.
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. 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 is also developing a prerequisite fix that must be downloaded before SP3 will automatically install prior to its proactive distribution of SP3.
The patch will be posted to this support page. There's no ETA on the fix.
For now, as the support page suggests, users can fix the problem by
* Disabling Intel Power Management
* Use Microsoft Recovery Console to rename intelppm.sys
* Details on the workaround are posted at the support page.
Source: By Tech Ex