Aug
30
Windows could not start because the following file is missing or corrupt: WINDOWS\SYSTEM32\CONFIG\*
Filed Under Data recovery, Microsoft, Technical, Windows 2000, XP
Perform a registry hive recovery using the information in my System Volume Information article for the hive mentioned after CONFIG\ (typically SYSTEM).
Sorry, Windows 2000 users, Microsoft hath cursed thee without an enabled-by-default automatic registry hive backup facility. Try ERUNT, though, and perform similar steps to roll back your failed SYSTEM hive when it inevitably fails.
Tags: Operating systems, Refresher tip, System RestoreComments
2 Responses to “Windows could not start because the following file is missing or corrupt: WINDOWS\SYSTEM32\CONFIG\*”
Leave a Reply

My system crashed with this error message a few weeks ago. I was able to boot the recovery console and run chkdsk which ended up fixing the problems without going through the steps you list. You might want to recommend running 'chkdsk.exe /r' as a possible first step.
I don't recommend chkdsk /R as a first step until I've tested the hard drive for bad sectors.
If it has bad sectors, chkdsk /R is the last thing you'd want to do:
http://wiki.DjLizard.net/Data_recovery