This situation is relatively simple to solve, and more common, so it is also one of the first methods we take when encountering this fault, that is, in the Recovery Console or other systems, the system's installation CD-ROM in the i386 directory of the NTLDR file copied to the system partition (usually the C disk) can be.
Two, NTLDR is not damaged or lost
If the NTLDR file on the CD-ROM is copied to the C drive and rebooted, the problem is still not solved, and then we can realize that it is not the NTLDR that is damaged or lost, but the system is blind to it. Why is this so? Generally speaking, the causes of this phenomenon are the following:
1, the use of non-system disks to start the computer. This problem may occur if some non-system disks are used to boot the computer, such as floppy disks, CD-ROMs, USB removable storage devices, and so on. The solution is to remove these devices and then just restart the computer.
2. The information in the hard disk in the BIOS has been changed and the detection method has been set to manual.
Because the hard disk information has been tampered with, the system can't find the system partition in the hard disk, so it can't find the startup file NTLDR in the system partition. Just set the hard drive detection mode to "Auto" in the BIOS "Standard CMOS Setup".
3. The system partition is not activated. If the system partition used for storing boot files (including BOOT.INI, NTLDR, and NTDETECT.COM) is not activated, but other main partitions are activated, then the NTLDR file cannot be found when the system boots. To solve this problem, boot your computer with Windows 98 startup disk, then run Fdisk and select "Set active partition" to activate the system partition. If you still can't solve the problem, you need to run the FIXBOOT command under the Recovery Console to make the active partition a bootable partition.
4. The master boot record (MBR) on the hard disk is corrupted, resulting in the system not being able to find the system partition. The solution is to run the fixmbr command under Recovery Console, or boot the computer with a Windows 98 startup disk and run FDISK /MBR.
5. The MFT root folder of the system partition is fragmented. The Master File Table (MFT) is an index of every file on a volume, and if the MFT root folder contains more than one file, the MFT becomes so fragmented that it requires the creation of a separate allocation index. Because files are mapped alphabetically into allocation indexes, NTLDR files may be pushed into a second allocation index. It is generally not recommended that users write files directly to the root folder, especially large numbers of files. This can be caused if there is some program that regularly creates and deletes temporary files in the root folder of the system partition, or copies many files to the root folder by mistake. However, if we delete those temporary files or files copied to the root folder at this point, the Master File Table (MFT) allocation index does not drop to its original size, so the failure still exists.
This is when we need to reboot the computer using a Microsoft tool called bcupdate2 (download:
Windows 95, Windows 98, or Windows Me startup disk.
step2: Run the following command to back up the msdos.sys file in the root directory of the system partition:
attrib -h -r -s c:\msdos.sys
rename msdos.sys *.ysy
step3: At the command prompt, type sys c:. . This command rewrites the Windows 95, Windows 98, or Windows Me boot code with the correct BPB information.
step4: Run the fixboot command under Recovery Console to rewrite the Windows 2000 or Windows XP boot code.
After following the above, you can usually make the original installation program continue.
Summary: The above list of fault phenomena and their causes are in accordance with the easy to difficult, from common to rare to arrange. We encountered this failure, you can follow the order of this article, troubleshooting