So the other day, I had a client with an HP Desktop computer that was the victim of a harsh malware attack. So harsh in fact that it had to be reinstalled. So I installed from the recovery partition, and then went to update to SP3. Upon reboot, it bluescreen’d and then would just keep bluescreening. Soooo, thinking that the SP3 install bombed, i re-installed from the recovery AGAIN, and then tried SP3 again… And it bombed again! Wow, so I’m thinking now its no longer a SP3 fail. I did some research and found this site. (Click here to see it.)
Turns out if you have one of these HP desktop machines with a AMD processor you need to follow the steps mentioned in this page above BEFORE installing SP3. Its specifically a registry edit that has to be made so the SP3 doesn’t trigger installing an Intel file, thus causing the bombfest after the SP3 install.
You still learn new things all the time doing this stuff. Jeesh…
Weird, so is it all AMD and sp3? why just HP? some lame OEM piggyback software that comes with them that interferes?
Its related to HP only because HP decided to use the same installation windows image for many different types of PCs.. Laptops, desktops, etc etc. So an image was used on these AMD machines that was possibly created on a machine with an Intel chip… Using that image on a machine with an AMD chip causes some files to not work right after the servicepack etc. The link to the info also provides more explaination. HP making shortcuts…
Weird, so is it all AMD and sp3? why just HP? some lame OEM piggyback software that comes with them that interferes?
Its crazy…. Took a lot of my time researching this to figure out what the hell was going on. Check the links etc that I posted for more info on it. Its because companies like HP/Dell, etc etc etc all release their machines with basic images that they use across a lot of different machines instead of images made for each specific machine… And how those images interact with the OS and hardware inside.