Where is the ntldr file for windows xp. NTLDR is missing, what should I do? NTLDR recovery is missing
While loading the Windows operating system, the user may encounter an unpleasant message on the monitor screen:
NTLDR is missing
Press CTRL+ALT+DEL to restart.
There may be several reasons for this malfunction:
The system uses several hard drives, booting from the wrong drive;
- CD, flash drive, floppy disk inserted;
- severe fragmentation of the MFT table of the root folder. If the root folder's MFT contains a large number of files, it may become so fragmented that an additional allocation index must be created. Because allocation indexes list files in alphabetical order, an NTLDR file may end up in a second allocation index;
- NTLDR and/or NTDETECT.COM files were deleted by the user;
- files were damaged due to a power failure or hard drive error.
To solve this problem, we extract all possible storage media and, if this does not help, choose one of the following methods:
1. The easiest way is copy data files from a working machine and replace.
Connect the hard drive to another computer;
Boot from LiveCD
2. Boot from the original Windows XP disk in "Recovery Console" mode. After the command line appears:
Use command fixboot.
Copy files from the disk "copy D:\i386\ntldr c:\", "copy D:\i386\ntdetect.com c:\" and change the attributes for the copied file
attrib ntdetect.com -r -s –h
attrib ntldr -r -s –h
Use a utility from Microsoft Bcupdate2.exe (DOS program).
Bcupdate2.exe C:/F
/q - quiet mode (the /y parameter must also be used)
/y - do not require confirmation
/f - update the used volume
/t - check only for old boot code
If the computer does not boot, the screen is black and displays the error NTLDR is missing, this means that it is impossible to read the boot record from the Ntldr and NTDETECT files. Let me make a reservation right away: there is no need to reinstall Windows. These files could have been damaged by a virus, a hardware failure, or for me they simply disappeared without a trace.
How to restore Windows with this error:
1. Disassemble the system unit, check the cable to the hard drive, you can change the cables (if there are 2) between the drive and the screw. Reboot and try.
2. Insert the Windows XP disc into the drive , At the same time, do not forget to set the BIOS to boot from CD-ROM. After booting, press the R key to open the recovery console. If one OS is installed on the computer, the following information will appear:
Which copy of Windows should I sign in to?
Type 1, press Enter.
A message will appear:
Enter the administrator password:
If the administrator does not have a password, then simply press Enter.
The following message appears:
**WARNING**
This computer has a non-standard or invalid Master Boot Record. Using FIXMBR may damage your existing partition table. This will result in loss of access to all partitions of the current hard drive.
If there are no disk access problems, it is recommended that you abort the FIXMBR command.
Are you confirming the new MBR entry?
Enter the letter Y (yes, yes) and press Enter.
A message will appear:
A new master boot record is created on the physical disk \Device\Harddisk0\Partition0.
The new master boot record has been successfully created.
The system prompt will then appear: C:\WINDOWS>
Enter fixboot and press Enter.
After this the message will appear:
End section: C:.
Do you want to write a new boot sector to the C: partition?
Enter the letter Y (yes, yes) and press Enter.
A message will appear:
File system on boot partition: NTFS (or FAT32).
The FIXBOOT command writes a new boot sector.
The new boot sector was successfully written.
The system prompt C:\WINDOWS> appears
All operations have been completed, now we exit the recovery console. Now exit the recovery console, enter the exit command and press Enter. After this, the computer will restart. If the error continues to appear, then go to step 3.
3. You need to write the Ntldr and NTDETECT files to the root of drive C. You can download them, unzip them and write them to a flash drive. Next, you will need a boot disk such as Windows LiveCD, LiveCD, Hirens boot, Reanimator xP or others that allow you to boot without Windows and access the file system. You can download Linux LiveCD from the Dr. Web website (there is also a built-in antivirus there) - a very necessary thing, and then using the built-in file manager Midnight Commander, move the specified files to the root of drive C. The only peculiarity of Midnight Commander is that it is on the Windows file system shows in the "win" directory. Download LiveCD. We used the same disk for .
Sometimes the computer starts to start, the NTLDR is missing error is no longer there, but it starts swearing at the file
boot.ini, located in the same root of drive C, then the archive you downloaded also contains this file and it must also be replaced.
Quite often in my practice, I came across the message NTLDR is missing when booting the computer. Perhaps often enough to write a separate article on this subject :)
This is what a similar situation looks like on the monitor screen:
After the message NTLDR is missing (NTLDR does not work, “missing” is damaged), we are asked to reboot, and then the situation repeats itself cyclically. Overloaded - the same picture. In general, the operating system does not boot.
I propose, as always, to analyze the situation in detail. What is NTLDR? This is the boot loader for Windows XP and Windows 2000. The abbreviation NTLDR means “ nt load r" (load - loading, and completely - a bootloader for systems based on NT technology).
Note: "NT" from English. New Technology - new technology. I don’t know why exactly this is so? Although, compared to Windows 98, it is certainly new and even revolutionary! :)
Now we know that our operating system boot loader is damaged. It sounds unpleasant. But there is good news: this is completely fixable and there is no need to reinstall Windows!
But before we start fixing the problem, let’s take a basic look at the process of starting Windows XP. How does it happen? We need to understand what we are dealing with, right? Let’s skip everything related to the “hardware” part of the system startup process (we discussed these points in previous articles on the site), and let’s touch specifically on the software component.
At the initial stage, the computer reads the so-called “ Master Boot Record" or - MBR (Master Boot Record). MBR data occupies one (first) sector of hard disk space (512 bytes). An insignificant volume, in fact, but it contains code that is copied into RAM and prepares the computer for startup.
Without going into details (so as not to complicate the description), the master boot record scans all physical and logical drives and finds a partition marked as “ active"(the OS starts from just such a partition) and transfers further control to the boot sector located on it.
This sector of the active partition (it is called the boot sector - Boot sector) is located in the first sector of the logical disk from which the operating system (OS) will be launched. The boot sector contains all the necessary information about the file system type and size and logical parameters.
In turn, the Boot Sector finds the bootloader of the operating system itself (in this case, NTLDR) and transfers control to it.
Note: Windows Vista and Windows 7 use file instead of "NTLDR" Winload.exe. This is the file located at C:\Windows\System32\winload.exe.
Once in control, NTLDR does the following:
- switches to 32-bit operating mode
- organizes access to the file system
- reads the file " boot.ini"and in the case of several installed systems - displays a menu for selecting them
- launches the program " ntdetect.com", which collects data about the composition of the computer's hardware (ntdetect.com builds a list, which is then used in the system registry key: HARDWARE of the HKEY_LOCAL_MACHINE branch)
- initializes the file " ntoskrnl.exe"(kernel of the operating system. "Kernel" - kernel) and transmits to it the collected information about the found equipment. In addition to the kernel, another very important file is loaded - “ hal.dll"(Hardware Abstraction Layer - level of hardware abstractions). It separates (abstracts) the system kernel from the hardware (this mechanism allows the OS to function on various hardware platforms).
Note: The files “ntoskrnl.exe” and “hal.dll” are located in the System32 directory.
After this, the operating system itself starts. This is in short :) There is still a lot of “interesting” happening there, but we are not interested in this now, but in the inscription NTLDR is missing and how to fix it?
NTLDR is missing how to fix it and what to do?
Now, understanding what role and at what stage of system startup the operating system loader performs, we can begin to solve problems associated with it.
Let us remember the following: for the successful start of the Windows 2000/XP/2003 operating systems, the following files are required:
- Ntldr
- Ntdetect.com
- Boot.ini
They are located at the root of the disk " C:" Yes, the bootloader is a file on our hard drive, as well as the accompanying modules involved in loading. Let's take a closer look at it.
To do this, we will need to display system files and folders that are hidden by default in Windows Explorer. To do this, click on the “Tools” menu and from the drop-down menu - “Folder Options”.
Go to the “View” tab and uncheck (as shown below) the “Hide protected system files” checkbox and set the switch to “Show hidden files and folders”. I also recommend removing the “bird” from the item: “Hide extensions for registered file types.”
Click “Apply” and go to our “C” drive. This is what we see there:
All three of our files responsible for loading the system are present. Great!
I suggest simulating an accident and removing them all! :) This is the easiest way to visualize what will happen if any of these files are damaged (or missing).
We delete them all and reboot. After the reboot we see the message NTLDR is missing Press Ctrl+Alt+Del to restart. Exactly what we need! :) Let's start restoration.
First, here is our action plan: since the files are missing (damaged), it would be very logical to assume that we will need to take exactly the same files somewhere and substitute them instead of the missing (damaged) ones. Iron logic! :) Where can I get them? Here are several options:
- download from the Internet
- rewrite from a friend
- use the Windows installation disk (copy them from there)
Since we are our own admins and are accustomed to solving issues without outside help, we will choose the third option! :)
To do this, we will need a disk with the original Windows XP (in the case of Windows 2000, the process looks almost the same), preferably with the one that we installed on the computer. We load it into, set the BIOS to boot from CD and wait for the window we need to appear.
At first, it's similar to the process of installing Windows from scratch, with one (very important) exception. At some stage we should have a window that looks something like this:
Pay attention to the line: “To restore Windows XP using the recovery console, click “ R" Let's take advantage of this opportunity: click the " R" on keyboard.
Note: What does the Recovery Console do? It allows you to gain limited access to the system (in text mode) if it does not boot. In “text” it means that we will not be able to use the mouse (since there will be no graphical shell) and we will have to enter all commands from the keyboard.
Already scared? When I saw it for the first time, I was scared, but then it went away :) In general, anyone who is familiar with DOS will feel absolutely comfortable.
So, after launching, the program will scan the disks for the presence of Microsoft operating systems on them and display the result in a column under numbers, starting from the first.
Since we have one system, then (in the photo below) we see that there is one OS under the number “ 1 " in the folder "C:\WINDOWS".
Next we are asked, “Which copy of Windows should I sign in to?” Naturally - the first (and, in our case, the only one). Press the number on the keyboard " 1 ", then - the key " Enter" We are then asked to enter the administrator password. If you have it, enter it; if not, just press “Enter” again.
Here we are, logged in! This is evidenced by the inscription at the very bottom “C:\WINDOWS” and the blinking cursor for entering text commands.
What commands do we need to know? First of all, those that respond to our navigation (movement) around the disk. We will need to go into folders.
The task is to go to drive “C” and view its contents! Simply, having a mouse at hand :)
Take a close look at the screenshot below:
Let’s wrinkle our brains and figure it out! First of all, what does the entry "C:\WINDOWS>" mean? This is the identifier of our current position. We are located on the “C:” drive in the “WINDOWS” directory. Icon " > " is a separator that simply visually separates the result of previous commands (to the left of it) from the ones we enter (to the right of it).
Since we need to display the contents of the system disk, first we need to “select” from the “WINDOWS” directory. To do this, enter as shown in the photo above: “ cd.." The abbreviation "CD" stands for " Change Directory"(change directory, folder, directory), then - a space and two dots in a row. This command is analogous to the back arrow in Windows Explorer.
Just remember that things like space, indentation, left or right slash are very important here. There is only one correct spelling and that is the one that must be given!
I dwell on this in such detail due to the fact that this is the basis (roots and origins), which, unfortunately, not everyone knows and remembers. And then the message appears on the monitor NTLDR is missing, but how to fix it, what to do and immediately - go to the specialist! :) And the master goes to the “sources”, loads into the recovery console, enters simple commands from the keyboard and gets a positive result :)
Let's move on. After that, press “Enter” (this ends the entry of any command) and see the symbol “C:”. We left the “WINDOWS” directory one level up and got to the root of the C drive. And in it we enter the following abbreviation: “ dir"(directory), which will display the contents of the current directory.
We see all our files and directories that are located on it.
Now let's go to our CD or DVD drive. We have a Windows installation disk in it, remember? To do this, enter the command “ D:"(without quotes). The main thing here is to “guess” under which letter of the alphabet it is located. I have one logical partition (aka system partition), so the letter “D” is an optical drive. If you have several partitions (or hard drives), then the letter may be completely different. Let's say - “F”, “G” or - even further down the alphabet. Well, I think you will choose by brute force :)
In the folder with our installation disk, we give the command “dir” (browse the contents) that is already familiar to us. We get this result:
Here we will be interested in the folder “ I386" It contains the bootloader files we need. NTLDR And Ntdetect.com, which we are going to copy instead of the damaged ones (deleted by us on purpose).
To do this, we need to go to this folder and make sure that this is true? Enter the command “cd” (change directory) and the exact name of the target directory is “i386”. Press enter. We see the result: D:\i386> We have moved to the directory we need. In it we will execute the content review command - “dir”.
Among the large number of files it contains, we can see the one we need!
Now we write a copy command, indicate which file we are copying and where: “ copy ntldr c:“You need to write exactly like this, observing all spaces, colons and putting a slash at the end.
The system tells us that one file was successfully copied to the root of drive C. Let's check this circumstance. Let’s go to the system drive (you should already know how to do this), enter “dir” and see this picture:
There appeared a Windows bootloader file - ntldr.
Super! We just solved the problem with the message NTLDR is missing from the command line when booting the computer! Let's reboot and taste the fruits of our labors :)
To do this, we just need to type the command “ exit» (exit) and press enter. The computer will begin to restart. But... for now we won’t see anything happy, except that the NTLDR is missing message will no longer appear, and the system will reboot cyclically without giving any more messages. Remember, in a fit of experimentation, we deleted two more files “Ntdetect.com” and “boot.ini”?
The first file can be copied from the same “i386” folder on the installation disk. Let's do this. Let's enter the recovery console, then go to the directory with this file and execute the copy command.
Please note that the file “Ntdetect.com” has an extension (everything after the dot in the name), so the extension must also be specified in the command itself. We see confirmation of successful copying.
Let's make sure of this. Go to drive C and look around there:
We see that both files we copied are in place. We try to reboot - “exit”. When loading, we, again, do not see NTLDR is missing, but we see this picture:
The “boot.ini” file is not only incorrect, we don’t have it at all! But the Windows system is smart and “tells” us that it is ready to start loading without it. And indeed, after a few seconds we can observe the successful start of our OS.
The problem is that such an entry will not go away and will appear every time you turn on the computer (and if the configuration file is truly incorrect, the system will not boot at all).
Therefore, let's learn how to fix this problem too! First of all, what is this file and what function does it perform? This is a small text configuration file that can be opened using Notepad. Let's do it. Here's what's inside:
Let's quickly look at its contents.
- boot loader - boot section (just a designation)
- timeout=30 - countdown timer until the OS starts loading (in seconds)
- default - operating system that will boot by default (relevant for systems with several operating systems installed at the same time)
- operating system - boot parameters of the system(s). Each subsequent one adds a new line here.
Now let's look at the parameter values themselves. The “multi” and “disk” parameters will almost always be set to “0” and we do not touch them. We will be interested in " rdisk" - the serial number of the disk (starting from zero) from which the operating system is loaded. For example: if we physically (at the hardware level) have one hard drive, then there should be “0”, but if we have two hard drives and the OS is installed on the second one, then in this case the “rdisk” value will be “1”.
Parameter " partition"means almost the same thing, but for logical disks into which our hard drive is divided. Here the numbering starts from one. For example: if I load Windows from drive “C”, then “partition” will be equal to “1”, if from drive “D”, then - “2”, “E” - “3”, etc.
It remains to parse what comes after the slash: Windows="Microsoft Windows XP Professional RU". Instead of what is indicated in quotation marks, you can write anything. This is text information (download ID) and does not affect anything. Parameter " /fastdetect"instructs the bootloader that (if there is only one system installed) it should ignore the value of the timeout timer and immediately load the operating system without displaying the boot option selection window.
Knowing these simple things, you can set the required values directly in a text editor (notepad) and save the file. When you reboot, the new values we entered will be read from it. But I want to show you another method, specially designed for such cases by developers from Redmond.
We boot into our (hopefully already familiar console) and enter the command there “ bootcfg", from English. "boot config" (boot management). Since we entered the command without parameters (we did not indicate what it should do), the system will show us all possible options for its use:
Marked in red are the “keys” (additional options) of this command, which we can type immediately after it. Look, read, everything is in Russian.
Let's first use the "key" list" to display a list of systems already in the boot list. Before the “key” we put a space and a slash.
We are "told" that there are no items available for display in the download list. It’s no wonder, we don’t have the boot list itself (boot.ini), we successfully deleted it.
We use another “key” of this command - “ add"(add), you can also - " rebuild"(rebuild). The result will be the same.
We "forced" the program to scan all disks for the presence of Windows family systems installed on them. The result is one OS on the “C” drive in the “Windows” folder. Next we are asked to select the system to be added. Where to add it? Namely, in the “boot.ini” file, which was created at the same point in time :) We put the number “1” - the serial number of the found OS. Next is a prompt to enter the download ID. You can write whatever you want. For example - "My Windows XP". In the “Enter boot parameters” line, I advise you to enter “/fastdetect” (so as not to waste the timer).
Let's make sure that the "boot.ini" file is actually created in the root of the disk. Let's go to it and execute the "dir" command.
This is true! We reboot and make sure that the loading goes smoothly, the NTLDR is missing message does not appear, and no other windows either. Q.E.D!
Let's go to the loaded system (using the mouse) into the bootloader configuration file and see what it contains?
Notice what's highlighted in red. This is exactly the data that we entered from the console, and it was written at that moment to this file.
In conclusion, I would like to note the following, if you see the message when loading NTLDR is missing, then you can solve the problem in another way. Remove the hard drive, connect it to another computer with the same system and copy the necessary files from there. It’s up to you to decide, but I think your console skills will definitely come in handy in the future!
NTLDR is missing when booting Windows XP or bootmgr is missing when booting Windows 7
You turned on the computer, but when loading Windows XP it says NTLDR is missing and Windows 7 does not load or does not load with an error bootmgr is missing. Don't panic. Usually the problem is quite easy to solve.
Let's figure out what the inscription means ntldr is missing(in Windows 7 error bootmgr is missing). The message indicates that the Windows bootloader (ntldr or bootmgr file) was not found. The bootloader is the program that is first loaded into RAM and controls the subsequent loading of the operating system. Naturally, if the bootloader is not found, then there is no question of any further loading of the OS and the computer prompts you to simply reboot by pressing the Ctrl+Alt+Del keys.
Files ntldr And ntdetect.com must be located in the root folder of the drive from which Windows XP is loaded (drive C:). If it is not there, then this error appears.
In Windows 7 boot loader bootmgr can be located either on the partition with the operating system (drive C) or on a special hidden partition that is created during installation and NTLDR is missing - causes of the error
1) The reason that the Windows bootloader is missing from the disk may primarily be logical errors in the file system. These errors can appear, for example, after an incorrect shutdown of the computer or after it freezes, or as a result of damage to the hard drive itself.
2) Also, the cause of this error may be the banal deletion of a file by the user himself or by a virus.
3) Another reason is changing the active disk partition. Files ntldr And ntdetect.com(Windows XP) or bootmgr(Windows 7) must be on the active disk partition, otherwise they will not be found.
4) Also, this error often occurs after the boot disk, that is, drive C, has been compressed.
5) The cause of damage to the ntldr and bootmgr files can be physical damage to the hard drive (bad sectors or bad block).
NTLDR is missing - how to fix it
To resolve the error, you will need an ERD Commander boot disk (the disk image can be downloaded, and in this article read: how to burn an image to a CD) and an archive containing the files ntldr and ntdetect.com: .
If you don't have a disk drive, you can make a bootable USB flash drive ERD Commander. The archive with the files must be unpacked onto a flash drive so that it can later be copied to the system hard drive.
Now I will tell you what to do if you receive the message NTLDR is missing
1) First of all, you need to check the disk for logical errors in the file system.
We boot the computer from the ERD Commander boot disk or flash drive. Select the version of ERD Commander for your version of Windows. The screen will be black for some time after loading starts - don’t be alarmed, this is how it should be. You can judge that loading is in progress by the activity of the drive or flash drive. A dialog box will then appear asking you to connect to the network in the background. Click the button Skip Network Connection (in ERD 6.5 you need to click No) to skip this step. If you are prompted to redistribute drive letters as in the OS, agree by clicking Yes.
In the next window, select your operating system and click OK.
Now you need to open a command prompt window. To do this, go to the menu Start - Command Prompt(in ERD Commander for Windows 7, select Command line)
At the command prompt, enter the command chkdsk c: /f to check the C: drive and press Enter. If a message appears as in the figure below, press y(yes), then Enter
The verification process will begin, after which a report will be displayed.
Please note the point in bad sectors, showing the number of unreadable sectors on the hard drive. If this parameter is different from 0, I recommend trying to recover unreadable sectors using specialized programs or replacing the hard drive. After the disk errors are corrected, try booting Windows normally. In many cases, the operations performed are sufficient to restore the boot of Windows XP.
If, after doing this, the error NTLDR is missing or BOTMGR is missing still appears, proceed to the next step.
2) Check for the presence of NTLDR and NTDETECT.COM files on the system disk
For Windows 7, this step is not always relevant, as the bootloader is often located on a special hidden partition and it is not possible to remove it. Therefore, for Windows 7 you can skip this step.
Check if there are files ntldr and ntdetect.com in the root folder of the C: drive. To do this, download ERD Commander and launch Explorer ( Start - Explorer) and check for the presence of these files.
Even if the ntldr and ntdetect.com files are present on the C: drive, it is better to replace them with files from the Ntldr_ntdetect.zip archive
Select the files that need to be copied and right-click. From the context menu, select Copy to .
In the window that appears, you must specify the destination path for the copied files. Select drive C and click OK.
If the files already existed, a window will appear asking you whether to replace the file. Click Yes to replace the existing file with the one you are copying.
Now try restarting your computer. If this does not help, go to the third point.
3) Make sure that the disk partition on which Windows XP is installed is active
Windows can only boot if the ntldr or bootmgr boot loader is located on the active partition. You should check to see if the partition has accidentally become inactive.
Acronis Disk Director will help with this. The boot disk image can be downloaded. Burn the image to disk and boot from it.
From the disc menu that appears, select Acronis Disk Director 11 Advanced.
Now launch the management console (Work with the current machine)
Drive (C:) (or the one on which Windows is installed, if it is not on drive C) must be active. The section status should contain the inscription Active(underlined in the figure below), and there should be a red flag on the graphical image of the section. For Windows 7, the hidden 100 MB partition at the beginning of the disk must be active, if it exists.
If the disk with the bootloader is inactive, then the reason for the error is NTLDR is missing in Windows XP and BOOTMGR is missing in Windows 7 this is exactly the case. It is necessary to make the drive (C:) or the hidden system partition (if it exists) active. To do this, right-click on local volume (C:) and in the context menu that appears, select Mark as active.
A warning window will appear warning you that this may affect booting of the operating system. Click OK.
Now you need the program to carry out the planned operations and make the drive (C:) active. To do this, click on the button Apply scheduled operations.
A window will appear where the operations that will be performed will be written. Click Continue.
After completing all operations, click the button Close.
Then close the main window Disk management and press the button Reboot.
Try booting your computer in normal mode. Windows should boot normally.
This article is about a small bug NTLDR is missing Windows operating system, which some users may encounter while working.
I must say that the error is quite annoying and not everyone knows how to fix it, as a result of which they reinstall the system. This is not very convenient and not entirely correct, because there are more humane and, in part, simple methods, which will be discussed in this article.
NTLDR is missing in Windows XP
And this error pops up instead of loading the OS (operating system) of the Windows family in the form of the inscription: NTLDR is missing. It is impossible to get into Windows after this. What does it mean? Most likely, the boot files on the system partition are erased or damaged and the OS cannot boot, because. doesn't know what, where or why.
When you see something like this, don’t panic, but calmly insert the disk with (You have it, right? :)), set to boot from CD-ROM and after booting from this disk, instead press the R button to open the recovery console. In this very console you will be asked to select the OS you want to restore (to do this you need to click, for example, 1 and Enter, as well as when answering the console question, you may need to press y and Enter) and type the commands FIXBOOT and FIXMBR (see pictures below).
All. Reboot, wait... it should work :)
If it doesn't work.
If the above commands did not help, then the same recovery console and the copy command, i.e. the command for copying files, will save us. Using this command, you need to transfer 2 files from your disk - “NTLDR”, and “NTDETECT.COM”.
To do this, we will use the copy command. It works like this: “copy
copy e:\i386\ntldr c:\
copy e:\i386\ntdetect.com c:\
Where e:\ is the letter of your CD\DVD drive, and c:\ is the letter where the operating system is located where you, in fact, want to copy these files.
NTLDR is missing in Windows 7/8/10 (and bootloader recovery)
The solution is generally similar. You will need to get into recovery mode, for which, for example, you need to boot (also using booting from external media, as in the method above) from the installation disk or flash drive and at the first stage of installation, click on " System Restore":
In the command line that appears, we will need to enter two commands:
bootrec/fixmbr
bootrec/fixboot
Well, that’s all, actually.
Don’t forget to press Enter at the end of all this, restart the computer and, in fact, it will boot again from the disk, and not from external media.
It should help.
Afterword
Also, if you have any problems or don’t understand something, feel free to write in the comments, I’ll try to help, although NTLDR is missing is not such a terrible problem, unless, of course, the hard drive has failed.
