The preset areas in the list

[system]

Hi ;o)

What inclued the preset Areas in the “preset areas in the list in Resident Protection”
Standard Shield - Advanced

List of excluded areas. Areas listed here will not be searched or scanned. We recommend you to keep the preset areas in the list. You can modify the list using the buttons Add and Remove.

I have for exampel
C:\WINDOWS\TEMP*.TMP
C:\WINDOWS\WINSXS*.MANIFEST
C:\WINDOWS\CSC*.TMP
C:\WINDOWS\CSC?0???
*\EDB.CHK

why should they be there, and do they belong to the preset one

Regards
P.

[Vlk]

Performance reasons. No need to scan these files (normally)…

[system]

Have you a list of the preset one.

P.

[Vlk]

I thought you listed them yourself in the first post…

[system]

I think the OP might be alluding to the following:
?:\pagefile.sys
*.txt
*.log
*.ini
which are all I have in my exclusion list as I removed the extras that the OP lists when Avast ‘improved’ the program last year (after first checking with Avast). Note vlk states ‘no need to scan… normally’ (my emphasis) However I am open to updated advice as I rely on Avast set at high (with BoClean, WinPatrol Plus and AdMuncher) to protect my system.

[system]

My list return to the pre-set list every time I restart the Std Provider !!! I normally add *.pdf *.jpg and stuff like that to the exclusion list so get better performances

Also, I don’t have the C:\Temp and C:\Windows\CSC excllusion on my list. I just have TXT, INI and LOG, is it normal ?

Can someone confirm if these are bugs ? ?

[Lisandro]

@sunphoenix post:6

My list return to the pre-set list every time I restart the Std Provider !!!

Are you disabling Standard Shield to change the settings? It’s not necessary…

@sunphoenix post:6

I normally add *.pdf *.jpg and stuff like that to the exclusion list so get better performances

Look, jpg could contain exploits and it’s not safe to exclude them from scanning.

[DavidR]

C:\Temp is not in my exclusion list and I don’t think it should be.

C:\Windows\CSC isn’t in the list as a folder exclusion but for (see below, as per the original poster.

C:\Windows\CSC\?0?????? and 
C:\Windows\CSC\*.TMP

[system]

@Tech post:7

Look, jpg could contain exploits and it’s not safe to exclude them from scanning.

Which file types may contain exploits? :

[system]

@Tech post:7

@sunphoenix post:6

My list return to the pre-set list every time I restart the Std Provider !!!

Are you disabling Standard Shield to change the settings? It’s not necessary…

@sunphoenix post:6

I normally add *.pdf *.jpg and stuff like that to the exclusion list so get better performances

Look, jpg could contain exploits and it’s not safe to exclude them from scanning.

1- I know, I dont stop/terminate the Standard Shield to change setting or add Area Exclusion ... But I Do need to stop it sometimes and I dont need reason/justification to do it…My problem is that the list is reseted every time I do it. It should be persisted.

2- JPG cannot contains exploit as far as I am concerned and if they do it is surely because of the reader you use to read it !!! I have once coded myself a JPG viewer and I have no clue how it could contains exploit.

[system]

OK you`re right. JPG exploit are possible I have to agree to obvious but still it depends on the software you use to read it. The risk of seeing another JPG exploit for Vista IE and explorer are almost null ( I hope so …)

Regards

[Lisandro]

@ght1 post:9

Which file types may contain exploits? :

I’m not the one who can answer this question… I let it for Alwil programmers.

@sunphoenix post:11

OK you`re right. JPG exploit are possible I have to agree to obvious but still it depends on the software you use to read it. The risk of seeing another JPG exploit for Vista IE and explorer are almost null ( I hope so …)

You’ve got the point.