Corrupt Registry
Corrupt Registry PDF Print E-mail
Written by Lazarus   
Tuesday, 26 January 2010 09:45
Article Index
Corrupt Registry
Part 1
Part 2
Part 3
Part 4
All Pages

When you try to start your computer, do you get one of the following error messages?

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE
Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate
System error: Lsass.exe
When trying to update a password the return status indicates that the value provided as the current password is not correct.

Corrupted registry files can cause a variety of different error messages, so it is possible to receive a message that is not shown here.

This article describes how to recover a Windows XP system that does not start because of corruption in the registry. This is not a guaranteed full recovery of the system to a previous state; however, you should be able to recover data when you use this procedure.

Warning: Microsoft recommends that you do not use the procedure that is described in this article if your computer has an OEM-installed operating system. The system hive on OEM installations creates passwords and user accounts that did not exist previously. If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives.

Microsoft also recommends that you use the ASR backup before you try the procedure described in this article. But how many of us have an Automatic System Recovery (ASR) backup?

With that warning in place, I just want to say that these steps have worked for me almost every time, even with OEM-installed Windows operating systems.

NOTE: Make sure to replace all five of the registry hives. If you only replace a single hive or two, this can cause potential issues because software and hardware may have settings in multiple locations in the registry.

If you have ever run NTBackup and completed a system state backup, you do not have to follow the procedures in parts two and three. You can go to Part Four.



Last Updated on Sunday, 07 February 2010 10:21