Major Scan Problem with ver 418

Avast Free Antivirus / Premium Security
1

When I tried to manually scan my system with the new version I ran into the same two problems that were listed as problem with ver 412.
1 - Many files not being scanned. (in comparison to previous version)

2 - Biggest problem is that as it scans it writes temp files until my system locks up.

Any ideas? I never had this problem before. Is there going to be a fix or what is the official suggestion?

Any help will be appreciated.

2

Did you try to “repair” your avast! installation from the Control Panel? Maybe the update didn’t go as expected…

3

Also please check the file version of \aswEngin.dll

In Explorer, right click the file, choose Properties and see the Version tab.

I’m expecting a number like 4.1.415.

Thanks
Vlk

4

Yes, the aswengin.dll is 4.1.415. Is that the problem? Should it be 418? If so how does one fix that? I tried the manual program upgrade but that didn’t do anything.

Any and all help is appreciated.

5

No, the version is OK.
Did you try the “repair” option?

6

Where is the repair option? I tried the manual update but that had no effect. Is there a repair that I’m missing?

7

Also try searching your hard drive for other occurences of aswEngin.dll. Make sure there is only one file of that name on your disk (the one in the avast folder with the 4.1.415 version info).

Thanks
Vlk

8

I searched my C drive and there is only the one entry.

I found the repair option and tried it.

I then tried the manual scan. This time my computer didn’t freeze, but it is still creating hundreds of temp files. (maybe more) I am attaching a jpeg from my GoBack Log that shows the activity during the scan. Is this normal?

There are 25 files that can’t be scanned. I used to have only around 6 or so.

Any ideas?

Thank you

9

Well the creation of the files is perfectly normal but they should be deleted automatically when the scan finishes. Aren’t they?

As for the untestable files – does any of them have the [Aspack] suffix added to the filename? What are the reasons of their non-scannability? (see the Results column)

Thanks
Vlk