Replacing Corrupted System Files in Windows NT (102359)
The information in this article applies to:
- Microsoft Windows NT Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
This article was previously published under Q102359
WARNING: Using Registry Editor incorrectly can cause
serious, system-wide problems that may require you to
reinstall Windows NT to correct them. Microsoft cannot
guarantee that any problems resulting from the use of
Registry Editor can be solved. Use this tool at your own
risk.
To enable a Windows NT machine with a corrupt .DLL file to complete the
logon process successfully, you must replace the .DLL with a new,
renamed version of the file:
- From a Windows NT machine that has an uncorrupted version of the
.DLL file you want to replace, connect to the machine with the
corrupt .DLL file as Administrator.
- From the remote machine, place a new, uncorrupted copy the of the
file in the SYSTEM32 directory on the machine with the damaged
file (use a different filename for the copy of the file).
- From the remote machine, run REGEDT32.EXE, to edit the registry on
the affected machine.
- Locate the following section:
HKEY_LOCAL_MACHINE on (Remote Machine Name)
SYSTEM\CurrentControlSet\Control\SessionManager\KnownDLLS. - In this section, change the name of the file pointed to by the key
to the new, renamed version of the file that was copied to the
SYSTEM32 directory. Close REGEDT32 and restart the machine with the
previously corrupted file.
The machine should start up and complete the logon process.
Modification Type: | Major | Last Reviewed: | 11/20/2003 |
---|
Keywords: | kbusage KB102359 |
---|
|