There are multiple potential causes for the "NTOSKRNL.EXE is missing or corrupt" error in the Windows operating system. Review each section below for troubleshooting and resolution options.

Keyboard issue

This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not causing your error by replacing the keyboard with a different keyboard, or disconnecting the keyboard from the computer.

Miscellaneous corruption

Before trying any of the below recommendations, it's recommend you load the last known good configuration.

• How to load the last known good configuration.

Corrupt boot.ini file

This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system or added or removed hard drives in the computer.

Make sure the line pointing to the operating system and its drive and partition is properly configured in the [boot loader] and [operating systems] section.

• Help and information with the file boot.ini.

Missing boot.ini file

Microsoft Windows XP users

If the boot.ini is severely corrupted or missing, a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue.

• How to rebuild the Windows boot.ini.

Microsoft Windows NT and Windows 2000 users

To restore the original boot.ini file in Microsoft Windows NT or Windows 2000, you need an ERD [Emergency Repair Disk], then follow the steps below. If you do not have an ERD, you cannot follow these steps.

1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
2. In the setup menu, type R to start the repair.
3. When prompted for the ERD diskette, insert the diskette and inspect the startup environment.

Missing or corrupt ntoskrnl.exe file

If the ntoskrnl.exe file is corrupt or missing, this can also generate the error. To restore this file, follow the steps below.

1. Insert the Microsoft Windows XP CD.

Note

If you have a restore CD and not a Microsoft Windows XP CD [compact disc], it's likely the steps below will not resolve your issue.

1. Reboot the computer, as the computer is starting a message to press any key to boot from the CD should be seen. When you see this message press any key.
2. In the Microsoft Windows XP setup menu press the R key to enter the Recovery Console.
3. Select the operating system you want to fix, and then enter the administrator password.
4. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
5. Once prompted if you want to overwrite the file, press Y then Enter to overwrite the file.
6. Type exit to reboot the computer.

Windows NT installed on a partition bigger than 7.8 GB

If you are running Microsoft Windows NT 4.0 on a partition larger than 7.8 GB, this issue can occur if the boot files are located outside this limitation. When this error occurs, your computer displays the error message shown below.

OS Loader v4.01 Disk I/O error status=00000001 Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe Please reinstall a copy of the above file.

If your system partition is larger than 7.8 GB, you need to delete the partition and recreate the partition to 7.8 GB or less.

Corrupted hard drive or severely corrupted Windows

Check the hard drive for any errors by running the chkdsk program. To do this, follow the steps below.

1. Insert the Microsoft Windows XP CD.

Note

If you have a restore CD and not a Microsoft Windows XP CD, it's likely the steps below will not resolve your issue.

1. Reboot the computer. As the computer is starting, a message to press any key to boot from the CD should be seen. When you see this message, press any key.
2. In the Microsoft Windows XP setup menu, press the R key to enter the Recovery Console.
3. Select the operating system you want to fix and then enter the administrator password.
4. Once at the Recovery Console, type chkdsk /r at the prompt.
5. Once completed type exit and see if the issue is resolved.

If, after trying all the above steps you're still encountering the same issue, it's likely that Windows is severely corrupted and we recommend you reinstall Windows.

The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.

Description and Symptoms

The error messages, alerts, warnings, and symptoms below are tied to this error.

Symptom 1: ntoskrnl.exe is missing or corrupt error screen on startup

The ntoskrnl.exe [short for Windows NT operating system kernel] is responsible for various system services such as hardware virtualization, process and memory management. Right after NTLDR and NTDETECT boot files are done with the basic loading subroutines and hardware detection, the control over the boot process is passed to ntoskrnl.exe so that the operating system could start loading. However, if ntoskrnl.exe is missing or corrupt, then the following error appears and the boot process is halted.

Windows could not start because the following file is missing or corrupt: \system32\ntoskrnl.exe. Please re-install a copy of the above file.

For more information on how computers start up and how the Windows XP boot process works, please refer to the respective pages in our extensive wiki and knowledgebase.

Causes of this Error

This error has been known to occur as a result of one or more of the following:

Cause 1: Invalid boot.ini configuration

An incorrectly configured boot.ini file may result in the Windows XP bootloader attempting to load Windows from the wrong drive or partition.

If NTLDR attempts to load Windows from the wrong partition, it will not find ntoskrnl.exe and this error may be occur.

Boot.ini may become misconfigured as a result of incorrectly installed software, a failed Windows update, virus infection, or an incomplete Windows upgrade.

Cause 2: Corrupt boot volume

Corruption of the boot partition on a Windows XP PC can cause this error to be present.

The boot drive can become corrupted as a result of an unsafe shutdown, sudden power loss, unsafe removal of a local or external disk, or physical disk damage and/or corruption.

A corrupted boot partition may occur on both NTFS and FAT32 filesystems and volumes.

Cause 3: Corrupted or deleted ntoskrnl.exe

As the error screen states, this error is sometimes caused by a lost or corrupted ntoskrnl.exe file on the Windows system partition. The system partition may or may not be the same as the boot partition [see above].

\Windows\system32\ntoskrnl.exe may be deleted or corrupted as a result of unsafe shutdown, NTFS or FAT32 volume corruption, failed Windows updates, or virus infection.

Cause 4: PS/2 keyboard incorrect behaviour

Keyboard-related software issues are largely no longer a concern with newer USB/internal keyboards. However, older PCs that use a keyboard attached to the PC via a serial interface, could misinterpret the device’s mapped memory as a storage volume, leading to boot problems like this one.

Cause 5: Missing drivers for hard disk controller

If Windows does not have the necessary drivers to access the Windows system files on the main partition, this error message can be seen. This can happen as a result of a failed driver update, changes to the hardware configuration, or changes to the hard disk configuration in the BIOS.

Fix NTOSKRNL.exe is missing or corrupt in Windows

Fix

1: Use Easy Recovery Essentials

Easy Recovery Essentials is guaranteed to fix the “NTOSKRNL.EXE is missing or corrupt” error automatically using its built-in Automated Repair option. EasyRE is currently available for Windows XP, Vista, 7, 8, Windows 10, and Windows 11 and can be downloaded and created on any PC.

1. Download Easy Recovery Essentials. Make sure to note your Windows version [XP, Vista, 7, 8, 10, or Windows 11] before you download EasyRE. This guide can help you identify what version of Windows you have installed.
2. Burn the image. Follow these instructions on how to burn the bootable ISO image very carefully, as making a bootable CD can be tricky! Alternatively, these instructions explain how to create a bootable EasyRE recovery USB stick/drive.
3. Boot up your PC from the Easy Recovery Essentials CD or USB you created.
4. Once EasyRE is running, choose the “Automated Repair” option and click Continue.
   Choose “Automated Repair” in Easy Recovery Essentials
5. After EasyRE scans your computer’s drives, identify and select the drive letter for your Windows installation from the list, and then click on the Automated Repair button to begin.
   Choose the drive associated with the Windows installation you’re trying to repair.
6. Easy Recovery Essentials will start analyzing the selected drive for problems. EasyRE will test for and attempt to automatically correct errors with the disk, partition, bootsector, filesystem, bootloader, and registry. No intervention is required, as EasyRE’s repair is fully automated:
   Easy Recovery Essentials searches for errors and makes corrections to the selected Windows installation.
7. Once the process is complete, EasyRE will report its findings. Click on the Restart button to reboot your PC and test the changes.
8. The “NTOSKRNL.EXE is missing or corrupt” error should now be fixed as your PC begins to load:

You can download Easy Recovery Essentials from here.

Fix

2: Replace or recreate a corrupted/incorrect boot.ini

A boot.ini file is used by Windows to configure and display its operating system options. Instructions on manually recreating the boot.ini file are also available, but require a moderate level of computer expertise. The instructions below will guide you on recreating boot.ini automatically from the Windows XP setup CD.

Unable to boot into the Windows setup CD? See our guide on setting up a PC to boot from the CD or DVD for troubleshooting and more detailed instructions.

1. Insert your Windows XP CD and restart your computer.
2. Press a key to boot into the CD when you see the “Press any key to boot from CD” message.
3. When you arrive at the “Welcome to Setup” message, press R to start the Recovery Console.
4. Type in your Administrator password; hit Enter
5. The next command you need to write is below; hit Enter afterwards: bootcfg /rebuild

The above command, bootcfg /rebuild, will scan your computer for installed Windows copies. If you have Windows XP, here are the next steps:

1. Press Y if the command prompt shows a message similar to the one below: Total Identified Windows Installs: 1 [1] C:\Windows Add installation to boot list? [Yes/No/All]
2. When you receive a message like this: Enter Load Identifier You are being asked to provide a name to be assigned and shown in the boot menu for the installation you picked in the previous step. Examples: Enter Load Identifier: Windows XP Professional [Recovered]
3. [Optional] When you receive a message like this: Enter OS Load options Type in bootcfg /rebuild 0 followed by Enter
4. Restart your computer.

Here is an example of what the PC’s console output should look like once the boot.ini file is restored:

Restoring Boot.ini file

Fix

3: Boot into Last Known Good Configuration

Windows Setup CD/DVD Required! Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use Easy Recovery Essentials for Windows instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.

Rebooting your PC into “Last Known Good Configuration” mode forces your computer to use a saved version of the Windows registry that was in place the last time your computer successfully booted. If this error is being caused as a result of incorrect, misconfigured, or uninstalled drivers, booting your PC in “last known good configuration” mode may resolve the problem. This option is available from the Advanced Boot Options menu at system start.

Here are the steps to start your PC up using the Last Known Good Configuration option. More detailed instructions on starting up your PC using the last known good configuration are also available.

1. Restart your computer
2. Wait for your BIOS to complete POST [the screen with your manufacturer logo and/or system information]
3. Quickly begin tapping F8 repeatedly, until you see the list of boot options
4. Choose “Last Known Good Configuration [Advanced]”
5. Press Enter and wait for your PC to boot.

Fix

4: Disconnect PS/2 or serial keyboard

If the fix above doesn’t work and the PC is using an old PS/2 keyboard, it’s recommended to attempt disconnecting it and then restarting the computer to see if anything changes. Here are the steps to do it:

1. Shutdown the computer
2. Disconnect the keyboard
3. Power up the computer

Some users have reported that that the NTOSKRNL.exe error disappears after disconnecting the keyboard and then reconnecting it after a restart.

Fix

5: Restore the ntoskrnl.exe file

If ntoskrnl.exe is in fact missing or corrupt, you can restore the original ntoskrnl.exe file back from your Windows XP installation disc.

Unable to boot into the Windows setup CD? See our guide on setting up a PC to boot from the CD or DVD for troubleshooting and more detailed instructions.

1. Insert your XP CD into the computer.
2. Restart your computer.
3. Press any key to boot into the CD when you see the “Press any key to boot from CD” message.
4. Press R to start Recovery Console when the Options screen appears.
5. Type in your Administrator password followed by the Enter key to submit it.
6. You’ll reach the Command Prompt now, type the following command, where bootcfg /rebuild 1 is your CD’s drive letter and bootcfg /rebuild 2 is the letter of the drive you installed Windows to: expand D:\i386\ntoskrnl.ex_ C:\Windows\system32\
7. Press Y when you are asked if you want to overwrite this file and then hit Enter to submit the command.
8. Restart your computer.

Here is an example of what the PC’s console output should look like once the ntoskrnl.exe file is restored:

Restoring the ntoskrnl.exe file

Fix

6: Run chkdsk

If this problem is being caused by a corrupt boot or system partition, it may be repaired by scanning the NTFS or FAT32 partition for errors or corruption.

bootcfg /rebuild

3 will verify files and data on the disk.

Here are the steps:

1. Insert your Windows CD; restart your computer.
2. Boot into the CD by pressing any key when the “Press any key to boot from CD” message appears on your computer.
3. Press bootcfg /rebuild 4 to open the Recovery Console once at the Options menu.
4. Type in your Administrator password; hit Enter
5. At the command prompt, type in the following command and press Enter chkdsk /r
6. After the bootcfg /rebuild 3 process is completed, restart your computer. Make note of any warnings or alerts that bootcfg /rebuild 3 prints.

Here is an example of what the PC’s console output should look like once the chkdsk.exe is complete:

Windows XP chkdsk result screen

More Information

Linked Entries

The errors below have been verified as being associated with or related to this problem:

• On Windows Vista, 7, and 8 this error appears as Windows\system32\winload.exe is missing or corrupt
• MBR boot process
• Windows XP boot process
• bootcfg
• chkdsk
• The Advanced Options menu

Support Links

Easy Recovery Essentials for Windows – our repair and recovery disk.

It’s an easy-to-use and automated diagnostics disk. It’s available for Windows 8, Windows 7 and Windows Vista. It’s also available for Windows XP and Windows Server.