Well, Microsoft is at it again! Nothing is more frustrating than when you apply updates, or Microsoft does it for you in most cases, so that your system will be more safe or run better and then find that it breaks your system!
This is what happened this week with the latest round of patches on Patch Tuesday.
Here is what happens. You see the little message from Microsoft in your system tray that tells you there are updates available to install. You blithely tell it to do so and off it goes. Everything seems to have gone just fine, and you are told you need to reboot your system to finish the updating process. Even though you’re busy and facing deadlines, you figure you might as well get it out of the way. Don’t want any hackers getting into your system! Windows shuts down and starts to reboot.
Suddenly, one of two things happens. Many machines will stall and come up with the Blue Screen Of Death (BSOD) and tell you that Windows has been shut down to prevent damage to your system. Some systems are configured to automatically reboot when a BSOD is encountered. This is even more frustrating because your system will go into an endless loop of rebooting.
The infuriating thing about this situation is you can’t even boot into Safe Mode to try and fix anything. Your system is completely unbootable.
Well, the problem seems to be with the MS10-015 patch. Ironically enough, this was supposed to patch a vulnerability in all 32-bit versions of Windows that has been out there for 17 years!!!! You can read about the patch and what it was supposed to fix here: Microsoft’s Fatal Patch
If you have a computer with a DVD or CD drive, you may be able to extricate yourself from this disaster without reinstalling Windows. If you have one of the new Netbooks that have no optical drive, you may be out of luck unless you can find someone who can make a bootable USB drive for you.
Here is what you need to do:
1. Insert your Windows XP CD into the drive and reboot your computer.
2. When it says press any key to boot from the CD, press the any key! 🙂
3. Wait for the CD to boot to the screen where it gives you the option of running the Recovery Console.
4. Press R to go into Recovery Mode
Your screen will turn black and you will be asked which Windows you want to log into. Usually pressing the number 1 and then the Enter key will be ok.
5. If you have a password on the account, you will be asked to enter it here. If you don’t know what it is, you’re screwed unless you have a bootable CD that lets you remove the passwords on Windows accounts.
6. When the command prompt appears, you need to enter the following commands:
After you enter each line, press the Enter key before entering the next one.
When you press Enter after BATCH spuninst.txt, you should see some text come onto the screen before you’re allowed to enter the next command.
Now, type in EXIT and your system will reboot.
Hopefully, your system will now boot into Windows as it’s supposed to. The problem is, this update will be offered to you again and if you accept it, you’ll end up with the same problem again, so DO NOT accept this update! Hopefully, Microsoft will come up with a fix to their fix, but it will be too late to help anyone afflicted with the problem now.