February 12, 2010, 3:40 PM — I so didn't need this. I'm a long way from my home office and I helped some family members to update their Windows XP PCs with February's massive set of Windows patches. Since they fixed a lot of serious bugs in these patches-including the one Google blames China for and the 17-year old security hole -- I figured this was a must patch job. What could go wrong? Lots.
One of the XP PCs started having BSODs (Blue Screen of Death) even before it could properly boot up. Two others booted up just fine, but then Windows Explorer started locking up. I needed this like a hole in the head.
It turns out I wasn't the only one seeing BSODs in the aftermath of this XP fix. Many others are seeing the same kind of XP lock-ups. So, if after you patch your XP system and you then reboot to see a message like the one below:
STOP: 0x00000050 (0x80097004, 0x00000001, 0x80515103, 0x00000000).
Congratulations and welcome to the party. You're in good company.
At this time, Microsoft hasn't released a fix.
Nevertheless, there is a way to get around this problem. First, it appears that the bum patch is MS10-015: Vulnerabilities in Windows kernel could allow elevation of privilege so you don't have to try to track down which of the more 11 XP patches is the trouble-maker.
To get rid of it, you'll need an XP boot CD or DVD. Or, you can boot from the Recovery partition on your PC. Don't have any of that? Ugh. Then, you've got real problems. You can try calling Microsoft support at 1-866-PCSAFETY, 1-866-234-6020, or 1-800-936-5700 in the Canada or the U.S. Good luck with that.
In my case, I was lucky enough to have packed my handy-dandy DVD pack, which includes a copy of XP SP3.
After you boot up you then start the recovery console. From there, head to the
Repair Screen and type the following commands:
1. CHDIR $NtUninstallKB977165$\spuninst
2. BATCH spuninst.txt
Then, reboot normally, and all should be well.
This also fixed my locked up copies of Windows Explorer.