Originally Posted by teacherdon
Any reason why this approach-- copying a good hal.dll file from one drive to another-- wouldn't work?
There are 7 different versions of the hal.dll
file. There are two other files that have to match the version of the hal.dll
file that is in use, or the system might not boot.
So you have to use the correct one and rename it.
Also, it's more often a corrupt boot.ini
file rather than an actual problem with the hal.dll
Not sure why you can't see the System32
folder, unless it's also had the System
attribute set and you don't have the system set to show system folders, so double check the View settings:
To change View Settings to show hidden and system files
In Windows Explorer, click on Tools | Folder Options
- Display the contents of system folders (not present in Win2K/Vista)
- Show hidden files and folders
- Hide extensions for known file types (WinXP/Vista)
- Hide file extensions for known file types (Win2K)
- Hide protected operating system files (Recommended)
See this post for steps to fix this using the Recovery Console. A live CD or connecting the drive to a different PC also works, just need to use the correct drive letter (If you can get the System32 folder visible). Haven't heard of malware deleting the entire folder, as so many of those files are in use you'd think something would be left.
How to fix the missing or corrupt <windows root>\system32\hal.dll error.