Get the fix to the NTLDR is missing boot error message affecting Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10.
About the “NTLDR is missing” error
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: NTLDR is missing error screen on older versions of Windows
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.
NTLDR is missing
Press Ctrl+Alt+Del to restart
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
and , please refer to the respective pages in our extensive wiki and knowledgebase.
Symptom 2: NTLDR is missing error screen on newer versions of Windows
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.
Causes of this Error
This error has been known to occur as a result of one of the following causes:
Cause 1: Computer is booting from a non-bootable source
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.
Cause 2: NTLDR-related files are corrupt or missing
On Windows XP, Windows 2000, and Windows 2003 Server this error may appear if any of boot-related files(NTLDR, NTDETECT.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.
Cause 3: The bootable volume has its active partition set incorrectly
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.
Cause 4: Wrong bootsector code is installed
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.
Cause 5: Too many files in the root folder
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.
Fixing “NTLDR is missing” on Windows
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
instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.
Fix #1: Rebuild NTLDR via Easy Recovery Essentials
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.
Easy Recovery Essentials is guaranteed to fix the “NTLDR is missing” error automatically using its built-in Automated Repair option. EasyRE is currently available for Windows XP, Vista, 7 and 8 and can be downloaded and created on any PC.
. Make sure to note your Windows version (XP, Vista, 7 or 8) before you download EasyRE. This guide can help you
you have installed.
Burn the image. Follow these instructions on
very carefully, as making a bootable CD can be tricky! Alternatively, these instructions explain .
Boot up your PC
or USB you created.
Once EasyRE is running, choose the “Automated Repair” option and click Continue.
Choose “Automated Repair” in Easy Recovery Essentials
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.
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.
Once the process is complete, EasyRE will report its findings. Click on the Restart button to reboot your PC and test the changes.
The “NTLDR is missing” error should now be fixed as your PC begins to load:
Windows, booting up successfully.
You can download Easy Recovery Essentials .
Fix #2: Unplug all removable media
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.
Fix #3: Change BIOS boot order
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:
Restart the PC
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: Esc, Del, F2, F8, F10 or F12.
If the screen shows multiple keys, find the key to open “BIOS”, “setup” or “BIOS menu”
Use the arrow keys to select the BOOT tab. Move the HDD drive to the top of priority list.
Here is an example of a BIOS loading screen with a key guide:
Notice the key guide in the top-right corner
And here is an example of a BIOS boot loader configuration screen:
BIOS boot loader configuration screen
Fix #4: Replace NTLDR and NTDETECT.COM files
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.COM.
Here are the steps to replace these files:
Insert the Windows XP install CD
Restart the computer and boot from the CD
Press any key to boot from the CD
Press R when the Windows Options menu is loaded to access Repair Console
After this step, log into Windows by pressing 1 using the Administrator password
Use the following commands to copy the NTLDR and NTDETECT.COM files from the Windows installation disk to the hard disk:
copy D:\i386\ntldr C:\
copy D:\i386\ntdetect.com C:\
Where D:\ is the install CD’s drive letter and C:\ is the Windows XP partition’s drive letter
Once these files are copied, remove the Windows installation disc from the disc drive
Restart the PC
Here is an example of what the PC’s console output should look like once NTLDR and NTDETECT files are restored correctly:
Replacing ntldr and ntdetect.com files
Fix #5: Rebuild boot.ini file
The next steps are to rebuild the boot.ini file:
Insert the Windows XP install CD
Restart the computer and boot from the CD
Press any key to boot from the CD
Press R when the Windows Options menu is loaded to access Repair Console
After this step, log into Windows by pressing 1 using the Administrator password
Use the following command when Command Prompt appears:
bootcfg /rebuild
When the systems prompts you about adding an identified Windows installation to the boot list, answer “Y”(Yes)
Enter “Windows XP” as Load Identifier and “/fastdetect” as OS Load Options.
Remove the install CD
Restart your computer
Here is an example of what the PC’s console output should look like once the boot.ini file is properly restored:
Fixing Boot.ini file
Fix #6: Change the bootsector code
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:
Insert the Windows Vista(or any newer version) install CD
Restart the computer and boot from the CD
Press any key to boot from the CD
Click on Repair your computer after selecting proper language, time and keyboard input.
Select the Windows installation drive, which is usually C:\, and click Next
Choose Command Prompt when the System Recovery Options box appears
Write the following command and press s Enter afterwards:
bootcfg /rebuild
If the program finds a Windows installation and asks whether it should add it to the boot list, press Y
Remove the install CD
Restart your computer
Here is an example of what the PC’s console output should look like once a boot sector is written correctly:
Writing a correct bootsect code
Fix #7: Delete excess files from root folder
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:
Insert the Windows XP install CD
Restart the computer and boot from the CD
Press any key to boot from the CD
Press R when the Windows Options menu is loaded to access Repair Console
After this step, log into Windows by pressing 1 using the Administrator password
Enter the following command when Command Prompt appears to move to the root folder from the default C:\Windows folder:
Enter the following command to display all files in the root folder
Then, enter the following command to delete the file:
del [filename]
Where [filename] is the name of the file to be deleted
Remove the install CD
Restart the PC
Here is an example of what the PC’s console output should look like after a single file is deleted from the root directory:
Deleting a file from command line
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
del *.* /A-S-H
command to delete all files in the current folder that are not hidden or system files:
Deleting multiple files
Linked Entries
Support Links
– our repair and recovery disk.
It’s an easy-to-use and automated diagnostics disk. It’s available for ,
and . It’s also available for Windows XP and Windows Server.
Read more at .
, member-to-member technical support and troubleshooting.
Get a discounted price on replacement setup and installation discs: , , , .
Applicable Systems
This Windows-related knowledgebase article applies to the following operating systems:
Windows XP (all editions)
Windows Vista (all editions)
Windows 7 (all editions)
Windows 8 (all editions)
Windows 8.1 (all editions)
Related Articles
Fix guides for common boot errors
Startup blue screens?
Disk corruption?
Registry failure?
Virus infections?
Bootloader issues?
And more!?Exact phrase
Available article translations:
ERROR: A disk read error occurred when starting Virtual Machine
APPLIES TO:
Parallels Desktop 9 for Mac
When you launching Virtual Machine on Parallels Desktop you receive A Disk Read Error message:
Windows installation on this Virtual Machine is corrupted. That could be caused by improper shutdown of virtual machine.
Resolution
Open Time Machine and restore the 'Windows_name.pvm' file (see location below). If you don't have a backup follow the steps below.
Check if the virtual machine is mounting with Parallels Mounter.
Locate the 'Windows_name.pvm' file, it is usually located in one of the following directories:
/username/Documents/Parallels/
/Users/Shared/Parallels/
Right click the .pvm file and choose 'Open With & Parallels Mounter'.
If virtual machine mounts fine then find the largest .hds file, copy it to .pvm folder and change extension to .hdd (you may rename file to make it easy to read) in order to restore the data which is not corrupted.
In case if virtual machine cannot be mounted, it means the whole virtual hard disk and its file system are corrupted and you can try to restore Windows by following the windows recovery guidance:
Recover using Windows CD/DVD:
For Windows XP:
For Windows Vista/7:
For Windows 8/8.1
Create new virtual machine from scratch and try to connect the virtual hard drive of corrupted VM to the fresh one:
Go to Configuration of the new virtual machine & Hardware & click '+' button in the left down corner of the window and add existing hdd file. Put the location path into the appeared dialog window.
In addition you may use one of the third party file recovery applications, for instance
(free trial).
Note: applications above are just examples of the possible recovery applications which can be used, in case if you have any difficulties using those applications, please contact the support team of each application separately.
If none of the above solutions help, the virtual machine cannot be restored and you need to create completely new virtual machine in order to continue running Windows on your Mac. We suggest that you make backups of the .pvm file regularly in order to prevent data loss.
Search words:
1e5db060acdf56d947b4 48e7cf384e3bcca8e050f19b889fb58f1
Was this article helpful?
Tell us how we may improve it.
Parallels International GmbH. All rights reserved.}