The call generally goes something like this:
- A foreigner with a thick Indian accent identifies himself as a member of Microsoft Support or similar.
- He informs you that you have a number of critical problems with your PC and that you will need to have it fixed.
- To convince you, he offers to connect remotely and pulls up your Event Log (eventvwr.msc). He then filters for Warnings, Errors, and Critical events and uses that as evidence that your PC will soon fail to work correctly if you do not pay him to correct it.
The astute among you have probably already sensed that something here is seriously wrong, and it’s not your PC. It’s the fact that someone is calling you to tell you there is a problem with your computer. No one will ever do that. The only way they could possibly know there is a problem is by hacking or guessing.
In this case, it’s mere guesswork, and it’s not even correct most of the time. The Event Log is supposed to log warnings and errors, and even on the healthiest of PCs there are plenty of Error Events that can be safely ignored, as they often don’t amount to anything. The important thing to remember is to never trust someone who calls you about a problem with your PC, and never, EVER let them connect remotely to your PC.
If you do make the mistake of letting them connect, but then you happen to get cold feet and refuse to pay the $180+ they request via credit card, the next thing that happens isn’t pretty. This scammer proceeded to actually follow through on his promise of the PC “not working” if they don’t agree to have him fix it, and so in a few quick steps, behind the user’s back, he enacted what is known as SysKey encryption on the SAM registry hive.
SysKey encryption is a little-known feature of Windows which allows administrators to lock out access to the Security Accounts Manager (SAM) registry hive so that login specifics cannot be stolen and the PC cannot be accessed without knowing the proper credentials. The problem is, unlike other scams, there is no way around the problem; you can’t simply remove the password, as the actual SAM hive has been encrypted entirely by the process. If your Windows installation has had SysKey activated, you’ll see the following message:
This computer is configured to require a password in order to start up. Please enter the Startup Password below.
The window which appears looks like this:
The ONLY solution is to find a clean copy of the registry hives from before this occurred. This scammer knew this, however, and as such, he took an extra step to block any repair or recovery attempts: he deleted all System Restore points on the machine, which normally house backup copies of the registry hives.
Unfortunately for him, I’m a much better technician. When the customer suspected foul play and decided to call me instead of proceeding, I immediately instructed them to power off the PC. Here’s how I fixed the problem without having to reinstall Windows.
FIRST, ensure you don’t have any Restore Points to work with:
- Check to ensure that the folder %SYSTEMROOT%system32configRegBack exists. If so, continue. If not, stop and immediately contact a technician.
- Reboot the PC and repeatedly press F8 to reach the Advanced Startup Options menu.
- Choose Repair your Computer from the menu.
- Cancel the automatic repair attempt and instead instruct the system to perform a System Restore to a date prior to the incident occurring.
If no Restore Points exist, your scammer intentionally removed them to prevent this from occurring. If this happens to you, follow these additional steps to resolve the problem:
- POWER OFF your PC immediately.
- Boot to external media of some sort (NOT your Windows installation) and navigate to the %SYSTEMROOT%system32config folder.
- Backup the registry hives in this folder to a temporary location. The files are:
- Navigate to %SYSTEMROOT%system32configRegBack as mentioned earlier.
- Copy all registry hives from this folder (the same files as listed above) into the %SYSTEMROOT%system32config folder.
- Reboot the PC.
This solution only works if you have not already tried to reboot the PC subsequently. If you have, it may still work, but that is entirely dependent upon whether or not Windows created a new RegBack copy following a successful boot.
In the case of my customer, it worked, and they were back in Windows, just like it never happened. Nice try, scammer. You’ll have to try harder to beat me though.