Fault phenomenon: The power-on test is normal, but it is stuck when entering the system, that is, the system is booting, and it is displayed
NTLDR is missing,Press CTRL+ALT+DEL to restart.
After thinking, analysis concluded:
The system is an NT kernel, and LDR is the abbreviation of the commonly used loader in the operating system. Therefore, the failure may be caused by the loss of the system boot file, and the name of the file is NTLDR.
2. The computer is stuck when entering the operating system, that is, when the system boots, so it is judged that it may not be able to boot the system and lead to the inability to enter the operating system.
The following is an explanation of the fault on the official Microsoft website:
When starting the computer, I received an error message "NTLDR is missing" (NTLDR is missing)
symptom
After copying multiple files to the root folder of the boot volume using the NTFS file system, you may receive the following error message the next time you start the computer:
NTLDR is missing
Press CTRL+ALT+DEL to restart.
If you delete a file copied to the root folder, the main file table (MFT) allocation index does not drop to the original size.
reason
This problem may occur if the MFT root folder is fragmented. If the MFT root folder contains multiple files, the MFT becomes so fragmented that it requires another allocation index to be created. Because the files are mapped alphabetically into the allocation index, the NTLDR file may be pushed into the second allocation index. If this occurs, you will see the error message described in the "Symptoms" section of this article.
Generally, files are not written to the root folder. This can occur if a program periodically creates and deletes temporary files in the root folder, or if many files are copied accidentally to the root folder.
Solution
To resolve this issue, contact Microsoft Product Support Services for the Bcupdate2 utility. For more information on how to contact Microsoft Product Support Services, visit the following Microsoft website:
/selectassist (/selectassist)
Alternative Method
To work around this issue, create a boot disk to boot your computer.
For more information on how to create a boot disk on a Microsoft Windows XP-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
305595 (/kb/305595/) How to create a boot disk for NTFS or FAT partitions using Windows XP
For more information about how to create a boot disk on a Microsoft Windows 2000-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
119467 (/kb/119467/) How to create a boot disk for an NTFS or FAT partition
[quote]
We can use the "compensation method" to repair the conclusions drawn by ourselves and the instructions of Microsoft's official website, that is, copy the lost file from other system disks or computers, fill it up, and then enter the operating system normally.
The following are the solutions summarized by your own experience and online:
(Step 1) Enter through the fault recovery console (assuming that the G drive is the optical drive letter...)
copy G:\i386\ntldr c:\(Enter),
Then enter:
copy G:\i386\ c:\(Enter)
At this time, the system needs to prompt something, enter y, and then press Enter. (The problem should be considered to be solved at this point. The next step is to determine whether the problem has been solved.)
Enter c:\, and if the information displayed normally, restart it, which means that the problem has been solved.
Question summary:
The NTLDR file is a boot file for WinXP. Backup should be given when the system is normal.
Description of NTLDR File: NTLDR is a hidden, read-only system file used to load the operating system.
Extraction of NTLDR file: The NTLDR file is WinXP boot file. When this file is lost, the system will prompt it to be missing and requires pressing any key to restart. It cannot enter the WinXP system correctly. This file can be extracted under the fault recovery console. This file exists in the i386 directory of the installation CD. The extraction method is as follows:
Enter the system recovery console, go to the C drive, enter "copy X\I386\NTLDR" (Note: The X here is the optical drive letter) and press Enter. If the system prompts you to not overwrite it, press "Y", and then enter the exit command to exit the console and restart.
Attached:
The boot process of XP system:
1. The power supply self-test program starts running
2. The main boot record is loaded into memory and the program starts executing
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts running the appropriate small file system driver. The small file system driver is built inside NTLDR and can read FAT or NTFS.
7. NTLDR file reading
8. NTLDR loads the selected operating system
*If NT/XP is selected, NTLDR runs
*For other operating systems, NTLDR loads and runs and passes controls to it.
The windows NT process ends.
Search for computer hardware and pass the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE.
10. Then NTLDR is loaded and the system information collection.
Search for a collection of system information and load the device driver configuration so that the device starts working at startup
Leave control to, at this time, the start-up program ends and the loading phase begins
The following are some of my personal experiences and I hope they can help you a little.
NTLDR is missing,Press CTRL+ALT+DEL to restart.
After thinking, analysis concluded:
The system is an NT kernel, and LDR is the abbreviation of the commonly used loader in the operating system. Therefore, the failure may be caused by the loss of the system boot file, and the name of the file is NTLDR.
2. The computer is stuck when entering the operating system, that is, when the system boots, so it is judged that it may not be able to boot the system and lead to the inability to enter the operating system.
The following is an explanation of the fault on the official Microsoft website:
When starting the computer, I received an error message "NTLDR is missing" (NTLDR is missing)
symptom
After copying multiple files to the root folder of the boot volume using the NTFS file system, you may receive the following error message the next time you start the computer:
NTLDR is missing
Press CTRL+ALT+DEL to restart.
If you delete a file copied to the root folder, the main file table (MFT) allocation index does not drop to the original size.
reason
This problem may occur if the MFT root folder is fragmented. If the MFT root folder contains multiple files, the MFT becomes so fragmented that it requires another allocation index to be created. Because the files are mapped alphabetically into the allocation index, the NTLDR file may be pushed into the second allocation index. If this occurs, you will see the error message described in the "Symptoms" section of this article.
Generally, files are not written to the root folder. This can occur if a program periodically creates and deletes temporary files in the root folder, or if many files are copied accidentally to the root folder.
Solution
To resolve this issue, contact Microsoft Product Support Services for the Bcupdate2 utility. For more information on how to contact Microsoft Product Support Services, visit the following Microsoft website:
/selectassist (/selectassist)
Alternative Method
To work around this issue, create a boot disk to boot your computer.
For more information on how to create a boot disk on a Microsoft Windows XP-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
305595 (/kb/305595/) How to create a boot disk for NTFS or FAT partitions using Windows XP
For more information about how to create a boot disk on a Microsoft Windows 2000-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
119467 (/kb/119467/) How to create a boot disk for an NTFS or FAT partition
[quote]
We can use the "compensation method" to repair the conclusions drawn by ourselves and the instructions of Microsoft's official website, that is, copy the lost file from other system disks or computers, fill it up, and then enter the operating system normally.
The following are the solutions summarized by your own experience and online:
(Step 1) Enter through the fault recovery console (assuming that the G drive is the optical drive letter...)
copy G:\i386\ntldr c:\(Enter),
Then enter:
copy G:\i386\ c:\(Enter)
At this time, the system needs to prompt something, enter y, and then press Enter. (The problem should be considered to be solved at this point. The next step is to determine whether the problem has been solved.)
Enter c:\, and if the information displayed normally, restart it, which means that the problem has been solved.
Question summary:
The NTLDR file is a boot file for WinXP. Backup should be given when the system is normal.
Description of NTLDR File: NTLDR is a hidden, read-only system file used to load the operating system.
Extraction of NTLDR file: The NTLDR file is WinXP boot file. When this file is lost, the system will prompt it to be missing and requires pressing any key to restart. It cannot enter the WinXP system correctly. This file can be extracted under the fault recovery console. This file exists in the i386 directory of the installation CD. The extraction method is as follows:
Enter the system recovery console, go to the C drive, enter "copy X\I386\NTLDR" (Note: The X here is the optical drive letter) and press Enter. If the system prompts you to not overwrite it, press "Y", and then enter the exit command to exit the console and restart.
Attached:
The boot process of XP system:
1. The power supply self-test program starts running
2. The main boot record is loaded into memory and the program starts executing
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts running the appropriate small file system driver. The small file system driver is built inside NTLDR and can read FAT or NTFS.
7. NTLDR file reading
8. NTLDR loads the selected operating system
*If NT/XP is selected, NTLDR runs
*For other operating systems, NTLDR loads and runs and passes controls to it.
The windows NT process ends.
Search for computer hardware and pass the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE.
10. Then NTLDR is loaded and the system information collection.
Search for a collection of system information and load the device driver configuration so that the device starts working at startup
Leave control to, at this time, the start-up program ends and the loading phase begins
The following are some of my personal experiences and I hope they can help you a little.