Windows cannot be started due to file corruption or loss

When a Windows 2000 or XP system fails, we can usually fix it through "Last correct configuration", "security mode", and "System Restore" (for XP only. However, some situations cannot be solved through these methods, such as loss of system boot files, loss of boot. ini files, configuration errors, and loss of system DLL files. It takes a long time to reinstall the operating system. In fact, we can restore the console to make the final attempt. Using the Recovery Console, we can not only enable and disable system services, partition and format disks, but also repair boot records, you can also copy the files on the source disc to fix System File loss errors.

Although the restoration console is very practical, it also has some restrictions:

To use the Recovery Console, you must know the account of the system administrator and zookeeper?

The system console can only access the following folders: boot folder, system directory, and removable storage devices. If you access other folders, the system prompts "Access Denied" (Access denied );

On the Recovery Console, you can copy files from the light, floppy disk, or hard disk to the hard disk. However, the disk cannot be copied to a floppy disk.

Ii. Start Recovery Console

To log on to the recovery console, use the OS CD to start the instance. On the "Welcome to installer" page, we can see that the second prompt is "to use/'recovery console/'To fix Windows XP installation, please press R ".

After you press the r key, the installer checks the disk. Wait a moment, the screen will list the found operating system and its installation directory, and will be automatically numbered. The system will ask which Windows system you want to log on to. We only need to enter the serial number before the system and press enter (do not press enter directly! The system restarts !), Then, we will ask the Administrator's password and press enter to enter the repair console.

Iii. Common system fault recovery commands

1. bootcfg: used to configure and restore the boot. ini file. (This command is unavailable for Windows 2 K)
2. Disable and enable: used to disable/enable system services or device drivers
3. Expand: used to extract files from compressed files
4. fixboot: re-write the new Partition Boot area to the specified system partition.
5. fixmbr: fixed the boot disk's Master Boot Record.
6. Help: Display help
7. listsvc: list all system services and device drivers on the system (used with disable/enable)
8. Set: Display and set Environment Variables

4. Fixed common system startup faults

(1) Damage to the system boot Area

It is usually caused by virus damage, or some third-party disk tools, causing damage to the content of the boot sector. This occurs when the OS is started or the system prompts that no disk can be started. In fact, the Recovery Console can easily recover such errors. Log on to the recovery console, enter fixboot, and the system will prompt whether you want to write the new boot sector to the target disk partition. Press Y and then press Enter. After the system writes the data successfully, press exit to restart.

If the problem persists, it may be that the Master Boot Record (MBr, Main Boot Record) is damaged. At this time, we will use the fixmbr command, but this command is highly risky, partition information may be damaged, causing data loss. Therefore, do not use it in the end!

Like fixboot, enter the Recovery Console and enter fixmbr. The system will have a warning (if you are sure you want to execute the command, Press Y and press Enter, then resume the console prompt and press exit to restart.

(2) damaged or lost system boot files
When the system starts, the system prompts that ntldr or ntdetect. com cannot be found, and the system requires a restart. In this case, multiple systems are installed in the same partition, or some misoperations are performed to delete the files under the root directory of the system.

In fact, these two files can be found in the i386 directory of the installation disc and copied directly to the root directory of the system disk. First, go to the recovery console and enter (assume that the drive letter is d ):

"Copy D: // i386 // ntldr C: //" or "Copy D: // i386 // ntdetect. com C ://"

(If the file exists, overwrite it) and then press exit to restart.

(3) the boot. ini file is damaged or lost.

This often happens when the system is installed in an incorrect sequence or due to some misoperations. Saves the boot with multiple boot menus. after INI is lost or damaged, the Startup Menu disappears. (If you only have one system, it will be started in the default directory, but there will still be an error message ,.

In fact, this error is very simple. We can use the restore console bootcfg command to recreate the boot. ini file. First, go to the recovery console and enter bootcfg/rebuild at the prompt. Then, the system automatically scans all disks to find the operating system that can be added to the boot menu. After scanning, the system lists the operating systems that can be found, and you can select which one to load to boot. INI (Y indicates "yes", N indicates "no", and a indicates "all "). Then, enter the name of the startup Item when "Enter the loading identifier" is prompted, and enter the startup parameter (usually fastdetect or others) when "Enter the OS loading option" is prompted, such as nodetect), then press enter to return to the recovery console prompt, press exit to restart, and then the Start menu appears again.

(4) System File loss

Sometimes this problem occurs. When the system is started, it prompts that a file under Windows // system32 is lost and the system cannot be started. You need to reinstall the system. There are many reasons for this problem. It is usually because some important system files are deleted or replaced when software is installed and uninstalled, which causes the system to fail to be started. The following is an example.

In this case, we can use the restore console's expand or Copy command to fix the issue. Log on to the recovery console and go to the i386 folder under the CD. First, check whether the lost files have been compressed. If the data has not been compressed, copy the data directly to the target location, for example, NTDLL. DLL; if it is compressed, you need to use the expand command, such as ntdsbcli. DL _ (as long as the last suffix is underlined, it is compressed ).

The format of copy is: Copy (Space) to the target folder of the source file (Space)
For example: Copy D: // i386 // NTDLL. dll C: // windows // system32

Expand format: expand (Space) to the target folder of the source file (Space)
Example: Expand D: // i386 // ntdsbcli. DL _ c: // windows // system32