Exclusion does not work after the new Avast-update 6.0.1367

[lifeson99]

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.

[lifeson99]

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

[DavidR]

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) ?

[avast@@dvantage77.com]

Sir, have you submitted this file as False Positive?  Normally it is fixed by the next day.

[Notorious]

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.

[igor]

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.

[Notorious]

yes is not valid  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