Windows registry error on boot

Ok, so yes an atypical windows registry issue.
I goto the recovery console and start doing the

copy c:\windows\system32\config system c:\windows\tmp\system.bak and I get a file could not be copied, this works for sam, software, default, and security however doesn't work for system. Anyone out there able to help on this, I need this machine up and running again ASAP please help.

 

Hello matty,

Can you access System Restore in safe mode?

Or http://support.microsoft.com/default.aspx?scid=kb;en-us;304449&sd=tech how to access from a command prompt.

Regards - Charles

 

When trying the safemode + command prompt i get to
multi(0)disk(0)rdisk(0)partion(2)\Windows\System32\Config\System.alt

Windows coult not start because the following file is missing or corrupt
\Windows\System32\Config\System

Since I can't copy it when I tried doing the Recovery Console I'm guessing the file is slammed? Now by not copying that file over and going the regular way of doing the recovery console with the copy and delete and then using the repair directory would this horribly destroy the system?

If not I guess I can just use ERD Commander 2005 when I get home, I forgot to bring it to work with me today.

 

Hi matty,

How did you make out?

Have you tried fixing the boot record which looks botched up right now:

Bootcfg: Automatically scans all local disks for Windows installations and configures and repairs entries in the operating system menu (Boot.ini)

Regards - Charles

 

I used ERD Commander and did the registry repair option, kind of worked, the machine boots however now im faced with the diliema of putting files back in thier right place, and for some reason Outlook won't read a PST file.

Back to the drawing board.

One thing I did learn, is DO NOT do a recovery console registry repair if you are missing any of the files IE: Software, System, Default, Security, or Sam.

My System was the one that was screwy so I tried doing the recovery console repair, it apparently did something to Sam to make a Lsass error on boot of the machine.

I finally said im done and went with ERD and backed up to a restore point prior too and then took off from there.

Lessons Learned:
1: Last Known Good doesnt do anything at all apparently
2: Safe mode boot will not automatically repair a registry
3: Do not do a half assed recovery console
4: Do not repair files unless they need repairing (If system is messed up you dont need to recover sam)
5: Take your time and don't skip steps (Again, I learned the hard way on this)
6: ERD Commander is probably one of the best software and recovery tools out there, if you work in an IT field I highly highly highly recommend purchasing a license. It has now saved my *** countless hours at 4 times to date.

 

Hi Matty,

6: ERD Commander is probably one of the best software and recovery tools out there, if you work in an IT field I highly highly highly recommend purchasing a license. It has now saved my ass countless hours at 4 times to date.

Thanks, have never run into ERD Commander, will look into it.

Regards - Charles

 

ERD Commander - www.wininternals.com and if you can't afford their Admin Pack (or just don't need all the features), it is an outstanding utility to have.

Both the ERD Commander and the Admin Pack (which includes the ERD commander) are excellent value for the money.

 

Hi Newt,

Thanks, I can see how this utility is usefull for pros - a little too "rich" for the home user though.

For the home user the "ultimate weapon" is a restored drive image or a re-install.

Regards - Charles

 

Agreed Charles. As mattymatt79 noted, ERD Commander is a great tool if you do this stuff for a living. Otherwise, it certainly is not the least expensive option available.

 

This is how I pay the bills, for me its worth it especially when I need to recover dead drives.

also a new tool ive been playing with lately is recover my files, and ontrack data recovery.

this recover my files tool completly resurected a dead drive that wouldnt even register that it was connected.