Windows Forum

Ask something
Discussion Locked

Corrupt Registry File - Can't Boot

0 helpful
9 replies

by sblakeup

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We've been an NT shop and recently acquired a 2000 server.

I was stupid.

I downloaded printer drivers from the HP web site and installed them on the NT server (they are designated for Plug and Play-type systems, 98, Me, 2000, XP).

After theinstall routine completed, I gracefully restarted (Start Button/shutdown/restart). I now get the blue screen of death with a message saying the registry hive (or it's alternates or log files) can't be read (\system32\software). Obviously, I can't boot now.

All F8 related alternatives have the same result, including all Safe Mode boots, Last Known Good Config, VGA mode and Debugging.

We don't have the experience with 2000 yet to know squat about our options. Can anyone offer suggestionsthat may be helpful? I've got the 2000 Server CD handy...

Thanks in advance for your help. We're not afraid of doing a re-install, it's just that this was a separate domain with separate userid's, profiles, security settings and apps...more work than we want to recreate today if not necessary.

Scott

9 replies

by mbrunton

What you need to do is boot from the 2000 cd. Choose the repair option from the menu. Don't choose recovery console. Choose the other option, i think it is manual. Run the repair and it will reboot. This might fix it. If not just reinstall.

Mike

by timwalsh

If you have a CURRENT ERD, you can attempt a repair install from the NT setup routine.
You will need to boot from the NT4 boots disks. When it gets to the point where it is ready to start installing NT4, it will attempt to detect any previous installations.

Assuming your previous installation is detected, you will be given the option of repairing the previous installation or conducting a fresh installation. Choose the repair option and follow directions. Even if you don't have a CURRENT ERD, you might try an older one with the understanding that any configuration changes you have made since the ERD was created will be lost. If you don't have an ERD, you can still attempt a repair install, but in my experience , it usually doesn'twork without an ERD.

I'm assuming the server you are talking about is your PDC. Do you have any BDCs installed? If you can't get your PDC to boot (no matter what you try), you can promote a BDC to PDC.

I almost sound as if you want to attempt a migration from NT4 to WinK, but I'm not sure from your wording.
If the server you are having problems with IS your PDC, you can't get it to boot, and you don't have any BDCs, having Win2K available won't help you. You will need to recreate your domain from scratch either with NT4 or Win2K. Your only other salvation would be if you have a RECENT, GOOD, full backup of your server.

Hope this points you in the right direction.

by sblakeup

After following Chris's advice, I went through the Recovery Console process and was able to get to a c: prompt. The good news is, we can see what happened - the software file (the registry hive) is corrupt. I renamed it and can reboot from older versions of the file from the winnt\repair directory, but it's the 15MB corrupted file I obviously want. The autorepair feature when booting from CD didn't work (it either wants an emergency repair disk, which of course we don't have, or it can't find the Windows installation on it's own in the default directory).

Anyone know of any ways to try to recover this file? The OS won't read it to copy to alternate locations...don't know if utility programs would help at all or not.

Scott

by nitin

All ppl above are saying it right - but they are perfect scenarios(which work 50%). If nothing works, try loading the hive from a different computer(you will need a load of tools like winternals etc)

I have a number of errors like this (on Promise RAIDs) when ppl switch off computers by accident. But a number of times, I have recovered. Dont loose heart - this error what you are reporting is 99% recoverable

This discussion is closed to new replies.