Hello, I'm getting an error when booting into Windows 7 NTLDR is missing Press ctrl+alt+del to restart! I know this error indicates that the NTLDR bootloader file is missing from my system or is corrupted, but let me, because there is no NTLDR file and the function of the operating system bootloader is performed by a completely different file, namely the system boot manager (bootmgr file), but what is strange , this file is in place - in hidden section without a letter (100 MB) "Reserved by the system, also in this section is the Boot folder, and in it the boot storage configuration file (BCD).
In short, it turns out that I have everything right! The BIOS is set to boot from the hard drive first, the boot files of the operating system are all in place, so what is this error NTLDR is missing in Windows 7 and how to get rid of it?
NTLDR is missing in Windows 7
NTLDR (NT Loader) - operating system loader Windows systems NT, 2000, XP, Server 2003
Hello friends! Yes, in Windows 7 this error should not be, but at times I have to deal with it. Let me tell you the very first case that happened to me a few years ago.
They brought me to work system unit with complaints that Windows 7 does not load and, in fact, when the computer was turned on, a error NTLDR is missing Press ctrl+alt+del. I was a little surprised if boot files are corrupted on Windows 7, then a " " error usually occurs and I even have an article on the site on how to deal with it. But here there was an error more inherent in the Windows XP operating system.
How to defeat this error in Windows XP there is also an article "", the whole point of the article is to copy the ntldr file from the installation Windows disk XP to the root of our system disk With operating system using the copy ntldr C:\ command, you need to do this all in the recovery console. But what about Windows 7?
I reasoned in this way, if in previous operating systems an error NTLDR is missing was associated with the boot files of a non-bootable operating system, then in my case the meaning is the same - the boot files are faulty Windows 7 or they don't exist at all.
Note: Windows 7 has a hidden System Reserved partition that is 100MB in size. The main purpose of this partition is to store files Windows boot 7. This small partition is always "Primary" and has an "Active" attribute, which tells the BIOS that this partition contains operating system boot files. You can only see it in Disk Management. If you assign a letter to it, you can go inside and see the system boot manager file bootmgr, you can still see daddy Boot, if we enter it, we will see the configuration files of the boot storage ( BCD).
File bootmgr and boot storage configuration files ( BCD) are directly responsible for loading the operating system, and if they are damaged, Windows 7 will not boot, issuing various errors, for example "BOOTMGR is missing.Press ctrl+alt+del" or "NTLDR is missing Press ctrl+alt+del"
If you assign a letter to the hidden partition, you can go inside and see the system boot manager file bootmgr, you can still see the Boot daddy if you enter it,
we will see the boot storage configuration files ( BCD).
Since all these files have the "Hidden" attribute, you first need to go to Folder Options and uncheck the Hide protected operating system files checkbox and check the Show hidden files, folders and drives then Apply and OK.
So friends, I decided to boot from the Windows 7 installation disk and restore everything in one fell swoop, namely:
#1 Restore the bootmgr file and restore the boot storage (BCD) configuration files with a single command bcdboot.exe D:\Windows (in your case, the command may be different, read the article to the end)
No. 2 Make active the hidden partition System Reserved (Reserved by the system), the volume is 100 MB.
Something to help, I thought. Looking ahead, I’ll say that you just had to make the hidden System Reserved partition active, that is, limit yourself to point number 2.
Note: Friends, now we will work with the command line of the recovery environment. I will give you the necessary commands, but if it is difficult for you to remember them, you can. This will greatly facilitate your work.
So, in the environment Windows recovery 7 I first decided on the drive letters.
We enter the command:
diskpart
list volume
You can see that the drive letter is assigned F:, and the hidden partition is System Reserved, 100 MB, Windows 7 Recovery Environment assigned a letter C:. So the operating system files with the Windows and Program Files folders are on the disk D:.
exit
and exit diskpart. AT command line we drive
bcdboot.exe D:\Windows
Attention: This command will restore the Windows 7 bootloader bootmgr file, as well as restore the Boot Storage Configuration (BCD) files, the contents of the Boot folder in the hidden System Reserved partition, 100 MB, specifically for the operating system located on the D:\Windows drive.
Success. The download files have been successfully created.
Let's look at a fairly common problem with booting a computer today, when the bootloader crashes and the system issues white on black: NTLDR is missing. Inexperienced users in most of these cases panic - still, the system offers a reboot by Ctrl - Alt - Delete, but then the same thing happens, the PC does not boot. The thing is that the system cannot detect the NTLDR file (NT Loader - OS loader Windows families NT), which is located in the root directory of the main partition from which the operating system is loaded. The causes of this problem may be different. The solution to this issue by reinstalling the operating system, which many people resort to due to their ignorance, is not optimal, it takes a lot of time. We will figure out why this happened and how to effectively fix the problem.
NTLDR is missing error. The file is physically missing
The first reason why the system does not find the bootloader file can be commonplace - the file was simply deleted. How and why - there are a lot of options, from the consequences of a virus attack to “too thorough” cleaning of the C: drive (you should not delete files in the root of the system drive if you don’t know exactly what they are responsible for). The solution is just as simple - you need to restore the bootloader file, usually along with the NTDETECT.COM file. If you have a computer with the same operating system at your disposal, write the ntldr and NTDETECT.COM files to any external media. Keep in mind that the boot.ini file on computers with different configurations may be different, this archive contains the most common version. There are two ways to return required files:
- Produce for Windows installations, by pressing the R key, enter the Recovery Console and copy the ntldr file to the boot partition using the command:
copy Z:\ntldr C:\ (where Z is the letter of the drive you are copying from)
- Boot the operating system from any available "live CD" (for example, ALKID LiveCD, Bart PE, portable Linux versions etc.) and with the help of any file manager(FAR manager, Total Commander) copy the files. In order for the NTLDR file to be visible in the file manager window, you must enable the option to show hidden and system files.
After the files are copied, we reboot the computer. If the problem NTLDR is missing did not disappear - let's understand further.
Incorrect boot due to clogged boot partition
Another reason for the appearance of the above may be the "contamination" of the root directory boot disk. In fact, the bootloader file is present in the right place, but for some reason the OS cannot detect it at this stage. Do not copy files or install various applications to the root of the system drive. Analyze your activity on the computer in the time before the problem with the download. You can delete unnecessary files using a method similar to copying system files by booting from a "live CD".
damaged boot record
There are cases when, for various reasons, the master boot record (master boot record) is damaged. To restore it, you can use the utility from the developers of Windows OS, Microsoft– BCUpdate2. The utility should be written to the disk from which you will boot. Boot from it and enter the command in the following format: Bcupdate2.exe C: /f /y Upon completion of the program, you should see the following message: The boot code was updated successfully successfully.
You can also use the Recovery Console tool by booting from the installation disk, executing the fixboot c:\ boot recovery command. But this is not always enough, you can also run the fixmbr command, although before that it is highly desirable to check the system antivirus program. Many antivirus developers offer absolutely free solutions in the form of regularly updated images of boot disks with a scanner - antivirus. There is still the possibility of losing information about partitions. In this case, they will have to.
Boot partition "is no active"
The partition from which the operating system is loaded must be in the state active otherwise it will not be possible to download from it. To correct the situation, you will have to boot from a disk that has a manager program. partitions of the hard disk (from Acronis or Paragon, for example...), select the partition you are interested in and set its attribute as active, which in turn should eliminate the problem with NTLDR is missing in the future.
Problems with hardware
Due to hardware problems, data may simply not be read from hard drive and this may be due to:
- Bad contact in the cable connecting the hard drive to motherboard. If the problem either occurs or disappears, replace the cable.
- Problems with myself hard drive in the form of the presence of poorly readable sectors, the so-called. bedov. There are tests and "treatments" hard drives, which scan the hard drive for bad sectors and, if any, will be required hard repair disk. In a special way, they mark such poorly readable sectors so that in the future, during operation, the operating system does not make calls to them. But this is usually the beginning of the end of the hard drive and you need to be prepared to fork out for a new one - otherwise there will be no problems with losing important information can't be avoided.
- Also, the possibility of problems with the motherboard cannot be completely ruled out. Microcracks, dried or swollen capacitors and other troubles - all this is quite likely. Alternatively, you can try to "throw" your hard drive on another motherboard that is known to be working. If the boot process started and went on (yet on a PC with other hardware, a full boot is unlikely), this will definitely indicate problems with your motherboard. You will have to take it in for repair or replace it.
Today we looked at the possible causes of NTLDR is missing errors and methods for its elimination. It will also not be superfluous for you to study a similar one (BOOTMGR is missing), which is found in Windows 7.
Quite often in my practice, I met the inscription NTLDR is missing when the computer boots. Perhaps enough often to write a separate article about this :)
Here is what this situation looks like on the monitor screen:
After the inscription NTLDR is missing (NTLDR does not work, “missing” is damaged), we are offered 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 bootloader for Windows XP and Windows 2000. The abbreviation NTLDR means - " nt load r" (load - loading, and in full - the loader of systems based on NT technology).
Note: "NT" from English. new technology- new technology. I don't know why exactly? Although, in comparison with Windows 98, it is certainly new and even revolutionary! :)
Now we know that our operating system bootloader is damaged. Sounds unpleasant. But there is good news: it is quite fixable and you don't need to reinstall Windows at all!
But before we start fixing the problem, let's take a look at the process itself in basic terms. Windows startup xp. How does it happen? Do we need to understand what we are dealing with? Let's skip everything related to the "iron" part of the system start process (we analyzed these points in previous articles of the site), and let's touch on the software component.
At the initial stage, the computer reads from the first sector of the zero cylinder of the hard disk the so-called " master boot record" or - MBR (Master Boot Record). MBR data occupies one (first) sector of hard disk space (512 bytes). A negligible volume, in fact, but it contains code that is copied to RAM and prepares the computer to start.
Without going into details (in order 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 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 logical drive, from which the operating system (OS) will be launched. The boot sector contains all necessary information about the type and size of the file system and logical parameters.
In turn, the Boot Sector already finds the bootloader of the operating system itself (in this case- NTLDR) and transfers control to it.
Note: in Windows Vista and Windows 7 uses file instead of "NTLDR" winload.exe. This is the file located at C:\Windows\System32\winload.exe.
Once in control, NTLDR does the following things:
- switches to 32-bit mode
- organizes access to file system
- reads file " boot.ini» and in the case of multiple systems installed - displays a menu for selecting them
- starts the program ntdetect.com”, which collects data on the composition of the hardware of the computer (ntdetect.com builds a list, which is then used in the key system registry: HARDWARE branch HKEY_LOCAL_MACHINE)
- initializes the file " ntoskrnl.exe”(kernel of the operating system. “Kernel” is the kernel) and transfers 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 - the level of hardware abstractions). It separates (abstracts) the system core 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 that, the operating system starts itself. This is if - in short :) There is still a lot of "interesting" things going on, but we are not interested in this now, but the inscription NTLDR is missing and how to fix it?
NTLDR is missing how to fix and what to do?
Now, understanding what role and at what stage of the system start the operating system loader performs, we can begin to solve the problems associated with it.
Let's remember the following: for the successful start of 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 the download. Let's take a closer look at it.
To do this, we need to display in Windows Explorer hidden by default system files and folders. 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 checkbox "Hide protected operating system files" and put the switch on "Show hidden files and folders". I also recommend removing the "bird" from the item: "Hide extensions for known file types".
Click "Apply" and go to our "C" drive. Here's what we see there:
All of our three files responsible for loading the system are present. Excellent!
I propose to simulate an accident and delete all of them! :) This is the easiest way to visually show what would happen if any of these files were corrupted (or missing).
Delete them all and reboot. After the reboot, we see the inscription NTLDR is missing Press Ctrl+Alt+Del to restart. Exactly what we need! :) Let's get down to recovery.
To begin with, our plan of action: 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 for the missing (damaged) ones. Iron logic! :) And where can I get them? Here are several options:
- download from internet
- write to a friend
- use the Windows installation disk (copy them from there)
Since we are our own admins and are used to solving issues without outside help, we will choose the third option! :)
To do this, we need a disc with the original Windows XP (in the case of Windows 2000, the process looks almost the same), it is highly desirable from the one that we installed on the computer. Upload it to , expose it to BIOS boot from the CD and wait for the window we need to appear.
At first it looks like a process Windows installation 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: press the button " R" on keyboard.
Note: what does the recovery console do? It allows you to get limited access to the system (in text mode) if it doesn't load. In "text" it means that we will not be able to use the mouse (since there will be no graphical shell itself) and we will need to enter all commands from the keyboard.
Already scared? When I saw it for the first time, I was scared, then it passed :) In general, anyone familiar with DOS will feel absolutely comfortable.
So, after launching, the program will scan the disks for the presence of operating systems from Microsoft on them and display the result in a column with numbers, starting from the first one.
Since we have one system, then (in the photo below) we see that there was one OS under the number " 1 ' in the folder 'C:\WINDOWS'.
Next, we are asked: "In what a copy of Windows should you sign in?" Naturally - in the first (and, in our case, the only one). Press the number " 1 ", then - the key" Enter". We are then asked to enter the administrator password. If you have it - enter it, if not, then just press "Enter" again.
Here we are logged in! This is evidenced by the inscription at the very bottom "C: \ WINDOWS" and a blinking cursor for entering text commands.
What commands do we need to know? First of all, those that respond to our navigation (movement) on the disk. After all, we will need to go into the folders.
The task is to go to the "C" drive and view its contents! Just having a mouse at hand :)
Take a close look at the screenshot below:
Let's wrinkle our brains and we'll figure it out! First of all, what does the entry "C:\WINDOWS>" mean? This is the ID 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 the execution of the 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 "get out" of 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 similar to the back arrow in Windows Explorer.
Just remember that things like space, indent, slash left or right are very important here. There is only one correct spelling and 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 inscription appears on the monitor NTLDR is missing, but how to fix it, what to do and immediately - to the master! :) And the master - refers to the "origins", loads into the recovery console, enters simple commands from the keyboard and - gets a positive result :)
We move on. After that, press "Enter" (this ends the input of any command) and see the symbol "C:" We left the "WINDOWS" directory one level up and got to the root of drive C. And in it we enter the following abbreviation: " dir» (directory), which will show us the contents of the current directory.
We see all our files and directories that are on it.
Now let's go to our CD or DVD drive. We have in it installation disk Windows, remember? To do this, enter the command " D:" (without quotes). The main thing here is to "guess" under what letter of the alphabet you have it. I have - one logical partition (it is also a system partition), therefore - the letter "D" is - 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 the brute-force method :)
In the folder with our installation disk, we give the already familiar command "dir" (content overview). 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 (which we deleted on purpose).
To do this, we need to go to this folder and see if this is the case? We enter the command "cd" (change directory) and - the exact name of the target directory is "i386". We press enter. We see the result: D:\i386> We have moved to the directory we need. In it, we will execute the content browsing command - "dir".
Among the large number of files contained in it, we can see the one that we need!
Now - we write the copy command, indicate which file we copy and where: " copy ntldr c:» It is necessary to write in this way, observing all spaces, colons and putting a slash at the end.
The system tells us that one file has been successfully copied to the root of drive C. Let's check this fact. Let's go to the system drive (you should already know how to do this), enter "dir" and see this picture:
There was a file Windows bootloader- ntldr.
Super! We just solved the problem with the NTLDR is missing message when booting the computer from the command line! Let's reboot and taste the fruits of our labors :)
To do this, we just need to type in the console the command " exit» (exit) and press enter. The computer will start to restart. But... so far we won't see anything joyful, except that the inscription NTLDR is missing will no longer appear, and the system will reboot cyclically without displaying any more messages. Remember, in a fit of experiment, we deleted two more files "Ntdetect.com" and "boot.ini"?
The first file can be copied from the same "i386" folder of the installation disk. Let's do it. Let's enter the recovery console, then - to the directory with this file and execute the copy command.
Note that the "Ntdetect.com" file 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. We go to drive C and look around there:
We see - both files we copied are in place. We try to reboot - "exit". When loading, we, again, do not see NTLDR is missing, but we observe this picture:
The “boot.ini” file is not only wrong, we don’t have it at all! But Windows is smart and "tells" us that it's ready to start booting without it. And - indeed, in a few seconds we can observe the successful start of our OS.
The problem is that such an entry will not go anywhere and will appear every time you turn on the computer (and if the configuration file is really wrong, 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 with notepad. Let's do it. Here's what's inside it:
Let's quickly analyze its contents.
- boot loader - boot section (just a notation)
- timeout=30 - countdown timer until OS boot starts (in seconds)
- default - the operating system that will be loaded by default (relevant for systems with several operating systems installed at the same time)
- operating system- boot parameters of the system (systems). Each subsequent one adds a new line here.
Now consider the values of the parameters 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» - 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 “0” should be here, but if we have two hard drives and the OS is installed on the second, then in this case the value of "rdisk" will be equal to "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 my Windows is loaded from the “C” drive, then “partition” will be equal to “1”, if - from the “D” drive, 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 quotes, you can write anything. This is textual information (the download ID) and has no effect on anything. Parameter " /fastdetect” tells the bootloader that (if there is one installed system) it should ignore the “timeout” timer value and immediately load the operating system without displaying a boot selection window.
Knowing these simple things, you can set the desired values right in a text editor (notepad) and save the file. Upon reboot, the new values entered by us will be read from it. But I want to show you one more method specially provided for such cases by developers from Redmond.
We boot into our (I hope, already familiar console) and enter the command “ bootcfg", from English. "boot config" (boot management). Since we entered the command without parameters (did not indicate what it should do), the system will show us everything possible options its applications:
Red marked "keys" ( additional options) of this command, which we can type directly after it. Look, read, everything is in Russian.
Let's start with the "key" list” to display a list of systems already in the boot list. Before the "key" put a space and a slash.
We are "telling" that there are no items in the load list available to display. It is not surprising, because we do not have the boot list itself (boot.ini), we successfully deleted it.
We use another "key" of this command - " add" (add), you can and - " rebuild' (rebuild). The result will be the same.
We "forced" the program to scan all disks for the presence of installed systems Windows family. 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? Namely, in the "boot.ini" file, which was created at the same time :) We put the number "1" - the serial number of the found OS. Next - a suggestion to enter the download ID. You can write anything. For example - "My Windows XP". In the line "Enter boot parameters" I advise you to enter "/fastdetect" (so as not to display the timer in vain).
Let's make sure that the "boot.ini" file is really created in the root of the drive. Let's go to it and execute the "dir" command.
And there is! We reboot and make sure that the download goes smoothly, the inscription NTLDR is missing does not appear, no other windows either. Q.E.D!
Let's go into the loaded system (already with the mouse) into the bootloader configuration file and see what it contains?
Pay attention to what is highlighted in red. This is exactly the data that we entered from the console, and they were recorded at that moment in given file.
In conclusion, I would like to note the following, if you see the inscription when loading NTLDR is missing, then the problem can be solved in another way. Remove the hard drive, connect it to another computer with the same system and overwrite the necessary files from there. It's up to you to decide, but I think the skills of working in the console will definitely come in handy in the future!
Hello everyone, dear friends! Today I tried to turn on my computer, but it didn’t work, some incomprehensible inscription appeared something like this: “NTLDR is missing”, I don’t even have a clue what it is and why my computer stopped booting. I have a lot of important information on my computer, have I really lost everything now?? Help me please!
These are the letters to me recent times began to come to my email from many users, with a plea for help. Well, let's figure out what actually causes the appearance of such an inscription when the operating system tries to boot successfully.
An error - NTLDR is missing of this kind occurs extremely rarely, but not every user can cope with it. The first thing that comes to the mind of the user after several attempts to reboot is reinstalling the operating system (OS). This is long, and sometimes unprofitable, because there may be important files on the system disk. In today's article, I will tell you how to deal with the error without reinstalling the system. The methods are suitable for all relevant Windows versions(XP, Vista, 7, 8, 8.1, 10).
And there are several reasons for the appearance of "NTLDR is missing":
- corrupted boot files of the system;
- conflict due to the installation of another OS;
— installation of an additional hard drive;
NTLDR is missing What to do?
Hardware failure.
Reasons #1 and #2 - Damage boot files
So, instead of loading Windows, the error "NTLDR is missing" appeared. In the event that an error appears due to damage to boot files or a conflict between two systems, these methods will help you. Check if you have a Windows installation disc or flash drive that is in this moment is on the computer.
If there is no disk, then check out the following article, from which you will learn how to create such a disk or flash drive:
If the cherished flash drive or CD / DVD is present, then the sequence of actions for Windows Vista, 7, 8, 8.1.10 is as follows:
1. We restart the computer and insert the disk or USB flash drive.
2. Now we need to set the boot priority from the media, and not from the hard drive. To do this, you need to go into the BIOS and set the "boot priority" on CD-ROM or USB. Almost all modern computers can get into boot menu without entering the BIOS. Try pressing F8/F9/F10 during boot. Then if it didn’t work with “F8”, then reboot and press “F9”. You can read more details
3. If the priority is set, then the download will already be from the disk. We are waiting for the installer to perform automatic operations. The installer will offer you two options: install new system Or restore the current one. Select "Restore current" and wait for completion. Done, problem solved.
Note for Windows users xp.
We carry out the first two points of the instruction located above. As soon as the installer starts, we immediately start pressing the "R" button - do not be afraid to overdo it. You will be given a list of OSes that need to be restored. We select the desired system (for this, the installer may ask you to press the number and Enter) and confirm your actions with the "Y" and "Enter" keys. The last action is a set of commands FIXBOOT and FIXMBR- the procedure is shown in the screenshots below.
What if the above actions did not lead to a positive result?
If the commands did not return the files, then you need to go the other way - using the same recovery console. Our task is to copy two files from your Windows boot drive. Using the "copy" command, transfer the files "NTDETECT.COM" and "NTLDR".
To do this, you need to register this in the recovery console: copy
where
Actions on the command line will look like this:
copy f:\i386\ntldr e:\
copy f:\i386\ntdetect.com c:\
In commands, "f:\" means the letter of your Windows boot drive;
"c:\" is the address of the drive where the operating system is located.
Perhaps you have it on drive "d", and not on "C" - fix it. Also the name of the CD/DVD may be different. Check this data and write two simple commands - the problem will definitely be solved.
Reason #3 – Active Disk Change
After installing an additional hard drive, the error most often occurs due to incorrect user actions. The already familiar recovery console and the standard DiskPart utility, which is launched using the command diskpart on the command line.
When the utility starts, proceed as follows:
Enter the list disk command - you will see a list of hard drives that are connected to the computer.
If only one disk is present, the program will display disk0.
We need to enter the command "select disk 0" to select the disk with the operating system to boot.
After selecting the disk, we drive in the “list partition” command to display a list of partitions on the disk.
We select the partition with the operating system, it is most often signed "select partition 1".
To complete the procedure, enter the command "active". Done, the partition with the operating system is again the main one - reboot and use it.
Reason #4 - hardware failure
If the instructions above did not help, then there was a hardware failure. personal computer. The hard drive or the motherboard controller, which is responsible for the operation and recognition of hard drives, can fail. Most often this problem occurs on older hardware. But still, if a breakdown occurs, then there is usually only one way out - replacing the faulty equipment. In some cases, craftsmen repair or replace only the failed item.
Concluding the article, I would like to add that if the problem still turned out to be damaged files boot, and the disk with Windows is not found, then you have to go for another. The main thing is that the version of the operating system on the disk matches the Windows installed on your computer.
That's all for today, how do you like the article? If you have any questions wishes, then ask them in the comments!
Almost everyone had a similar error, but not every user of a computer or laptop can fix it. The most popular solution is to format the hard drive and install a clean operating system. This method has two big disadvantages: the loss of all accumulated data and the loss of time. In this article, we will consider simple, but at the same time effective methods.
While loading OC you get a warning:
NTLDR is missing
Press CTRL+ALT+DEL to restart.
Consider the main causes of the error:
1. A large number of files in the root of the system disk - in Windows folder. Because of this, there is a strong fragmentation of the MFT table of the root folder. If the root MFT table contains a large number of files, it can become so fragmented that an additional allocation index needs to be created. Since the files are listed in alphabetical order in the allocation indexes, the NTLDR file may end up in the second allocation index. This will display an error message.
Basically, the data is not copied to root folder. The indicated problem will appear if any program constantly creates and deletes temporary files.
2. Conflict of loaders of heterogeneous systems (Windows and linux) installed on the same computer.
3. NTLDR bootloader Ntldr and Ntdetect.com may be removed or corrupted for various reasons as a result of user actions or software errors.
4. The error message "NTLDR Is Missing" may appear after changing the active partition. For the stable operation of the Windows bootloader, it is necessary that the system files that it uses are located on the active partition.
5. I want to note that the error "NTLDR Is Missing" can be not only software, but also hardware. This is both a hard drive failure and outdated version BIOS on motherboard(extremely rare, but it happens), connecting another disk with an existing OS to the computer.
6. As well as other occasions that are less popular.
Troubleshooting:
First decision. If you or a good neighbor has a computer with the same operating system, you can copy the Ntldr and Ntdetect.com files or use the Windows Recovery Console.
If there is no computer, then you can copy these files using programs: Windows LiveCD, Linux LiveCD, or other programs (for example, such as Acronis Disc Director, etc.) that can work without an operating system, booting from BIOS by setting boot from CD -ROM.
Second solution: AT system file boot.ini file (Location: c:\boot.ini - is hidden by default, so you need to configure Windows to show such files.) check that the path to the operating system is correct. To fix this file, you can also boot using the programs that are written in the first solution.
The structure of the "Boot.ini" file with one operating system on the disk should look like this:
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional" /fastdetect
Third decision. Each PC user must have a distribution kit with an operating system that is installed on his computer. The method below is rightfully considered the fastest and easiest.
Insert the disk with your operating system (Windows XP in my case) into the drive, and do not forget to set the priorities in the BIOS - CD-ROM. After booting from the disk, press the R key to open the recovery console.
Now we will restore. If one OS is installed on the computer, then the following text will appear:
1: C:\WINDOWS
Which copy of Windows should I sign in to?
Type 1, press Enter.
A message will appear:
Enter administrator password:
If your account password has not been set, just press Enter.
- Now enter the fixmbr command and press the Enter button.
- A notification pops up:
**WARNING**
This computer has a non-standard or invalid master boot record. Using FIXMBR can damage the existing partition table. This will result in the loss of access to all partitions of the current hard drive.
If there are no disk access problems, it is recommended to abort the FIXMBR command.
Are you confirming the writing of the new MBR?
- Enter the letter Y (yes, yes) to confirm and press Enter.
- The message appears again:
A new MBR is made to the physical disk \Device\Harddisk0\Partition0.
The new master boot record has been successfully made.
- After the system prompt appears: C:\WINDOWS>
- Type fixboot and press Enter.
- After that, a message will appear:
Destination partition: 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:
The file system on the boot partition is NTFS (or FAT32).
The FIXBOOT command writes a new boot sector.
The new boot sector has been successfully written.
- The system prompt C:\WINDOWS> will appear
All that needed to be done, now you can exit the recovery console, for this, enter the exit command and press Enter. After that, the computer will reboot.
Do not forget to remove the boot from the CD-ROM in the BIOS by setting the boot from the HDD (hard disk).
The fourth solution is for older computers. We disassemble the system unit (this is not so scary, you will only need a screwdriver) and replace the cable slot or connect a new cable.
This is what the hard drive cable looks like: 
If you have any questions about the article or have not solved your problem, then go to our computer forum and we will definitely help you.