Monthly Archives: February 2013

Windows XP: Removing Syskey Startup Password

The issue:

Computer shows only a black screen with the following text: Windows XP Startup Password – This computer is configured to require a password in order to start up. Please enter the Startup Password Below. This occurred after a client got on a phone call with someone claiming to be from “Windows”. The phone call started going bad for the would-be-scammer and he decided incapacitate the computer.

Windows XP prompting the user to input a syskey password.

Windows XP prompting the user to input a syskey password.

The Troubleshooting:

After a quick search I realized the program is called “Syskey“.

The solution:

If you have a restore point from before this was set, copy the registry hives from the restore point into your active registry’s folder (Normally C:\Windows\System32\config\). If you don’t know how to do this from a non-booting copy of Windows XP just follow these directions to learn how to do just that with the use of a Knoppix live CD. Don’t forget to backup your old hives and to run a system restore after the process is complete.

How did this happen in the first place?

Here is the process to lock your computer using Syskey.

Process for setting up Syskey on Windows XP.

Process for setting up Syskey on Windows XP.

  1. First bring up the “Run” dialog box by clicking Start -> Run… or by pressing [Windows Key] + R
  2. Type syskey in the “Open:” field.
  3. Click OK
  4. On the new window: choose Update.
  5. On the Startup Key” window: choose the Password Startup radio button.
  6. Type in the Password you wish to set.
  7. Type in the password again to Confirm it.
  8. Click OK on the “Startup Key” window.
  9. Click OK on the Success window.

Windows XP: Repairing Registry Hives from a System Restore Point

This article is the first of what I hope will be many in a series I am calling “Base Level”. These articles will detail some of the base level skills you should already have if you work in a PC repair technician position. If you don’t know one of the items here don’t be embarrassed. I personally didn’t know any thing when I started and was hoping this would help someone in a similar position. If you aren’t familiar with these things learn to do them without having to refer to this site. The are things that you will do regularly.

Why would I need to know this?

This is a very easy way to fix your registry but you are pulling a registry from the past and pairing it with current files. This can be some what sorted out by doing a system restore immediately after but it still may cause issues. That said this is a very useful skill when it comes to something that is messed up in the registry that causes the computer to not respond. Here is one common example:

Windows XP displaying a boot error relating to a corrupt registry hive.

Windows XP displaying a boot error relating to a corrupt registry hive.

What am I going to need for this?

Head over to and get the latest version of the Knoppix and burn that to a CD. Make a nice CD case for it and keep it around. This is a useful tool in your arsenal.

Ok, I am ready. What do I need to do?

Place your Knoppix CD into the your optical drive. When the boot: prompt pops up type knoppix and press enter.

Knoppix ready to boot.

Knoppix ready to boot.

When Knoppix gets fully loaded click on the PCManFM icon in the bottom tool bar on the left.

Location of the file browser (PCManFM) in Knoppix.

Location of the file browser (PCManFM) in Knoppix.

Locate the partition where your windows install is and and click on it. Note: It probably will not be marked as “WINDOWS_XP”.


Click on the System Volume Information folder to open it.


Next, click on the directory marked _restore proceed by some random hex values and hyphens in brackets.


This next part may be easier if you put PCManFM into Detailed List View by clicking on View -> Detailed List View.


Now that it is set in Detailed List View you can clearly see when each restore point folder corresponds to what date. These dates are a good indicator of when each restore point was made. This should give you a good idea of which one you should pick. In the example below I opted to go back a couple of days. When you have chose the restore point that would like to use click on the folder associated with it. Then open the snapshot folder inside it.



Now you need to copy the following files to your clipboard:



Now click back on the partiton where your Windows install is and navigate to ./WINDOWS/System32/config and create a backup folder for the old registry hive files. Make sure to include today’s date in the folder name!


Now drag and drop the following files in the config directory into that newly created folder, like so:


Go ahead now and paste the files from the restore point directory into the config directory. And rename them to match the ones you backed up. Like this:



Okay, Nearly finished! Now just reboot the machine by clicking the start menu like item in the bottom left and choosing Logout then Reboot from the menu that pops up.


Last but not least you need to run a system restore now that you can get back into the system. This helps insure that your registry and Window’s system files are on the same page. Fire up system restore.


Now choose a date from system restore when the system was operating as you intended it to. It doesn’t have to be the same date as the day we picked earlier but it can be.


After the system restore completes you are done!

Wait, couldn’t I have used X and have gotten the same results?

As the first screencap in this article hinted at you can accomplish this same task with a Windows XP disk, but you can resolve this by booting into anything that will let you read and write to the files on the partition that the corrupted Windows install is located on. Examples of this are your Windows XP installation media, a installed recovery environment, or a Linux bootable live CD. We used a Knoppix live CD because it is very compatible and has a GUI so it wont alienate anyone starting out. If you are starting out I wouldn’t recommend using the windows installation media because you may end up needing to slipstream drivers and without tab completion some of the directories can be a pain to type up. In the event you are in the mood for it, the Microsoft Blessed™ way to accomplish this is laid out in Knowledge Base article 307545. They have you do some extra steps just to put you back into a GUI quickly and then you have to mess with file permissions (because you are back inside your Windows system) to get to the files you need.

Update Error: 0x80070426 on Windows Vista.

The Issue:

0x80070426 showed up when I tried to pull down Windows update KB928419. Later I noticed the CryptSvc service’s description was missing, but the service seemed to start and stop normally. The description I received instead of the normal one was:

<failed to Read Description. Error Code: 15100>

CryptSvc showing an error message instead of a proper description.

CryptSvc showing an error message instead of a proper description.

The Troubleshooting:

I ran the system file checker on the computer by opening up the command prompt and typing sfc /scannow. After that was fully completed it let me know it had failed to repair some items. So I opened up the log located at C:\Windows\Logs\CBS\CBS.log and did a search on the log for any line that said “Could not” (because those are particularly juicy). And this was the result:

2013-01-28 14:05:08, Info                  CSI    000000b5 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:32{16}]"cryptsvc.dll.mui"; source file in store is also corrupted

The solution:

I replaced the file named in the log (C:\Windows\System32\en-US\cryptsvc.dll.mui) with one from a working vista machine. The good file I replaced it with had an md5 hash of deebc869807089a9b0bfb8332278ce7b and a file size of 4.00KB. This ended up fixing my problem!

I hope this helps someone!