Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Kostronor on December 07, 2011, 09:15:48 AM

Title: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Kostronor on December 07, 2011, 09:15:48 AM: Hello guys,

i was using avast since years and i was always satisfied with what it does and was not doing, but since the new update, my exclusions are not working anymore.
I am myself handling with some files containing viruses and sometimes i need to execute them (i know what i do! ;) ) this has always been working with avast past the years.
I created a folder and excluded the whole folder with %path%/folder/*
but since this update, the filesystem-protection (Dateisystem-Schutz in German) keeps finding a virus. Interesting is, that the .exe itself is not threated only the files created by the .exe are found as virus. I have excluded the whole folder and every single file itself in both, the global settings and in the settings of the module, not i don't know what needs to be done to get this to work.

Help is appreciated
Sincerely
Kostronor
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 07, 2011, 12:08:26 PM: Is %path%/folder/* a typo for %path%\folder\* ???
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Kostronor on December 07, 2011, 01:56:58 PM: Quote from: Tech on December 07, 2011, 12:08:26 PM
Is %path%/folder/* a typo for %path%\folder\* ???
It is something like:
C:\Users\Me\Desktop\folder\*
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: ady4um on December 07, 2011, 05:06:45 PM: Which shield is identifying the malware? You may need to add exclusions / exceptions to other shields (and scans) too.

I would try also with several paths simultaneously like

Code: [Select]
C:\Users\Me\Desktop\folder C:\Users\Me\Desktop\folder\ C:\Users\Me\Desktop\folder\* C:\Users\Me\Desktop\folder\*.*
just in case.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 07, 2011, 05:50:12 PM: Enough C:\Users\Me\Desktop\folder\*
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Kostronor on December 07, 2011, 08:14:57 PM: Quote from: Tech on December 07, 2011, 05:50:12 PM
Enough C:\Users\Me\Desktop\folder\*
Thats what was working till the update has broken it.
Quote from: ady4um on December 07, 2011, 05:06:45 PM
Which shield is identifying the malware? You may need to add exclusions / exceptions to other shields (and scans) too.

I would try also with several paths simultaneously like

Code: [Select]
C:\Users\Me\Desktop\folder C:\Users\Me\Desktop\folder\ C:\Users\Me\Desktop\folder\* C:\Users\Me\Desktop\folder\*.*
Like said in op, it is the File System Shield.
I had tried every of these and none was working.
also i tried to exclued the file itself:
C:\Users\Me\Desktop\folder\herp.exe
Like said, the problem is not the path not beeing correct, but files which are created in the folder are found, not the .exe itself.
Example:
we have:
-virus.exe
on execution, virus.exe will create a file called virus.exe.tmp.
with C:\Users\Me\Desktop\folder\*:
virus.exe.tmp is deleted
without C:\Users\Me\Desktop\folder\*:
virus.exe is deleted
virus.exe.tmp is deleted
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: ady4um on December 08, 2011, 02:48:28 AM: Is it possible that you have to change the type of extensions (not just exe, dll, sys, com and alike) or the sensitivity of the FSS?

What settings you have in FSS -> EXPERT settings -> scan when... ?

Try "playing around" with those type of settings.

I'm not saying this is the best workaround, and probably avast should take this example for future improvements.

In this particular case, I don't know if the created virus is actually executed or just being written, which may make some difference too.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: -Genesis- on December 08, 2011, 10:43:16 AM: I think what his saying is true because it happens to me also latest build.

File system shield is detecting one of my .dll file as a threat. This is expected because the .dll file is a cheat for a game.

.dll file will work using injector.

I excluded in File system shield setting the folder and even the .dll file.

I even unchecked the behavior shield main setting.

The .dll file has been copied to the computer but opening it File System shield still detecting it.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Kostronor on December 08, 2011, 11:54:02 AM: Quote from: ady4um on December 08, 2011, 02:48:28 AM
Is it possible that you have to change the type of extensions (not just exe, dll, sys, com and alike) or the sensitivity of the FSS?

What settings you have in FSS -> EXPERT settings -> scan when... ?

Try "playing around" with those type of settings.

I'm not saying this is the best workaround, and probably avast should take this example for future improvements.

In this particular case, I don't know if the created virus is actually executed or just being written, which may make some difference too.

Hmmm... All settings in scan when are checked the way avast needs to operate in my opinion, so changing them would not help, because then i could also disable avast for 10 minutes, and that is not what i want ;)

Your last question is somewhat interesting because that is something i would like to analyse but avast is blocking me ;)
But with excluding, avast should not make any difference between the two!

Quote from: -Genesis- on December 08, 2011, 10:43:16 AM
I think what his saying is true because it happens to me also latest build.

File system shield is detecting one of my .dll file as a threat. This is expected because the .dll file is a cheat for a game.

.dll file will work using injector.

I excluded in File system shield setting the folder and even the .dll file.

I even unchecked the behavior shield main setting.

The .dll file has been copied to the computer but opening it File System shield still detecting it.

Thanks for the clarification, that i'm not the only one having this error.

Is there any statement by anyone from avast?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 08, 2011, 11:57:58 AM: Yes, the exclusions for writing don't seem to work in the last version.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: ady4um on December 08, 2011, 01:07:59 PM: Quote from: igor on December 08, 2011, 11:57:58 AM
Yes, the exclusions for writing don't seem to work in the last version.

This is the type of test I was aiming at. My point was, if the virus is only being written (not executed), then the "scan when writing" is the setting that should get you a different result in scanning, specially if you would use "scan all files". That's the reason I asked for your settings there.

If you can, please test these settings in several combinations so to confirm igor's suspicion.

Please report back your test's results.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Kostronor on December 08, 2011, 08:39:59 PM: Quote from: ady4um on December 08, 2011, 01:07:59 PM
Quote from: igor on December 08, 2011, 11:57:58 AM
Yes, the exclusions for writing don't seem to work in the last version.

This is the type of test I was aiming at. My point was, if the virus is only being written (not executed), then the "scan when writing" is the setting that should get you a different result in scanning, specially if you would use "scan all files". That's the reason I asked for your settings there.

If you can, please test these settings in several combinations so to confirm igor's suspicion.

Please report back your test's results.

seems like igor is right, disabling check for writing leads to no found and disabling check for open leaves no difference.

Ok, i think, in this case we all can clearly state that avast has a bug.
is there a need to report this bug, or is it already known or is it known since this thread?
just asking because i think this should be fixed soon ;)
Thanks for all your help in finding the issue
Kostronor

wowow big edit:
Seems to me that my first guess was wrong, the shield even scans when deactivated. i have deactivated the FSS and it is finding the virus. But i checked every module and none of them is telling me that a virus has been found...
i will now investigate a bit further about it

Well, i cannot find what is finding the virus.
even with FSS disabled it is finding it.
with all modules disabled nothing is found...
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Tetsuo on December 10, 2011, 12:26:35 PM: I'm quite sure that the exclusions for writing don't work in the current version.

I checked some files created by Online Armor (which is thoroughly excluded in Avast!) and I noticed that Avast! scans them anyway.

Win XP Pro SP3
Avast! Free AV 6.0.1367 (Behaviour/Script Shield removed)
Online Armor Free 5.1.1.1395 (Web Shield disabled)
*Avast!/OA mutually excluded

Hope this will be fixed soon. As always, thank you very much.

Regards,
T.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Kostronor on December 17, 2011, 01:58:12 AM: Just to bump it, is there any statement by the avast-team about fixing this bug?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 17, 2011, 02:03:17 PM: It will be fixed in the next program update.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 17, 2011, 03:54:04 PM: Quote from: igor on December 17, 2011, 02:03:17 PM
It will be fixed in the next program update.
avast 6 or avast 7 ???
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: lifeson99 on December 17, 2011, 04:23:10 PM: I switched to Avast from Avira for this very reason.
Avira exclusions would not work !!!

But ever since I installed Avast, the Exclusions have NEVER worked.
Very frustrating because I use VideoFixer to repair corrupt AVI files and it always find a virus in VideoFixer, as has every antivirus program done for years.
But it is a False Positive. I even reported it in the form to Avast as a false Positive and it is till being scanned.

I excluded the entire folder and the file itself - to no avail.

As a programmer, I would think implementing exclusions would be a simple matter. And if they suddenly stop working, then the fix would be simple as well. Not sure why Avast does not quickly post the fix in an update but I don't work there so have no idea.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 17, 2011, 05:59:01 PM: Quote from: lifeson99 on December 17, 2011, 04:23:10 PM
I excluded the entire folder
Did you use an * after it?

Quote from: lifeson99 on December 17, 2011, 04:23:10 PM
Not sure why Avast does not quickly post the fix in an update but I don't work there so have no idea.
They will release the fix in the next program update.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Kostronor on December 17, 2011, 06:10:53 PM: Quote from: igor on December 17, 2011, 02:03:17 PM
It will be fixed in the next program update.
Thanks for the quick answer!
Waiting for the update now
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 17, 2011, 06:15:14 PM: Quote from: Kostronor on December 17, 2011, 06:10:53 PM
Thanks for the quick answer!
Waiting for the update now
Secret... Can Igor answer my question?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 17, 2011, 06:22:33 PM: Quote from: Tech on December 17, 2011, 03:54:04 PM
Quote from: igor on December 17, 2011, 02:03:17 PM
It will be fixed in the next program update.
avast 6 or avast 7 ???

That's not completely clear at the moment... could be 7.

Quote from: lifeson99 on December 17, 2011, 04:23:10 PM
But ever since I installed Avast, the Exclusions have NEVER worked.
Very frustrating because I use VideoFixer to repair corrupt AVI files and it always find a virus in VideoFixer, as has every antivirus program done for years.

I'm not familiar with VideoFixer, so I may be wrong, but I guess you're setting an incorrect exclusion. The thing is that the only thing that doesn't work is the exclusion "on write" - but if the file is already there, exclusions for reading or executing do work. So unless something is constantly modifying your executable (unlikely), or unless the executable is actually some kind of extractor which drops another executable when you run it, the problem doesn't apply here.
So, what exactly and where exactly are you setting? What is the exact detection (full path shown) you get?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 17, 2011, 06:26:43 PM: Quote from: igor on December 17, 2011, 06:22:33 PM
That's not completely clear at the moment... could be 7.
Seems there are other staff members that are more self confident than you ;D
But thanks anyway.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: lifeson99 on December 17, 2011, 10:12:15 PM: Here are my settings - I run a scan nightly and every morning I have an Avast message that a "Threat" has been delected.
Then I click on the details of the threat and it says VideoFixer.exe was detected as having a virus. 7 days a week I get the same message and have to then tell it to "Ignore" it.

Here is a screenshot of my settings. I have tried using ONLY the folder, and ONLY the file, and also tried using BOTH as shown below. Nothing works:

(http://www.infocellar.com/temp/Screenshot-1.jpg)
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 17, 2011, 10:15:26 PM: These are exclusions for the File System Shield (to prevent scanning/detection when you run the application) - not for on-demand scans.
You can either set the exclusion in the settings of the particular scan (the one you have scheduled to run nightly), or in program settings, which would cover all on-demand scans.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: lifeson99 on December 19, 2011, 02:19:42 PM: Sorry - wrong screenshot as you noted.
I also have had the folder Excluded in the master "Settings".
So long as this is fixed I am not in a mad rush and will not switch.
I love the interface and surprisingly even like the voice since it is only very occasional. Very Professional look and feel.

(http://www.InfoCellar.com/temp/Screenshot-2.jpg)
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: chrysalis on December 19, 2011, 08:50:34 PM: Quote from: lifeson99 on December 17, 2011, 04:23:10 PM
I switched to Avast from Avira for this very reason.
Avira exclusions would not work !!!

But ever since I installed Avast, the Exclusions have NEVER worked.
Very frustrating because I use VideoFixer to repair corrupt AVI files and it always find a virus in VideoFixer, as has every antivirus program done for years.
But it is a False Positive. I even reported it in the form to Avast as a false Positive and it is till being scanned.

I excluded the entire folder and the file itself - to no avail.

As a programmer, I would think implementing exclusions would be a simple matter. And if they suddenly stop working, then the fix would be simple as well. Not sure why Avast does not quickly post the fix in an update but I don't work there so have no idea.

They have never worked for me either I think.

I have an app that avast seems to scan very slowly, its only a very small tiny app and takes about 3 seconds to launch. I disabled auto sandbox, no good, excluded the folder, no good. It only starts fast when I disable file shield. Also I thought avast caches positive scan results for performance yet this file still keeps been scanned.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: chrysalis on December 23, 2011, 01:00:06 PM: I think I dived in too quick here, this was a problem on the older version but it seems now my exclusion is working.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Maccara on December 26, 2011, 05:23:09 AM: This needs to be fixed ASAP!

Interferes with my build system, tried exclusions and noticed they do jack. Thread found, so subscribing so I might remember to turn avast back on when fixed.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 26, 2011, 11:52:39 AM: Quote from: Maccara on December 26, 2011, 05:23:09 AM
This needs to be fixed ASAP!
Next program release. Probably avast 7 beta next weeks.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: pk on December 26, 2011, 12:19:11 PM: @Kostronor, lifeson99, Maccara,

please apply ap2011-26-12-001: Patch for aswMonFlt.sys, on-close exclusions (IS) patch from http://public.avast.com/~kurtin/patches page.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Maccara on December 27, 2011, 09:59:24 PM: Thank you pk!

Will test on next scheduled reboot.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lefamonster on December 29, 2011, 11:32:56 PM: This is exactly what I experienced. I have a client who we replaced a computer in his home office. He runs a modest server/ client app with networked drives on the clients. Immediately after the 6.0.1367 update I enjoyed a two hour service call attempting to disable the network shield and/or set up exclusions on the mapped drives.

Can you replace the new marketing "nag screens" that try to sell me every service available for internet secuirty with a functional exclusions screen?

I have recommended this product for over 10-years for its awesome stability and functionality. I am sad to see the sales department driving this once fine establishment. Less push to get people to buy your crap, and more focus on perfrecting the crap you are trying to sell.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lisandro on December 30, 2011, 12:45:42 AM: Lefamonster, which avast version do your client run?

Well, do you really think you'll get a better help calling a 180+ million users app a "crap"? ;)
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lefamonster on December 30, 2011, 01:52:50 AM: It occured across the board. This one client was the tip of the iceburg. From free users to Pro, after 6.0.1367 update. The main point of my post is the disgust at the latest versions "add-on" features that it periodically pops up like a piece of malware.

Credit Monitoring, pay this price for 2 years more protection...so on and so forth.
Yes 180 million people at one point in time agree that this AV software does a great job, so lets not try and "up-sell" them into more services. Stay focused on providing the same great product that 180 million plus people have come to enjoy, not adding a larger revenue stream for the bottom line.

My two cents, stay true to what made you great.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: avast@@dvantage77.com on December 30, 2011, 02:54:36 AM: "please apply ap2011-26-12-001: Patch for aswMonFlt.sys, on-close exclusions (IS) patch from http://public.avast.com/~kurtin/patches page. PK"

The exclusion issue is a significant issue! Many businesses have applications that need to be excluded, and all large businesses. From my understanding, the exclusion issue also exists with avast Standard Suite and ADNM. After a FP this month, we learned that exclusions would NOT work in ADNM. We had to disable avast! to keep the systems running.

PK, will this patch fix this issue with avast! 4 and ADNM?

Until ADNM2 is stable and functional, we cannot stop version 4 updates. We also have to give these clients the necessary time to convert their systems. One of my avast! resellers literally has about 100 sites, with thousands of systems, that will have to be converted to ADNM2. I know that the end of avast! 4 support is 1 year away, but will there be enough time?

PK, or ?, when will we see ADNM2?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 30, 2011, 11:49:46 AM: I'd say your understanding is wrong.
I don't think this particular problem is present in the latest release of BP - and regarding ADNM... no, this issue really hasn't magically appeared in a program build a couple of years ago.
(So no, the patch has certainly nothing to do with ADNM.)
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 30, 2011, 12:07:57 PM: Quote from: Lefamonster on December 29, 2011, 11:32:56 PM
This is exactly what I experienced. I have a client who we replaced a computer in his home office. He runs a modest server/ client app with networked drives on the clients. Immediately after the 6.0.1367 update I enjoyed a two hour service call attempting to disable the network shield and/or set up exclusions on the mapped drives.

And this server/client app repeatedly modifies (or creates new) executables on the shares?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Lefamonster on December 30, 2011, 04:23:17 PM: I believe it does modify the exe, or libraries (dll), and/or config files stored locally (c:\mitchell\apppath) and remotely (M:\mitchell\apppath).

The series of troubleshooting started with the old computer when launching the icon on the workstation computer tanked the CPU, yet mouse movement was possible. Completely unresponsive to task manager calls, or any action. The machine was essentially locked up.

We brought in a freshly loaded, brand new computer with of course 6.0.1367. Once mapped and set up in the exclusion lists, the exact same lockup occured. System event logs showed no signs of an obvious culprit. It was like the lock up halted all system processes.

We then disabled all the shields, and set exclusions in each shield for wildcards, direct paths, and so on. Same exact thing on both machines. Lockups. Now the other calls started coming in. More users experienceing lockups. We service alot of these sites, they are at home insurance adjusters.

Best solution was to cripple Avast and make it look like it was running on the surface, diasble Security Alerts, and pray. We are currently testing and pursuing other AV as a result of this, and the marketing bombardment that exists now in the free versions.

So in a nutshell, yes a very dynamic application in a home business environment, that use to work flawlessly, with proper exclusions, is now locking up in particular on 64-bit machines when launching the mapped .exe file, that calls both local and remote applications and libraries.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 30, 2011, 04:39:48 PM: Well, I would rephrase this "very dynamic application" to "a very badly written application", because such a behavior is strange, suspicious and rare (and hard to distinguish from a file infector behavior).
But yes, if executable files are frequently modified, or at least copied/moved around a lot, the subsequent scanning may cause quite some CPU load.
The patch PK posted should help in that case.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: lifeson99 on December 30, 2011, 06:11:02 PM: I went to the Patch website that PK posted at:
http://public.avast.com/~kurtin/patches/#ap20112612001 (http://public.avast.com/~kurtin/patches/#ap20112612001)

I copied the two patch files into BOTH
\Windows\System32\drivers AND \Program Files\AVAST Software\Avast\setup\inf

I then immediately re-ran a Scan. SAME Problem - Exclusions did not work and it found a False Positive with VideoFixer.exe - which is Excluded.

So that's unfortunate. I must add this, however . . on that Patch Download page, right underneath the instructions it says:

NOTE: the patch is intended for build 6.0.1367 and it will invalidate itself with the new program update

Why release a Patch that - even if it did work (which it doesn't) will then be "invalidated" ??
This is really getting frustrating because Exclusions are such a critical part of any Antivirus scanner. Exclusions should be a part of the software - not a Patch.
It seems odd that Users must comb through Forums, go to a special link and download a Patch . . . only to have it be invalidated later.

I agree with others that this MUST BE FIXED. Not Patched temporarily. FIXED.
Otherwise the software is not at all ready for Prime Time, and it has been out for years already.

Igor, is this something you can get Management to tackle ? I do appreciate you responding to these angry Posts and realize that you are just the Guy that is trying to help us.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on December 30, 2011, 07:25:29 PM: "Re-ran a scan"? I'd say there's a bit of a confusion here...
There is a problem with the exclusions - but the problem manifests only in the FileSystem Shield (and maybe P2P and IM Shield, I'm not completely sure about those), only when a file is written or created (i.e. not when executed or read), and only when it's an executable file (i.e. not a document, for example) - which makes the affected situations rather limited. There's no problem with exclusions in manual scans or in FileSystem Shield scan on execution, they work just fine.

So, my guess is that your definition of the exclusion is not correct... what/where exactly did you set?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: ady4um on December 30, 2011, 08:23:27 PM: I would like to add to igor's post, that we are seeing posts mixing different editions / versions / softwares of avast.

The patch is for a certain version of certain editions of avast, and not related to "all and every avast software", but only to a limited set.

The reason the patch invalidates itself for future versions of the relevant editions of avast is that the patch will be included in future versions, so there is no positive consequence if a user would apply the patch over a future version.

I am just clarifying all this (or trying to) because other readers may get the wrong impression from lifeson99's post.
Title: Re: Exclusion does not work - SOLVED ! !
Post by: lifeson99 on January 02, 2012, 03:48:39 PM: Thanks for the Help guys . . . it is working now.
As you can see below . . . I am using the most recent version which IS the version that the Patch was made for and I copied in the two Patch files in as directed

I applied the patch but the file was still flagged as a Threat Detected . . . both when I got up in the morning (Scheduled Scan) and when I re-ran the scan (I performed a manual scan of the entire Graphics folder). Again the file was detected as a threat and moved to the Virus Chest.

What doesn't work - Basic Settings Exclusions:
See below . . .in the Basic Setting screen, it says that the Exclusions will apply to BOTH Manual and Scheduled scans. But the exclusions in this setting did not work for the scheduled scan and did not work for the manual scan - even with patch applied.

(http://www.infocellar.com/temp/Screenshot-6b.jpg)

What does work - File Shield settings Exclusions:
The File Shield Exclusions work . . . so long as you have applied the Patch. Since the Basic setting Exclusions are not working, I think the Patch fixes the File Shield Exclusions settings but does not fix the Basic Settings Exclusions - which is fine so long as the User realizes this and makes sure to fill in the Exclusions in both areas (Basic Settings and File Shield settings).

(http://www.infocellar.com/temp/Screenshot-7.jpg)

NOTE: this ONLY applies to v6.0.1367 with the Exclusions patch applied.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on January 02, 2012, 03:57:07 PM: I can't say I understand your sequence of images :)
The first image shows the exclusion settings for on-demand scans - and the second popup comes from the FileSystem Shield, for which this exclusion doesn't apply, i.e. I don't see any problem.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: DavidR on January 02, 2012, 04:18:17 PM: @ lifeson99
The first batch of images correctly explain what is meant to happen. If you set an exclusion on the on-demand and then run a file from the excluded folder, the file system shield, a resident, on-access scanner isn't bound by that on-demand scan, so it will alert on any file it considers infected.

As for your comment "in the Basic Setting screen, it says that the Exclusions will apply to BOTH Manual and Scheduled scans." Well it doesn't say that it applies to on-demand (manual and scheduled, e.g. initiated by the user) scans and on-access (initiated automatically when the file is accessed/run) scans and it is the on-access scan which is alerting.

Conclusion the Basic Exclusion settings work as expected only for on-demand scans (initiated by the user) not on-access scans (initiated automatically when the file is accessed/run).

It is the on-access scanner exclusions that don't work currently (without the patch).
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: lifeson99 on January 03, 2012, 03:01:07 PM: I posted the settings and the Threat was detected even though I had an Exclusion in the Basic Settings. It was detected during: on-access, Scheduled, and Manual scans

I don't know what more to tell you - the Basic Setting exclusion was not preventing detection for any type of scan or on-access. I did mistakenly use the on-access screenshot for the detection - however, the overnight scan and several manual scans ALL resulted in the file being detected as a threat even though the Basic Settings Exclusion was in place.

Since then - after applying the patch and adding an Exclusion to the File Shield settings - all is well and no threat detection occurs.

NOTE - late last night I found that once I added the File Shield exclusion setting and the exclusion began working . . . I was able to remove the File Shield Exclusion and the Basic Settings exclusion then magically began working alone for manual scans. I have not yet tested schedule scans but I assume it will also work for that too. Very odd but I am glad it started working.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: lifeson99 on January 13, 2012, 03:29:28 PM: Stopped working again. Was fine for about a week, then this morning I received the Threat notice again from the overnight scan. I rechecked my exclusions and they are still there.

This must be the part about the Patch where it says it will not work after an update is applied. I have Updates ON of course so maybe that is what happened.

Any idea when the new Release will occur that will fix this forever ?
Thanks
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: DavidR on January 13, 2012, 03:38:39 PM: The updates it relates to are Program updates, not VPS updates and once again the patch only covers the file system exclusions as that is where the problem lies.

The standard avastUI, Settings, Exclusions for on-demand scan has been working just fine. Ans has been said the file system shield exclusions don't apply to on-demand scans such as your scheduled nightly scan.

So I really don't know what is going on with your system as we have no information on the alert, exclusion composition (path of exclusion and in which exclusion list on-demand or on-access) ?
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: avast@@dvantage77.com on January 13, 2012, 05:12:57 PM: Sir, have you submitted this file as False Positive? Normally it is fixed by the next day.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Notorious on April 17, 2013, 01:31:46 PM: Hi, I too have the same problem, Global Exclusions use to work until the latest version which is Version 8 were used.

I think I may know the reason for the bug.

For example:

I've added 'C:\justatest\file.exe' in the global exclusion area using 'C:\justatest\*', this works before the update, now it doesn't, it will still detect it as virus when i try to copy it somewhere else.

I went in to the Virus Chest and found that file.exe in the list, then I notice the Original Location was odd, instead of showing 'C:\justatest\file.exe' it shows '\\?\Volume{djkf8sj7-55tg-fsd3-45ps-sjd89hfh9}\justatest\file.exe' instead.

So I went on to try adding '\\?\Volume{djkf8sj7-55tg-fsd3-45ps-sjd89hfh9}\justatest\*' in the global exclusions and viola, it works now.

Hope this info helps.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: igor on April 17, 2013, 04:22:55 PM: The "Volume" path is a valid path Windows can use instead of the usual drive letters (well, not the one you posted, it's not valid, but I suppose you changed the numbers and letters?) - and it works even on drives that don't have any letter assigned. But why access files using this path (of there is a letter)...
What operating system do you use? What tool did you use to copy the file?
Thanks.
Title: Re: Exclusion does not work after the new Avast-update 6.0.1367
Post by: Notorious on April 24, 2013, 05:16:09 AM: yes is not valid ;D just for example here

I know the volume path is the same as the letter, that's why I was wondering why would avast use the Volume path instead when detected a potential virus, even if it's the same as the letter path, the Global Exclusion should work, but it didn't.

I have to use the "Volume" path on my Global Exclusion because that's how avast recognize it, it won't work if I use letter path (eg. C:\, D:\)

I just do the normal drag and drop and copy and paste to move my files around, i'm using Windows 7 x64