Windows cannot boot because it cannot find hive. System root/System32/Config/Software is corrupt or missing
Posted on 2010-01-07
OK, experts, in 395 questions I have never put HELP! or URGENT! in a question title. I was tempted here, but I didn't.
All I did was remote into the server from my PC and uninstall the AV and hit restart when it said to. It would not and it just showed me the login screen, but I couldn't log in. I rebooted and got the above error message. I researched it via here and Google and found several articles, but I do not want to wing it when the best experts are out there. I did find one for XP that asked me to type a list of commands at the C: prompt in Recovery Console, but I chose not to.
I am running a Dell Server with SBS 2003 Standard Edition R2 with my system on the C: drive and data on my D: drive. the C: drive is a RAID1 and the data is on a RAID5. Two completely separate drives obviously.
Here is what I have at my disposal:
1. The server booted up from the install disk to the recovery console
2. A full backup from Acronis with system state (I believe)
3. A full backup from Backup Assist which uses the Windows Backup Program
I have another server with the exact same OS on a RAID5 just sitting here doing nothing and not connected to anything.
For reasons that I doubt I could ever explain, I do not think I backed up the system states on the NTBackups. I hope they are in the Acronis Backups.
I have two Buffalo II RAID5 NASs on my network, both of which are accessible from this machine. Each backup above is made in duplicate, one copy of each on each NAS.
I would appreciate any advice or input as to what would be the best way to go. Please tell me I can restore the registry.
I also have BartPE disks and the UBCD bootup disk. I also have complete Dell Support I could call, but I am not sure if they would be helpful with a software issue.
I should say I will answer from home. Right now it is midnight, and I am fried. I think if I try to do this now, I will get frustrated and do something stupid.
I guess if worse came to worst, I could fire up the HP with SBS 2003, attach it to the network, and restore some data for Friday.