Hello, yesterday I followed the prompt to update to v4.8.1282 which appeared to go through satisfactorily. I then checked for definition updates, selected a standard scan and continued web browsing. Normally this doesn’t give any problems, but since the update it ran for a few minutes and then everything froze. Eventually after repeatedly pressing the “Esc” key I was able to get Avast to quit (I couldn’t get Task Manager to open) and things returned to normal.
So this evening I ran it again and just observed the progress with Task Manager running as well. Once again after an indicated 3% scan progress everything froze, and for 2 minutes the HDD was going crazy. This time I left it to see what happened and it seemed to recover and successfully completed the scan. On completion the log showed some files it was unable to scan - The usual SUPERAntispyware quarantine, and 3 others:
C:\DRIVERS\MCDBF\SOURCE1\OTHER.EXE\BIOSLOCK.PIF
C:\DRIVERS\MCDBF\SOURCE1\OTHER.EXE\BIOSLOCK.EXE
C:\DRIVERS\MCDBF\SOURCE1\TSADDON.EXE\UINSHHS.ARJ\UPDTAT.BAT
I’ve never seen these before. There is also the possibility the the M/S update this week could be the culprit, but I’m hoping somebody can offer advice.
But, let’s get more information.
Please download HijackThis from the link below. Do not download HJT to the desktop but instead download it into it’s own folder on the hard drive.
Run the program but do not make any fixes and then post the log results using the “copy & paste” method. It will probably take more than one post to be able to get the complete log posted.
OR, you can post it as an attachment to your post by clicking on “Additional Options…” below left of the posting box. Someone will review your log and then offer help.
Logfile of Trend Micro HijackThis v2.0.2
Scan saved at 13:18:49, on 15/11/2008
Platform: Windows XP SP2 (WinNT 5.01.2600)
MSIE: Internet Explorer v7.00 (7.00.6000.16735)
Boot mode: Normal
Nothing obvious in the log, and the files mentioned are not necessarily malicious. (up load to VirusTotal if you want confirmation.) I suspect your problem with the scan stalling is one only one of the avast! team can answer, and there’s no guarantee they’ll notice the thread, but keeping to one thread means it’s clearer what’s going on.