_avast4_ folder

I ran a scan with another AV which reported a trojan in a “avast\unp*.tmp”. I now discover that this is to do with your s/w, which I have never installed. I am puzzled and a little concerned. Is anything known to imitate you? Can anyone shed any light?

Regards,
Duncan

Hi Duncan, welcome to the forum :slight_smile:

I just typed out a reply suggesting the possibility of avast! being installed, and saw the 4 was missing…

First off, let me say that I am not completely sure, this is merely a suggestion.

Now this is interesting…

avast! scans data in the avast4\unp*.tmp folder ← notice the 4?

This is very odd to me, can you be certain that it didn’t have the 4?

I would suggest i you haven’t already got it, to try a scan with MalwareBytes AntiMalware, like one or our resident experts suggests:
http://forum.avast.com/index.php?topic=53253.0

-Scott-

EDIT:

And now I just noticed in the title there is a 4…

Are there any avast! processes running?

http://dl.dropbox.com/u/3105891/Pics/avast!%20pics/Task%20Manager.gif

Can you find the ALWIL Software folder?
C:\Program Files\Alwil Software\

Dear Scott,

Thanks for getting back so promptly. My typo - it should read avast4 throughout, as you suspected.

I’ve checked the process list and folder and I have neither. My AV (trial only) is G Data IS2010 and I think this software is creating the avast4 folder. Do you share an engine?

I will follow up the link you supplied.

Thanks,
Duncan

Hi Duncan

Gdata, that may explain it…

What I do know is that GDATA uses avast! as one of two engines. This may explain how this folder is created.

I know that avast! is coded to ignore it’s own folders so I don’t know why I would be alerting on it…

http://www.gdatasoftware.com/information/partners/technologies.html

-Scott-

Aha! Yes, that would explain it. Wonder why they don’t ignore their own folders too? I ran the s/w you linked me to and apparently I’m fit and healthy. Well, thanks for your help and I think I ought to give your AV a go in recognition of prompt services rendered.

Cheers,
Duncan

This is the problem, you scan with another AV (scanner b) and avast (scanner a) is still active. Scanner B want to scan a file so it opens it, scanner A being the resident scanner will first intercept that call and scan that file, it does that in the avast4 folder in the form of the unp*.tmp file. This can cause scanner B to scan that file and now you have a bit of a conflict between scanners.

After avast scan an item in the avast4 folder it clears it, but if scanner B has locked that file, avast can’t clear it.

So when doing a scan with third party security software you either have to ignore the contents of the avast4 folder or pause the Standard Shield so it doesn’t intercept scanner Bs calls to scan files. This avoids possible conflict and will also reduce the scan duration as duplication is cut out.

Clearer and clearer. Now the seemingly eternal scan time makes sense too. Thanks again. Duncan

No problem, glad I could help.

Welcome to the forums.

So am I! Thanks, David. Duncan