CONFIG\SYSTEM missing turned into Lsass error

Discussion in 'Software' started by marcwtf, Nov 6, 2009.

  1. marcwtf

    marcwtf Private E-2

    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.
     
  2. dlb

    dlb MajorGeek

    No help here :( Sorry. Just wanted to say that I've used this exact same "fix" for corrupt hive problems on several occasions, and I have NEVER had the steps actually work to where I got to a desktop. I always ended up reinstalling. When I see these types of errors now, I usually perform an 'external' system restore by using Winternals ERD, and that works about 4 times out of every 5.

    GOOD LUCK!

    (I'm assuming you're using the steps outlined in this KB article)

    (signing out now to play some COD4 LOL )
     
  3. AustrAlien

    AustrAlien Specialist

    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&action=read&click=open&article=1150238652

    This "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.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds