Submit an edit

Get the fix to the <strong>NTLDR is missing</strong> boot error message affecting <strong>Windows XP, Windows Vista, Windows 7, Windows 8</strong>, <strong>Windows 8.1</strong> and <strong>Windows 10.</strong>
<h2>About the "<strong>NTLDR is missing</strong>" error</h2>
[kbintro]
<h3>Description and Symptoms</h3>
The error messages, alerts, warnings, and symptoms below are tied to this error.
<h4>Symptom 1: NTLDR is missing error screen on older versions of Windows</h4>
When a computer is turned on, the BIOS picks an eligible, bootable hard drive and then calls code stored in the MBR at the start of that hard drive. That MBR code in turn loads the bootsector from the active partition. On Windows XP, this bootsector code is tasked with loading NTLDR (the Windows XP bootloader) and its dependencies, which are used to load the operating system kernel and start up Windows. The NTLDR file is normally located in the root directory of the active partition on the first boot drive. However, if the NTLDR file is not found or is corrupt, then the loading process halts and the "NTLDR is missing" error screen appears.

<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/NTLDR-is-missing1.png"><img class="alignnone wp-image-3888 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/NTLDR-is-missing1.png" alt="NTLDR is missing error screen" width="720" height="400" /></a>
<pre>NTLDR is missing
Press Ctrl+Alt+Del to restart</pre>
The exact error message may vary: while “NTLDR is missing” is the most common one, the computer may also show “Boot: Couldn’t find NTLDR” or “NTLDR is Missing Press any key to restart”. For more information on <a href="http://neosmart.net/wiki/mbr-boot-process/">how computers start up</a> and <a href="http://neosmart.net/wiki/windows-xp-boot-process/">how the Windows XP boot process works</a>, please refer to the respective pages in our extensive wiki and knowledgebase.
<h4>Symptom 2: NTLDR is missing error screen on newer versions of Windows</h4>
Note that the NTLDR loader used in Windows XP, Windows 2000, and Windows 2003 Server was supplanted by a newer BOOTMGR loader since Windows Vista, so this error should not normally appear on newer systems. It can, however, still be encountered if the older NTLDR bootsector code is written to the partition with a newer version of Windows.  This is usually caused by errors made while configuring the boot loader manually.
<h3>Causes of this Error</h3>
This error has been known to occur as a result of one of the following causes:
<h4>Cause 1: Computer is booting from a non-bootable source</h4>
Sometimes this error can be caused if a computer tries to boot from a non-bootable source, such as a floppy disk or a flash drive. This usually happens if that computer's BIOS boot sequence is configured incorrectly.
<h4>Cause 2: NTLDR-related files are corrupt or missing</h4>
On Windows XP, Windows 2000, and Windows 2003 Server this error may appear if any of boot-related files(NTLDR, NTDETECT&#46;COM and Boot.ini) are missing or corrupt. These files are normally hidden and system protected, but they can still go bad because of user errors, power outages, or virus attacks.
<h4>Cause 3: The bootable volume has its active partition set incorrectly</h4>
Similar to the previous cause, this error may occur if a bootable disk's active partition is set incorrectly. For example, let's assume that the user's PC has a bootable volume with two primary partitions. The first partition is active, and has the operating system files, NTLDR + the NTLDR bootloader code set. The second partition is inactive, and has only the NTLDR bootloader code set without the NTLDR itself, probably as a leftover from a previous Windows installation. If the user sets the second partition as active instead of the first one, then the system tries to load from a second partition, looks for the NTLDR file, is unable to find it on this volume, and then halts the loading process, displaying an error screen.
<h4>Cause 4: Wrong bootsector code is installed</h4>
Windows Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10 use a newer version of loader called BOOTMGR, but this error can still appear if the older NTLDR-compatible master boot code is applied to the bootable partition. That is usually caused by errors made while configuring the boot loader manually.
<h4>Cause 5: Too many files in the root folder</h4>
On Windows XP Service Pack 1 and older versions of Windows 2000, if the root folder contains too many files, the MFT(Master File Table) may become so fragmented that an additional allocation index is created. Because files are mapped alphabetically in the allocation indexes, the NTLDR file may be pushed to the second allocation index. When this occurs, the bootsector will not be able to load NTLDR since it doesn't read any allocation indexes after the first one. Note that this error is properly fixed in Windows XP Service Pack 2 and the newer versions of Windows 2000.
<h2>Fixing "NTLDR is missing" on Windows</h2>
[setupcd]
<h3>Fix #1: Rebuild NTLDR via Easy Recovery Essentials</h3>
<div class="content dynamic_content_max_width"><span class="message_body">Easy Recovery Essentials’ one-click automated system repair corrects issues caused by missing or misconfigured NTLDR bootloader files by recreating them from scratch on the active bootable partition for Windows XP, 2000 and 2003 Server. Alternatively, on newer versions of Windows, EasyRE writes the correct bootsector code to the partition to make sure that the system loads properly. This is done automatically as part of the automated repair process, and requires no manual action or user intervention.
</span></div>
[easyre error="NTLDR is missing" bootscreen="xp-vista-7-8" guaranteed="true"]
<h3>Fix #2: Unplug all removable media</h3>
Since this error is often caused by BIOS trying to load from an external non-bootable drive, the user may try to unplug all external drives, and remove all removable media, such as CD/floppy disks, memory cards, and USB devices to make sure the BIOS doesn't try to load from any of them.
<h3>Fix #3: Change BIOS boot order</h3>
Alternatively, it is possible to check the BIOS boot order to ensure that the PC tries to load from an internal drive first.

To check the boot order, follow these steps:
<ol>
 	<li>Restart the PC</li>
 	<li>Press the necessary key to open BIOS menu. This key depends on the computer manufacturer and computer model.This is usually listed on the first screen that appears on your monitor. It can be any of the following: <kbd>Esc</kbd>, <kbd>Del</kbd>, <kbd>F2</kbd>, <kbd>F8</kbd>, <kbd>F10</kbd> or <kbd>F12</kbd>.</li>
 	<li>If the screen shows multiple keys, find the key to open “BIOS”, “setup” or “BIOS menu”
Use the arrow keys to select the <strong>BOOT</strong> tab. Move the HDD drive to the top of priority list.</li>
</ol>
Here is an example of a BIOS loading screen with a key guide:

[caption id="attachment_3711" align="alignnone" width="450"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2016/04/Dell-POST.jpg"><img class="wp-image-3711 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2016/04/Dell-POST.jpg" alt="Dell-POST screen" width="450" height="337" /></a> Notice the key guide in the top-right corner[/caption]

And here is an example of a BIOS boot loader configuration screen:

[caption id="attachment_3902" align="alignnone" width="500"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/boot_priority.gif"><img class="wp-image-3902 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/boot_priority.gif" alt="BIOS boot configuration" width="500" height="377" /></a> BIOS boot loader configuration screen[/caption]
<h3>Fix #4: <span id="Fix_1_Replace_NTLDR_and_NTDETECT046COM_files">Replace NTLDR and NTDETECT&#46;COM files</span></h3>
Windows XP users can replace the required files for NTLDR to load correctly by using your Windows Installation Disc. The files are named NTLDR and NTDETECT&#46;COM.

Here are the steps to replace these files:
<ol>
 	<li>Insert the Windows XP install CD</li>
 	<li>Restart the computer and boot from the CD</li>
 	<li>Press any key to boot from the CD</li>
 	<li>Press <kbd>R</kbd> when the Windows Options menu is loaded to access <strong>Repair Console</strong></li>
 	<li>After this step, log into Windows by pressing <kbd>1</kbd> using the Administrator password</li>
 	<li>Use the following commands to copy the NTLDR and NTDETECT&#46;COM files from the Windows installation disk to the hard disk:
<pre>copy D:\i386\ntldr C:\
copy D:\i386\ntdetect&#46;com C:\</pre>
Where <code>D:\</code> is the install CD’s drive letter and <code>C:\</code> is the Windows XP partition’s drive letter</li>
 	<li>Once these files are copied, remove the Windows installation disc from the disc drive</li>
 	<li>Restart the PC</li>
</ol>
Here is an example of what the PC's console output should look like once NTLDR and NTDETECT files are restored correctly:

[caption id="attachment_3906" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/NTLDR-NTDETECT-copy.png"><img class="wp-image-3906 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/NTLDR-NTDETECT-copy.png" alt="Replacing ntldr and ntdetect&#46;com files" width="720" height="396" /></a> Replacing ntldr and ntdetect&#46;com files[/caption]
<h3><span id="Fix_2_Rebuild_bootini_file">Fix #5: Rebuild boot.ini file</span></h3>
The next steps are to rebuild the <code>boot.ini</code> file:
<ol>
 	<li>Insert the Windows XP install CD</li>
 	<li>Restart the computer and boot from the CD</li>
 	<li>Press any key to boot from the CD</li>
 	<li>Press <kbd>R</kbd> when the Windows Options menu is loaded to access <strong>Repair Console</strong></li>
 	<li>After this step, log into Windows by pressing <kbd>1</kbd> using the Administrator password</li>
 	<li>Use the following command when Command Prompt appears:
<pre>bootcfg /rebuild</pre>
</li>
 	<li>When the systems prompts you about adding an identified Windows installation to the boot list, answer "Y"(Yes)</li>
 	<li>Enter "Windows XP" as Load Identifier and "/fastdetect" as OS Load Options.</li>
 	<li>Remove the install CD</li>
 	<li>Restart your computer</li>
</ol>
Here is an example of what the PC's console output should look like once the boot.ini file is properly restored:

[caption id="attachment_3905" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Bootcfg_rebuild.png"><img class="wp-image-3905 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Bootcfg_rebuild.png" alt="Fixing Boot.ini file" width="720" height="396" /></a> Fixing Boot.ini file[/caption]
<h3>Fix #6: Change the bootsector code</h3>
On Windows Vista, Windows 7, Windows 8, Windows 8.1, or Windows 10 this error can be fixed by writing a correct BOOTMGR-related boot sector code to the bootable partition.

Here are the steps to write a correct boot sector:
<ol>
 	<li>Insert the Windows Vista(or any newer version) install CD</li>
 	<li>Restart the computer and boot from the CD</li>
 	<li>Press any key to boot from the CD</li>
 	<li>Click on Repair your computer after selecting proper language, time and keyboard input.</li>
 	<li>Select the Windows installation drive, which is usually C:\, and click Next</li>
 	<li>Choose Command Prompt when the System Recovery Options box appears</li>
 	<li>Write the following command and press s <kbd>Enter</kbd> afterwards:
<pre>bootcfg /rebuild</pre>
</li>
 	<li>If the program finds a Windows installation and asks whether it should add it to the boot list, press <kbd>Y</kbd></li>
 	<li>Remove the install CD</li>
 	<li>Restart your computer</li>
</ol>
Here is an example of what the PC's console output should look like once a boot sector is written correctly:

[caption id="attachment_3912" align="alignnone" width="800"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Bootsect-nt60.png"><img class="size-full wp-image-3912" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Bootsect-nt60.png" alt="Writing a correct bootsect code" width="800" height="600" /></a> Writing a correct bootsect code[/caption]
<h3>Fix #7: Delete excess files from root folder</h3>
If the PC's operating system is an old version of Windows XP or Windows 2000 and it has too many files stored in the root folder, booting into the Repair Console from a Windows Installation disk and deleting the files from there is a possible solution.

Here are the steps to delete files from repair console:
<ol>
 	<li>Insert the Windows XP install CD</li>
 	<li>Restart the computer and boot from the CD</li>
 	<li>Press any key to boot from the CD</li>
 	<li>Press R when the Windows Options menu is loaded to access <strong>Repair Console</strong></li>
 	<li>After this step, log into Windows by pressing 1 using the Administrator password</li>
 	<li>Enter the following command when Command Prompt appears to move to the root folder from the default C:\Windows folder:
<pre>cd ..</pre>
</li>
 	<li>Enter the following command to display all files in the root folder
<pre>dir</pre>
</li>
 	<li>Then, enter the following command to delete the file:
<pre>del [filename]</pre>
Where [filename] is the name of the file to be deleted</li>
 	<li>Remove the install CD</li>
 	<li>Restart the PC</li>
</ol>
Here is an example of what the PC's console output should look like after a single file is deleted from the root directory:

[caption id="attachment_3903" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Delete-files.png"><img class="wp-image-3903 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Delete-files.png" alt="Deleting a file from command line" width="720" height="396" /></a> Deleting a file from command line[/caption]

Note that the Windows XP recovery console does not support mass file deletion in the recovery console, so manual file deletion may be a very long and tedious process if there is a lot of them. If that's the case, it is possible to load from a more modern Windows CD, and use the
<pre>del *.* /A-S-H</pre>
command to delete all files in the current folder that are not hidden or system files:

[caption id="attachment_3910" align="alignnone" width="800"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Deleting-multiple-files.png"><img class="wp-image-3910 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Deleting-multiple-files.png" alt="Deleting multiple files" width="800" height="600" /></a> Deleting multiple files[/caption]
<h2>More Information</h2>
<h3>Linked Entries</h3>
<ul>
 	<li><a href="https://neosmart.net/wiki/mbr-boot-process/">MBR boot process</a></li>
 	<li><a href="https://neosmart.net/wiki/windows-xp-boot-process/">Windows XP boot process</a></li>
 	<li><a href="https://neosmart.net/wiki/bootsect/">Bootsect</a></li>
 	<li><a href="https://neosmart.net/wiki/bootcfg/">Bootcfg</a></li>
</ul>
[partial name="partial_moreinfo" versions="xp,vista,7,8,8.1"]