Resolve Windows can not start prompt hal.dll damaged or lost method

Windows can not start prompt hal.dll corruption or loss reasons:

1, GHOST system caused, GHOST original package system files Caused by the brand host partition type (most of the brand computers have hidden partitions);

2, after the accidental system shutdown, boot can not be started, use the system repair disk repair prompt system32\\\\hal. The dll file is damaged or lost;

3, overclocking may also cause system file corruption, indicating system32\\\\hal.dll is damaged or lost;

4, is the memory failure, the memory module Pull down and wipe off the dirt on the gold finger, check if it is tight and try again, or find a memory module to ensure that the normal memory is installed before testing, to eliminate the problem of the memory stick!

Download: hal.dll download

The following is a common solution for hal.dll corruption or loss

1, can not start prompt hal.dll Damaged or lost, in fact, the file may not necessarily say that it does not exist in the system, and according to the system prompts, copying a hal.dll file into system32 is simply not feasible.

2, the reason for this error is the boot.ini file error, can not guide the computer to start from the specified path, then the system will search for other paths, and other paths do not exist or simply There is no hal.dll file, so this error will be prompted.

3, for example, the system is installed to the C drive, if the boot.ini file format in the root directory of the C drive is not complete, the system defaults from C:\\Windows, but because of boot. The ini file format is incomplete and illegal. The system will determine that your Windows XP is not installed on the C drive, so the system prompts that the HAL.DLL file cannot be found. Causes the startup to fail. The solution is to re-edit the Boot.ini file.

4, use DOS boot disk to start, enter the DOS interface, use the DOS tool EDIT.EXE command to edit this file. After starting EDIT.EXE, open Boot.ini, edit the contents of the Boot.ini file in the correct format, and save it as the Boot.ini file.

5. Use the bootcfg command in the Recovery Console. Use the WINDOWS Recovery Console to fix boot.ini with the fixboot command. If it fails, use bootcfg /add to rebuild boot.ini.

6, if you do not catch a DOS command interface, you can also create a correct boot.ini on another computer, then copy to the root directory of the faulty computer C drive to overwrite the source file. can.

7. How is COPY? Still use DOS. You can't remove the hard drive of the faulty computer. COPY when hanging on another computer. The best way is to edit the boot.ini from another computer, use a u disk boot.ini copy, and then copy one. Hal.dll file.

8, then plugged into the faulty computer, use the boot disk and load the U disk drive support, enter the DOS interface. Go to the U disk directory and see the hal.dll and boot.ini files, then use the DOS command

copy hal.dll c:\\windows\\system32\\hal.dll

copy boot. Ini c:\\

After the above steps, it can basically solve the startup failure, suggesting that hal.dll is damaged or lost! Thank you for reading, I hope to help you, please continue to pay attention to this, we will try to share more excellent articles.