Windows 2000 Registry Error.

[trizzz]

This may be *REALLY* strange, or not really strange at all...but I'm
faced with a situation that I've never dealt with before.

Loading Windows 2000 (I'm the psuedo-IT guy at my office) and the
machine ALMOST fully loads, but then the blue screen comes up. I can't
read what it says, except that there's something wrong in the registry.
The computer reboots - and thus begins the cycle of almost loading
windows, blue screen (for a split second), and reboot.

Now, we just replaced the guy's HDD yesterday to get him back on his
feet - but the problem now is that he's archived his Outlook to his C
Drive, so it's become of upmost importantence to get his archive file
back.

I'm writing this from home. The last thing I tried was I used the
Windows 2000 install disk to get a recovery consol (it wouldn't even
boot in safe mode). I ran chkdsk /p and it came up with some
errors...when I left work yesterday, it was running the repair.

Perhaps this will work - maybe the errors were not allowing windows to
properly load the registry entry it needed?

If that doesn't work - perhaps others might have some other suggestions
on how to get this thing back working. It doesn't even necessarily
HAVE to work again - I just need access to that one file on there.

Thank you for your future suggestions,
TriZz

 

[Mark V]

This may be *REALLY* strange, or not really strange at all...but
I'm faced with a situation that I've never dealt with before.

Loading Windows 2000 (I'm the psuedo-IT guy at my office) and
the machine ALMOST fully loads, but then the blue screen comes
up. I can't read what it says, except that there's something
wrong in the registry.
The computer reboots - and thus begins the cycle of almost
loading
windows, blue screen (for a split second), and reboot.

Now, we just replaced the guy's HDD yesterday to get him back on
his feet - but the problem now is that he's archived his Outlook
to his C Drive, so it's become of upmost importantence to get
his archive file back.

I'm writing this from home. The last thing I tried was I used
the Windows 2000 install disk to get a recovery consol (it
wouldn't even boot in safe mode). I ran chkdsk /p and it came
up with some errors...when I left work yesterday, it was running
the repair.

Perhaps this will work - maybe the errors were not allowing
windows to properly load the registry entry it needed?

If that doesn't work - perhaps others might have some other
suggestions on how to get this thing back working. It doesn't
even necessarily HAVE to work again - I just need access to that
one file on there.

Skipping to file recovery...have you been successful booting the
system with a Linux or "PE" operating system and reading the disk?

 

[Guest]

Try http://support.microsoft.com/kb/830570/en-us

If the machine is not a laptop you could also try just slaving the hd
to th pc and booting up with the good hdd and reading the slave drive
that way....

HTH

This may be *REALLY* strange, or not really strange at all...but I'm
faced with a situation that I've never dealt with before.

Loading Windows 2000 (I'm the psuedo-IT guy at my office) and the
machine ALMOST fully loads, but then the blue screen comes up. I can't
read what it says, except that there's something wrong in the registry.
The computer reboots - and thus begins the cycle of almost loading
windows, blue screen (for a split second), and reboot.

Now, we just replaced the guy's HDD yesterday to get him back on his
feet - but the problem now is that he's archived his Outlook to his C
Drive, so it's become of upmost importantence to get his archive file
back.

I'm writing this from home. The last thing I tried was I used the
Windows 2000 install disk to get a recovery consol (it wouldn't even
boot in safe mode). I ran chkdsk /p and it came up with some
errors...when I left work yesterday, it was running the repair.

Perhaps this will work - maybe the errors were not allowing windows to
properly load the registry entry it needed?

If that doesn't work - perhaps others might have some other suggestions
on how to get this thing back working. It doesn't even necessarily
HAVE to work again - I just need access to that one file on there.

Thank you for your future suggestions,
TriZz

Ha®®y

(e-mail address removed)

 

[Dave Patrick]

If the system hive is corrupt, and assuming you already tried LKG (F8 and
choose Last Known Good), It may be possible to rename the system hive found
in
%systemroot%\system32\config\system
to system.old
then rename
%systemroot%\system32\config\system.alt
to
%systemroot%\system32\config\system

You can also try using the most recent backup found in
%systemroot%\repair\regback

If that fails you haven't much choice but to copy/ use the
original-as-installed system hive from
%systemroot%\repair\system
to
%systemroot%\system32\config\system
You'll need to reinstall the device drivers for any hardware added since the
original OS install.

If the software hive is corrupt, it may be possible to rename the software
hive found in;
%systemroot%\system32\config\software
to software.old
then copy the most recent backup found in
%systemroot%\repair\regback
as
%systemroot%\system32\config\software

If that fails you can copy/ use the file
%systemroot%\repair\software
This file is an image of the hive at the time the OS was installed, so you'd
have to reinstall all software. This being the case you might just as well
blow it away and start a new install. (note: this would at least allow you
to start the OS to make any necessary backups prior to wiping the drive.)


To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %windir% or %systemroot%



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

| This may be *REALLY* strange, or not really strange at all...but I'm
| faced with a situation that I've never dealt with before.
|
| Loading Windows 2000 (I'm the psuedo-IT guy at my office) and the
| machine ALMOST fully loads, but then the blue screen comes up. I can't
| read what it says, except that there's something wrong in the registry.
| The computer reboots - and thus begins the cycle of almost loading
| windows, blue screen (for a split second), and reboot.
|
| Now, we just replaced the guy's HDD yesterday to get him back on his
| feet - but the problem now is that he's archived his Outlook to his C
| Drive, so it's become of upmost importantence to get his archive file
| back.
|
| I'm writing this from home. The last thing I tried was I used the
| Windows 2000 install disk to get a recovery consol (it wouldn't even
| boot in safe mode). I ran chkdsk /p and it came up with some
| errors...when I left work yesterday, it was running the repair.
|
| Perhaps this will work - maybe the errors were not allowing windows to
| properly load the registry entry it needed?
|
| If that doesn't work - perhaps others might have some other suggestions
| on how to get this thing back working. It doesn't even necessarily
| HAVE to work again - I just need access to that one file on there.
|
| Thank you for your future suggestions,
| TriZz
|