Computer Trouble: Windows could not start because...

[DJC]

AVG ran a scan on my computer that required a re-start. The scan did pick
up a number of viruses, trojan horse I think, and it said all were healed or
sent to the virus vault. The computer will not boot up now and displays the
following message:

"Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll
Please re-install a copy of the above file"

Any advice on how to go about this? Any other suggestions?

Thanks

[NiteProwler]

Post by DJC
AVG ran a scan on my computer that required a re-start. The scan did pick
up a number of viruses, trojan horse I think, and it said all were healed or
sent to the virus vault. The computer will not boot up now and displays the
<Windows root>\system32\hal.dll
Please re-install a copy of the above file"
Any advice on how to go about this? Any other suggestions?
Thanks

Download that particular .dll file and copy it back to the system32
folder. You may find that you will get more issues after fixing this
one; the better option may be to do a 'repair' on windows. Good luck,
hope you are up and running again soon.

[DJC]

I cannot get the machine to start, even in Safe Mode.

Post by NiteProwler

Post by DJC
AVG ran a scan on my computer that required a re-start. The scan did pick
up a number of viruses, trojan horse I think, and it said all were healed or
sent to the virus vault. The computer will not boot up now and displays the
<Windows root>\system32\hal.dll
Please re-install a copy of the above file"
Any advice on how to go about this? Any other suggestions?
Thanks

Download that particular .dll file and copy it back to the system32
folder. You may find that you will get more issues after fixing this
one; the better option may be to do a 'repair' on windows. Good luck,
hope you are up and running again soon.

[Rick]

had the exact problem. took the hard drive out of the system (was a
laptop), put hard drive in external drive bay, plugged in usb cable and
accessed the drive like a storage drive. then copied the hal.dll file over
to windows/system32 and problem solved. or like corey said wipe the drive
and install from scratch.

Post by DJC
I cannot get the machine to start, even in Safe Mode.

Post by NiteProwler

Post by DJC
AVG ran a scan on my computer that required a re-start. The scan did pick
up a number of viruses, trojan horse I think, and it said all were healed or
sent to the virus vault. The computer will not boot up now and displays the
<Windows root>\system32\hal.dll
Please re-install a copy of the above file"
Any advice on how to go about this? Any other suggestions?
Thanks

Download that particular .dll file and copy it back to the system32
folder. You may find that you will get more issues after fixing this
one; the better option may be to do a 'repair' on windows. Good luck,
hope you are up and running again soon.

[Jim]

I used to use AVG until it did an auto update overnight and the next morning
my PC was essentially a paper weight.
managed to get it going and removed AVG. PC worked perfectly after that.
Been using ESET Nod32 since then and no problems

Post by DJC
AVG ran a scan on my computer that required a re-start. The scan did pick
up a number of viruses, trojan horse I think, and it said all were healed
or sent to the virus vault. The computer will not boot up now and
<Windows root>\system32\hal.dll
Please re-install a copy of the above file"
Any advice on how to go about this? Any other suggestions?
Thanks
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4603 (20091113) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4603 (20091113) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

[Corey]

I said it before and I'll say it again. Once your computer is
infected by a virus, you can no longer trust it. My suggestion is to
wipe it out and re-install from scratch, otherwise you are more than
likely to come across this problem again.

Ideally, restoring from a known-good image would be optimal.