Desktop platforms Toolkit

Story: AMD systems thrown by XP SP3 update

• 
• 

Wet ....

Although the cause of the problem is the use of OEM installtion disks intended for Intel computers on AMD computers, either by OEM's or by individuals using unsuitable branded OEM installation disks, Microsoft have known about this issue since 2004.

Clearly these faulty computer installations will still be around in significant numbers and, knowing this, Microsoft should have provided a simple work around to overcome the problem, not least in their own interests since they will now be heavily criticised anyway, notwithstanding that the original sin isn't actually theirs.

Microsoft's advice in kb888372 is only of value if the problem is known to the invidual (unlikely in most instances) before attempting an SP3 update since after a failed update to SP3, access to the computer, even in safe mode, appears to be impossible.

For those with a little (or a lot) more skill, it may be possible to effect a repair using the Console, Ultimate Boot Disk or similar. Maybe even using a Live Linux disk - something I have done to effect a repair or recovery on a number of occasions.

As I understand it, the problem is exacerbated by a change in the name of the AMD driver whereby SP3 only sees, recognises and updates the inappropriate Intel driver, which shouldn't even be on the computer, hence it installs and configures the updated Intel driver(s) without recognising and updating the AMD driver(s). Clearly a big no no!

In conclusion, Microsoft appear to have slipped up badly notwithstanding that they have previously pointed out to OEM's the error of their ways. Microsoft had the knowledge to have ensured that SP3 recognised these particular systems and installed correctly .

• 
• 

• 
• 
• 

Full Talkback thread