Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a Dell system with windows 2000 that will not boot and continues to indicate that the ntoskrnl.exe file is missing or corrupt.
No ERDs have been created so I have to perform a repair by locating the windows partition. For some reason the repair is unable to detect a previous windows installation even though there is a \winnt directory present. So a repair using this method is not an option. If I want to reinstall windows into the same \winnt folder, I'm warned that all folder and subfolders will be replaced including the My Documants folder. This tells me that a complete reinstall will happen.
Using a Winternals ERD disk, I replaced the ntoskrnl.exe file, the boot.ini file, the ntdetect.com file and the ntldr file from the I386 folder. But I still get a message saying that the ntoskrnl.exe file is either mising or corrupt.
I have no clue at this point how to proceed short of pulling the drive, put it in another compute as a slave, back up files and then replace it back into the original computer and do a complete windows installation.

This error is typically attributed to either the file "is" damaged in some way (even missing...);, or the boot.ini info is incorrect - i.e. the ARC path is pointing to the wrong location for the file. A virus can produce this latter effect (according to some folks). Any evidence of virus infection in the immediate past?
Some folks will advocate the Fdisk /mbr routine as resolution to this problem. Not one I tend to favour as if there is a virus involved it may do more damage than good...
Overall I'm not sure what's happening here, but one way that may at least regain access to data (and then to back it up prior to going any further):
Install W2K again as a separate installation giving you a dual-boot (W2K/W2K).
Simply run W2K setup as per norm (CD or floppies + CD boot) and opt for a clean/fresh install to new folder. Do NOT install to current winnt folder; do NOT opt for a repair routine.
Providing it goes in OK you can then access data; you may also find you can again access original version (if all things are in your favour...).
The default for W2K is winnt; adding a second installation will often offer windows - which is fine. Or you can change it to winnt-2 (or similar)?
Critical item is to ensure you do NOT install to the same folder as original installation.
Attempting a parallel/second (new) installation will not make the situation any worse... so I can't any harm in trying it?
Incidentally presumably the drive is ntfs?

Hi,
In Windows2000 this error can also be generated if the 'hal.dll' file is corrupt or missing. You may want to check into this if the issue still persists.
Jrsy

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |