BleepingComputer.com: CONFIG\SYSTEM missing

After getting this error:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

I did this:

md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default

It all went fine till I got to the 3rd part, first line, copy the system file out of the repair folder. File doesn't exist. So I finished other 4. Now there was no system file so I copied the system.bak back into the system/32/config folder. No when I rebooted I get:

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.

This has happened to me before once or twice out of the hundred times I've had to do it. I usually just reinstall after getting aggravated. Just wondering if this a fix or work around for this.

marcwtf, on Nov 7 2009, 09:26 AM, said:

Oh yes, there is a very simple solution.

You said: "all went fine till I got to the 3rd part, first line, copy the system file out of the repair folder. File doesn't exist."
If you have a look inside the "repair" directory using the "dir" command, you will probably find system.bak and if that is the case simply use that file like so ...

copy c:\windows\repair\system.bak c:\windows\system32\config\system
----------------------------

There is an altogether "better" way of doing the job .... which avoids this problem as well as others ....
System Restore from Recovery Console
http://2pure.net/index.php?session=0&a...icle=1150238652

The "off-line System Restore" can also be done using the same steps with a LIVE CD (a Linux version or BartPE version), or another Windows operating system/another computer. It is a very simple and familiar rename and copy/paste exercise.

Did you have a power failure/interruption (unplug or power switch), aborted restart or ungraceful shutdown prior to this message:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

What method are you using to boot to do this copying - a bootable XP installation CD, Recovery Console CD, etc.?

Whatever method you are using, please run a chkdsk /r before trying any file manipulation.

I've made a note of these solutions for future use,
but have to say that on the 2 occasions when I got
that message, (Oct 2007 and earlier this year)
I was up and running with chkdsk /r from the Recovery Console.

It is not a serious error. I also sometimes get this 1st message, but without doing a repair installation, I just omit the message and then my machine again works fine by itself.

Well, JS, it's pretty serious for those who cannot start their computers.

Do share your solution - just how do you 'just omit the message' ?

I'm curious.

Instead of doing this manually, use System Restore for backup your registry. You can also use http://www.larshederer.homepage.t-online.de/erunt

AustrAlien was correct about the file being called system.bak. Couldn't log into the windows Recovery off the XP Home disk, cause now asked for a password to log into the Admin account. So I used Active password Recovery, which is pretty much a windows live with a few tools. Used the explore my computer in Active Password, went to the windows/repair folder, and all the files were there, and for some reason the system file was system.bak, just as AustrAlien said it would be. I have no idea why a .bak extension was put on it. But I moved the file to the system32/config folder, deleted the system that was there, renamed the system.bak I just placed there to system (took off the .bak). Rebooted. No more errors, just freezes right before loading the desktop... Next step I'm trying is a repair install.