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 caused the appearance of such an inscription when trying operating system boot up 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 on system drive may be important files. In today's article, I will tell you how to deal with the error without reinstalling the system. Methods are suitable for everyone current versions Windows (XP, Vista, 7, 8, 8.1, 10).
And there are several reasons for the appearance of "NTLDR is missing":
- damaged boot files systems;
- 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 - Boot File Corruption
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 installation disk or a Windows flash drive that 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 the following:
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 you can get to the "Boot Menu" without going into 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 boot disk Windows. 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 in 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 - a list will be displayed in front of you 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. Can fail HDD or the motherboard controller, which is responsible for the operation and recognition of hard drives. 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!
If you have never encountered this error, then you are very lucky. But, often, it occurs exactly when you do not expect it at all.
Many users immediately begin to reinstall the system, because formatting it is a very reasonable decision.
But what to do if you have absolutely no time to reinstall or, for example, there is a very small number of files on the system disk. important information that you don't want to lose? It is quite possible to deal with this problem without reinstallation, and we will help you figure it out.
What does this error mean?
Literally, the abbreviation means: nt loader, that is, it is a load based on NT technology.
In other words, such an inscription can be interpreted as the absence of a boot file.
From here you can understand that your boot file is damaged, but do not worry: this trouble can be solved without even reinstalling the operating system.
It most often appears in these versions of operating systems. Windows systems like 2000, Vista, XP, 7 and 8.
Therefore, we will show how to fix this error, using the example of XP versions (which is similar to 2000 and Vista), as well as the seventh version (identical to eighth and tenth).
In addition to damage to the boot file, an error can occur in the absence of others.
And, in order to correctly and successfully launch into the operating system, you must have three main files that are in active mode on your device. It:
- Actually, the NTLDR file with the loader code;
- The boot.ini file with requests for the formation of a selection menu and launch settings for the required operating system;
- The ntdetect.com file, which collects software status information.
And if at least one of these files is missing, then you are probably guaranteed a failure to boot your device in the near future.
At any Windows versions, usually, this file is located in the root folder on the system drive, that is, on drive C.
By the way, in the same place, the above files are often located. boot.ini and ntdetect.com.
Reasons for the error
The ntldr is missing error could occur due to various reasons, for example:
- Damage to the cable that connects the motherboard to hard drive devices;
- Listed boot device no system hard drive. In chapter boot device Priority in the BIOS needs to check the device sequence at boot time;
- Failure of the hard disk due to the failure of memory sectors;
- When installing the disk, the jumpers in it were incorrectly set;
- The NTLDR file has been deleted from the operating system by a virus;
- The boot.ini file has been moved or removed from the root partition;
- The NTLDR and NTDETECT.COM files were assumed to be temporary and moved to a different folder;
- The presence of too many files in the root directory. The peculiarity of NTFS is that all data about the files are in the MFT - database. And when there are too many files, the database divides them into segments, the files in which are sorted alphabetically. If there are a lot of files, then NTLDR may not be in the first segment. But the problem is, when loading, the operating system accesses only the first segment, in which it may not find the desired file.
This list of reasons is not complete. But these can happen, both separately and simultaneously with others.
Software error
Before fixing the error, you need to figure out what we are facing and understand how the system startup process takes place.
Everything related to the launch of the hardware does not bother us, we will move on to the software.
First, the computer reads the master boot record (MBR), which is located in the first section of the zero cylinder of the system disk.
It is very small in size, only 512 MB, but contains a code that helps the computer to start up.
The boot record analyzes all disks, finds an active partition in them and transfers control to the boot sector that is located on it.
And this sector, called the Boot Sector, contains all the information about the size and type of the file system and disk parameters.
Important:
in versions older than 7, Winload is used instead of the NTLDR file, which is located at C:\Windows\System32\winload.exe.
Having received control, the bootloader executes the following commands:
- The central processor switches to the 32-bit mode;
- Access to the file system is organized;
- Displays a menu for selecting systems, if several are installed, by obtaining data from the boot.ini file;
- Launches ntdetect.com (an application that collects information about hardware);
- Activates and transfers all information about the hardware to the ntoskrnl.exe file, which is the core of the operating system.
And then the operating system starts.
How to fix the error?
After we figured out at what stage of the launch the error occurred, we can begin to fix this problem.
First, let's consider the occurrence of this error on Windows versions such as 2000/XP/2003, because the solution for them will be similar.
Once again, in order for the launch to be successful, you must have the following files:
→ Ntldr;
→ Ntdetect.com;
→ boot.ini.
Let's take a closer look at the bootloader and its maintainers.
in Windows 2000/XP/2003/Vista
- First you need to show the hidden system folders and files in "Explorer" . Click section "Service" and find there "Folder properties".
- Next, bookmark "View" and from points "Hide protected files" remove checkboxes. And at the point "Show hidden files» and folders put a mark. In addition, we recommend from paragraph "Hide extensions for known file types" also uncheck.
- We apply all the changes, and, going back to the system disk window, we will see necessary files, which are responsible for loading the system.
What to do if there are no files
If you do not have one of the files, then this, in fact, is the reason that you cannot boot the system. But don't panic, they can be restored.
Since we do not have the necessary files, they need to be found somewhere in the place to replace the missing ones. There are several options:
- Copy files from the installation disk;
- Copy from another device;
- Download from the net.
The last two options are too simple and can be easily handled, so we will look at the first and most difficult option - through the installation disk.
- First, insert it into the drive and start booting from the CD and set the boot to the BIOS.
- At first glance, it may seem to you that standard reinstall system, but when you see a window, as in the figure, you must select the option To restore Windows XP using the recovery console, press "R" and, in fact, press R on the keyboard.
- The Recovery Console helps you access the system in text mode if it doesn't load. You will not be able to control with the mouse, so you will only have to use the keyboard.
- The program will scan the disks, checking them for the presence of an OS, and then display the results found. In our case, only one operating system is installed on the computer, which is displayed at number 1.
- Pay attention to the question which a copy of Windows should you sign in? Since it is one, press the number 1 on the keyboard and the Enter key to confirm the entry. And also, if you have an administrator password, then you must enter it, if not, press confirmation again.
- After that, you will be logged in. To navigate and search for the necessary files on the disk, you need to know the basic commands.
Since we need to see the contents of the disk, we first need to enter it. To do this, enter the command "cd ..", which means:
- cd - change folder
Space and two dots - is an analogue of the arrow Back in "Explorer" .
- Be sure to follow all the spaces, dots and other characters, as they play a very important role and the further loading of the command depends on the spelling.
- Then press Enter and enter the English letter C to get into the folder of the system disk. To display the contents there, enter the dir command.
- After that, we need to go to the CD drive with the installation. Enter in the command with the path the letter under which the disk with optical drive. If you do not remember, do it by selection - sooner or later you will guess. For example "D:", "F", "G" and so on.
- After selection, enter the dir command and look for the I386 folder in the contents - it contains the files with the bootloader that you need to copy.
- Once again, we will repeat how the whole path will look like.
- Among all the displayed files, you need to find the one you need.
- To copy it, you need to enter the command "copy ntldr c:", which indicates in turn which command is being executed, with which file and where to copy it. Again, don't forget to pay attention to all the signs! Ideally the command should look like this:
Successful OS startup
NTLDR is missing in Windows 7/8/10
For these versions, the solutions are similar to the previous one:
1. Boot the system with external media and get into recovery mode.
3. After that, you need to select the method of system recovery that interests us - the console line.
4. Unlike the previous method, here you need to enter only two commands:
● bootrec /fixmbr
● bootrec /fixboot
/FixMbr – given parameter writes basic information to be loaded into system partition. Used to solve problems that are related to loading or deleting when loading custom code.
/FixBoot– writes to the system partition of the boot sector.
5. After entering the commands, press Enter to confirm and reboot the device.
conclusions
If these options are uncomfortable for you, then you can try another one.
Remove from your computer hard disk, move it to a computer with exactly the same version of the system and overwrite the files from there.
But, the skills of working in the console will never become superfluous and can always be useful to you.
Therefore, do not rush to reinstall the OS, try to figure it out on your own first.
How to fix NTLDR is missing error
The video tutorial deals with the situation when the NTLDR is missing error appears when the computer is turned on or restarted, which can be caused by deletion or damage to the boot.ini, ntldr and NTDETECT.COM files
Some users, working at a computer, may have encountered a little common, but very unpleasant situation, when the error NTLDR is missing Press Ctrl+Alt+Del to restart appeared on the screen. A little lower I will talk about the ntldr is missing error and what to do in this case.
When NTLDR errors is missing a novice user immediately tries to reinstall Windows, but reinstallation may take longer than fixing the situation for more short time. Let's make sure you're on the right page, I'll show you what this error looks like:
Reasons for the error
Before proceeding with the solutions to the NTLDR is missing error, you can read the list of reasons why it can appear on your computer.
- If the computer has multiple systems installed.
- The Ntldr file can be deleted or corrupted due to user carelessness or software bug(s).
- Changing the active partition on the hard drive can also cause this error. To boot Windows, you need system files that Windows is running were on the active section of the hard disk.
- The NTLDR is Missing error can appear not only due to a software error, but the hardware of the computer can also cause it. When such an error appears, you should pay attention to the hardware of the following components: hard drive, hard drive cable problem, outdated version BIOS on motherboard, another hard drive that has another Windows system installed.
- Noticed the error also in other cases.
So, we figured out why this error might occur, now let's talk about how to fix ntldr is missing error on your computer.
Tip #1. If you have at hand another computer with the same operating system that is installed on you, then copy the Ntldr and Ntdetect.com files or use the console Windows Recovery(more on that below).
If there is no computer at hand, but there is a hard drive with the system, then you can copy the NTLDR and Ntdetect.com files using programs: Windows LiveCD, Linux LiveCD, Acronis Disc Director or other programs that can work without an operating system. To boot from such discs, you need to go into BIOS and set boot priority from CD-ROM.
After a reboot, the NTLDR is missing message should disappear.
Tip #2. In the boot.ini file, you need to check the paths to the operating system for correctness. To edit given file, you can boot using the programs I mentioned above.
The structure of the "Boot.ini" file with one operating system looks 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
Tip #3. How to fix NTLDR is missing if the above methods did not help? Each advanced user should have a distribution kit with an operating system that is installed on his computer. I think this method is the fastest way to get rid of the ntldr is missing error, because you will need to do a minimum of actions, although at first glance everything seems a little incomprehensible. If you don’t know how to set Windows to boot from the drive, then follow the link below and read this information at about the beginning of the article: “.
To do this, insert the Windows disc into the drive , don't forget to put in BIOS boot from CD-ROM. After booting from the disk, press the R key to open the Recovery Console.
Now let's start the recovery. If the computer has one OS installed, the following information will appear:
Which copy of Windows should I sign in to?
Enter 1, click Enter.
A message will appear:
Enter administrator password:
If the administrator no password then just press Enter.
The following message will appear:
**WARNING**
This computer has a non-standard or invalid primary 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 a letter Y(yes, yes) and press Enter.
A message will appear:
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>
Enter 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 a letter Y(yes, yes) and press Enter.
A message will appear:
File system in boot partition: NTFS (or FAT32).
The FIXBOOT command writes a new boot sector.
The new boot sector has been successfully written.
The system prompt will appear C:\WINDOWS>
We have done all the necessary operations, now we exit the recovery console. To exit the recovery console, enter the command exit and press Enter. After that, the computer will restart.
The next step in the BIOS is to remove the boot from the CD-ROM by setting the boot from the HDD (hard disk). Now you can pull out the Windows installation disk and check for NTLDR is missing.
Method number 4. In some cases, juggling the cable (disconnect and connect) or connecting another cable helps. If the NTLDR is missing message persists, then try connecting another hard drive, and then connect your drive.
From what this error may appear, and what to do with ntldr is missing, you know, it remains to use one of the methods. If you have not encountered such an error, then print this article, because at the most inopportune moment you may find yourself in such a situation.
I want to warn you that before you take any action regarding serious problems with Windows, you need to do backups data.
Errors of this kind are a serious thing and, unfortunately, occur quite often. On the agenda NTLDR Is Missing. To begin with, we will consider the causes of this problem, and then we will solve it.
Why does NTLDR Is Missing appear and how to solve this problem?
The error can be different and may look, for example, like this:
Either like this:
The root of the problem lies in the inability of the operating system to boot using boot files, simply speaking, access to them is lost. This may be due to the fact that they are damaged or removed due to the fault of the user. Therefore, you will not be able to get into Windows, but there are some other reasons.
Option 1
The NTFS root partition contains a large number of various files, from this section the system is booted. If you try to somehow clear these files, then you are unlikely to achieve a positive result.
This can be solved by using special utility from Microsoft - BCUpdate2 . It is freely available on the Internet, you can ask Microsoft technical support.
Now let's get down to business. You will need a boot floppy that you boot from. Launch Command Prompt (Shift+F10) and enter the following command there:
| BCUpdate2.exe C: /f |
To start the program, you need to press the Y button on the keyboard. After completion, the computer can be restarted.
Option 2
If you have installed two operating systems, for example, Windows XP and Windows NT, then the second bootloader has a simpler form, which causes incompatibility with XP. In general, the problem may be if the operating systems are NT and XP.
To solve this variant of the problem, you need the Ntldr boot files and the Windows XP installation disk. So, we boot from the disk and start the recovery console, for which we simply press the R button. Now we select the partition to be restored, and then we write the command, if it doesn’t help, we write the command.
After that, you can reboot and hope that everything will work.
Option 3
You can restore the boot data in another way, for this you again need to boot from the boot disk, but in MS-DOS mode, as soon as you have done this, you need to copy the Ntldr and Ntdetect.com files to the root of the boot disk folder.
When we move files, a problem may arise. The solution is simple - remove the attributes that block us from moving files. Here's how to do it:
| attrib ntdetect.com -r -s –h
attrib ntldr -r -s –h |
Option 4
It's even simpler, but you need another computer that has a working system. We take out the hard drive from our PC and connect it to a working one. Go to utility "Disk Management" and look at the created partitions and disks. Whether they work normally, then make the first partition of the disk active. Now copy the NTLDR and NTDETECT.com files there. You can re-insert the hard drive into your computer. Resetting the BIOS is recommended.
There is no way to use another computer or you don’t have one, try installing a second system on your computer and do the above steps from there.
Option 5
You can try running the recovery console again. To get started, you must have a boot disk or flash drive, open the console with the R key, enter the following:
| copy e:\i386\ntldr c:\
copy e:\i386\ntdetect.com c:\ |
We copy the NTLDR and NTDETECT.COM files to the system disk. The command specifies the path from where the copying takes place and drive C, the letter e:\ is the drive.
Option 6
When changing the active partition, the same error may appear, you can solve it like this:
- Boot from floppy;
- Launch Command Prompt and enter the command fdisk;
- Confirm the inclusion of support for large disks with the Y key;
- Commands appear where you select an item "Select Active Partition", and then make the necessary section active.
Now we can copy boot files to the active partition.
- Boot from a boot disk, flash drive;
- Press R to open the recovery window;
- We enter the command cd... It is needed to get to the root of the disk. (You may have to enter several times);
- Once you are in the root directory, enter the drive letter, for example, "e:";
- We enter the command cd i386;
- Copy NTLDR to the boot drive - Copy ntldr + boot drive letter;
- Exit with the command exit.
These are all the main and well-known methods for dealing with the NTLDR Is Missing error. Sometimes a banal reconnection of the hard drive, replacing the cable can help. It is possible to update the BIOS, but this is done with caution. The disc may be physically damaged and should be sent in for repair.
NTLDR is missing when booting Windows XP or bootmgr is missing when booting Windows 7
You turned on the computer, but when you boot up windows XP writes NTLDR is missing and does not load or does not load Windows 7 with an error bootmgr is missing. Don't panic. Usually the problem is fairly easy to fix.
Let's understand what the inscription means ntldr is missing(in Windows 7 error bootmgr is missing). The message indicates that Windows bootloader(file ntldr or bootmgr ) not found. The bootloader is the program that is first loaded into RAM and controls the further 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 offers 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 being loaded (drive C:). If it is not there, then this error appears.
In Windows 7 bootloader bootmgr can be located both on the partition with the operating system (drive C), and 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 on the disk may be primarily logical errors in file system. These errors may appear, for example, after an incorrect shutdown of the computer or after it freezes, as well as due to damage to the hard drive itself.
2) Also, the cause of this error may be the banal deletion of the 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 often given error happens after the boot disk, i.e. drive C, has been compressed.
5) The cause of damage to the ntldr and bootmgr files can be physical damage to the hard disk (bad sectors or bad block "and).
NTLDR is missing - how to fix
To fix the error, you will need an ERD Commander boot disk (you can download the disk image, and read in this article: how to burn the image to a CD) and an archive containing ntldr files and ntdetect.com: .
If you don't have a floppy drive, you can make a bootable ERD Commander USB stick. The archive with the files must be unpacked to a USB flash drive, so that later it can 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 boot disk or flash drive ERD Commander. Choose a version ERD Commander for your version of Windows. The screen will be black for some time after the start of loading - don't be alarmed, it should be so. You can judge that the download is in progress by the activity of the drive or flash drive. Then a dialog box will appear asking you to connect to the network in the background. Click the button Skip Network Connection (in ERD 6.5, 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 drive C: and press EnterIf 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.
Pay attention to paragraph in bad sectors, showing the number of unreadable sectors on the hard drive. If this setting is different from 0, I recommend trying to repair unreadable sectors with specialized programs or replace the hard drive. Once the disk errors have been fixed, try booting Windows normally. In many cases, the operations performed are enough to restore Windows XP boot.
If after doing this the NTLDR is missing or BOTMGR is missing error still appears, proceed to the next step.
2) Check for NTLDR and NTDETECT.COM files on the system drive
For Windows 7, this step is not always relevant, so often the bootloader is located on a special hidden partition and it is not possible to remove it. Therefore, for Windows 7, this step can be skipped.
Check if there are files ntldr and ntdetect.com in the root folder of drive C:. To do this, download ERD Commander and run 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 you want to copy and click right click mice. AT 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 if you want to replace the file. Click Yes to replace existing file the one you are copying.
Now try restarting your computer. If this does not help, go to the third paragraph.
3) Make sure the disk partition on which Windows XP is installed is active
Windows can only boot if the ntldr or bootmgr bootloader is located on the active partition. You should check to see if the partition has accidentally become inactive.
This will help Acronis software Disk Director. The boot disk image can be downloaded. Burn the image to disk and boot from it.
From the disk menu that appears, select Acronis Disk Director 11 Advanced.
Now start the management console (Work with the current machine)
The drive (C:) (or the one on which Windows is installed if it is not on the C drive) must be active. The section status should contain the inscription Active(underlined in the figure below) and graphic image section should have a red flag. For Windows 7, the active must be hidden section 100 MB at the beginning of the disk, if it exists.
If the disk with the bootloader is inactive, then the reason for the error NTLDR is missing in Windows XP and BOOTMGR is missing in Windows 7 it is in this. 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 stating that this may affect the loading of the operating system. Click OK.
Now we need the program to perform the scheduled operations and make the drive (C:) active. To do this, click on the button Apply Scheduled Operations.
A window will appear where the operations to be performed will be written. Click Proceed.
After completing all operations, press the button close.
Then close the main window Disk Management and press the button Reload.
Try booting your computer in normal mode. Windows should boot normally.