OK... let's try some heavier weapons
I have prepared a special version of one avast! module that logs some "debugging" information into a file. So, if it's not a problem, please do the following:
1. Make sure you are using the latest build of avast! (4.6.731). If not, invoke a program update first and make sure that the problem is still present.
2. Download
this file3. Go to avast! installation folder and rename the file
aswEngin.dll to something else, e.g. aswEngin_.dll. It should be possible to do even when avast! is running. You can use the command
ren aswEngin.dll aswEngin_.dll4. Copy the file you downloaded in point 2 to avast! installation folder (i.e. you have just replaced the aswEngin.dll file with a new version)
5. Now, invoke again the commandÂ
ashQuick.exe "*STRT-MEM-SHORT"6. Wait for the window to disappear.
During the scanning, the file
C:\avast.log is created. When the scan is done, attach the file here, please - I'll take a look at it (you may have to rename it to .txt, I'm not sure if the board permits .log extension for attachments).
Then, you may rename the aswEngin.dll file back (i.e. delete the aswEngin.dll file and do
ren aswEngin.dll aswEngin_.dll) - or simply invoke a VPS or program update and avast! setup will revert the file back itself (but it will ask for reboot).
Thanks!