Originally Posted by
LIH Prem
The issue is that HP used a single binary image on their intel and AMD based systems, and though it was benign in SP2, it isn't benign in SP3. You have to remove a driver, otherwise the system won't boot.
This isn't all that uncommon a thing to do when building an OS image; we do it all the time across desktops and laptops from different vendors to deploy an upgrade for clients. Sucks that SP3 breaks it, but it seems like the workaround reg key is pretty simple to deploy, as is a GPO setting to fix the security zones thing, but I am definitely happy that others are discovering these issues instead of me.
