Why does the on-access scanner alert to avast TEMP files?

I’m just a little curious,

Why does scanning infected files from the chest invoke, what I think is the standard shield, to alert at the temp file that the scanning creates
This can cause problems as it is most likely would be deleted by the user, leading to the scan within the chest to produce errors.

The same alert happens when you click ‘email to alwil…’

To avoid the errors you have to choose ‘No Action’

I know it is deleted after but I don’t get why this isn’t accounted for by the shield
Is it possible program it to avoid this conflict, if that’s the right word?

Thanks,

-Scott-

EDIT:I know the scanner is doing it’s job, but shouldn’t it know that avast created it in the first place, and what is happening?

The file must be temporary unencrypted, extracted from Chest and scanned.
I’m not sure about when you’re seeing the virus alert and by what reason it’s being detected “externally” by other providers.
While scanning a file within Chest (right clicking it) I just receive the report (not the virus alert).

I can understand that this has to be done, and what is going on but,

I'm not sure about when you're seeing the virus alert and by what reason it's being detected "externally" by other providers. While scanning a file within Chest (right clicking it) I just receive the report (not the virus alert).

When I scan a file that is infected from within the chest, right clicking or otherwise, the scanner begins and instanly there is an alert regarding the subsequent temp file created.
It seems to be the standard shield alert, with the 4 options (move to chest, delete…), and the alert above the taskbar

It is like they are running independant of each other, can’t the scanners ‘see’ what the other parts of it are doing?

If it doesn’t happen to you, do you think that there is something wrong with the installation?

[OT]
I see your profile has changed.
Is ‘Avast Technical’ the next one up from uberevangelist? :slight_smile:

-Scott-

So you’ve changed avast Exclusion list and remove the avast temporary folder from there.

Is that what happened? That certainly explains it

I don’t remember doing that, and wouldn’t do it intentionally

So I would need to add it back into the standard shield list,
what would be the path?

I am not at the computer at the moment and I have school tomorrow so I won’t be able to check for a while but I’ll do it and report back

Thanks Tech

-Scott-

c:*_avast4_* should do it, add that to the standard shield.

Though that isn’t in my default standard shield exclusions, so it must be hard coded elsewhere as I reqularly scan files in the User Files section (samples) and don’t get pinged.

What David posted should solve…
You can narrow a bit if you add:
C:\WINDOWS\TEMP*.TMP
C:\WINDOWS\TEMP_AVAST4_\UNP*

I certainly wouldn’t choose this option “C:\WINDOWS\TEMP*.TMP” as far from narrowing the exclusion wouldn’t even exclude the avast4 folder. This would only exclude .tmp files in the C:\WINDOWS\TEMP\ folder and not extend to sub-folders, e.g. the avast4 folder, so detections would continue.

Hi guys,

Added to standard shield exclusion list and it is back to normal, no more alerts

Thanks to you both for your help,

-Scott-

You’re welcome.