Yesterday, September 26, 2012, I updated my Spybot 1.6.2 as I do every Wednesday. I usually choose the Giganet mirror from the list of update sites, but it was not on the list yesterday so I chose SecurityWonks.net#1 (USA). There was only 1 file listed which was a 2MB file, which I downloaded and was installed. I rebooted into Safe Mode and ran my scan. It came back clean, so I rebooted. At this point, when the computer restarted it could not boot into Windows. It just goes into an endless loop of restarts once it gets to the point where Windows would normally load and take you to the desktop screen.
I cannot get into Safe Mode either as it does the same thing of the endless reboot. The first computer this happened on was a family member's which I had updated. I did not know there was a problem at that point because after I did the scan and rebooted, I left. It was a short time later when I was told that their computer was doing this continuous reboot thing and at that time I didn't know that the Spybot update was the cause.
When I got home I had to update my Spybot and do my weekly scan, so I did, and the exact same thing has happened to my computer. I updated from the same SecurityWonks.net#1 (USA) mirror and after the scan was complete and I rebooted, my computer is doing the same endless reboot that my family member's computer is doing. The operating systems for the 2 computers are XP Home and XP Pro, both with SP3.
It appears that the 2MB Spybot update file on the SecurityWonks.net#1 mirror for September 26, 2012 is infected with a virus or malware or is corrupted in some way and now I have 2 computers that I cannot use at the moment. Can you look into this immediately and let me know how to proceed to correct this as I have two computers that I cannot use at this time as a result of this issue.
This is the blue screen error message I get:
Stop c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of
0xc0000135 (0x00000000 0x00000000) The system has shut down.
quirky1 on the Anandtech security forum is also having this issue "I have the same problem after downloading and scanning with Spybot. In my case the update file was downloaded from Safer-Networking mirror #2 and the resulting status code is 0x00000080. There is yet no mention of this problem in the Safer-Networking Forums. It appears Spybot has corrupted something. I don't understand how a simple scan with no problems found can cause this..."