Hello Wee,
This is most commonly caused by a corrupted system hive.
First thing to do is if you have another copy of this file with the same
service pack, use the recovery console to copy the file to the machine.
You can check to see if the registry is corrupted by trying to load the
corrupt registry with REGEDT32 in a parallel install of NT or Windows 2000.
If you cannot load up the hive you know it is corrupt. REGEDIT for .NET
server actually has the capability of automatically fixing corruption in the
registry by deleting the corrupt values or keys. So to fix this, load the
hive with REGEDIT on .NET server of even Windows XP, SP1 which also has the
updated REGEDIT that will fix the corruption. Another utility that can fix
this is listed below. With this utility you can also find out what the
corruption is versus .NET regedit which justs deletes the corrupted keys /
values. A utility called ChkReg.exe can be used to fix the corruption on the
registry hive. Please contact me if you need to get this utility and cannot
find it anywhere else.
830570 The Registry Repair Utility download for Windows 2000-based computers
http://support.microsoft.com/?id=830570
OR
You can try to run a full repair on the OS, to get the file back. You will
than have to re-apply all service packs and hotfixes.
268106 Repairing, Recovering, and Restoring an Installation of Windows 2000
http://support.microsoft.com/?id=268106
Thank You.
Diana.
This posting is provided "AS IS" with no warranties, and confers no rights.
