Author Topic: Exclusion does not work after the new Avast-update 6.0.1367  (Read 12202 times)

Offline Maccara

  • Newbie
  • *
  • Posts: 5
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #30 on: December 27, 2011, 07:59:24 PM »
Thank you pk!

Will test on next scheduled reboot.

Offline Lefamonster

  • Newbie
  • *
  • Posts: 3
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #31 on: December 29, 2011, 09: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.

Online Tech

  • avast! team
  • Certainly Bot
  • *
  • Posts: 64891
  • Gender: Male
    • Personal Message (Online)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #32 on: December 29, 2011, 10:45:42 PM »
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"? ;)
The best things in life are free.

Offline Lefamonster

  • Newbie
  • *
  • Posts: 3
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #33 on: December 29, 2011, 11:52:50 PM »
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.

Offline avast@ advantage77.com

  • J.R. Guthrie - avast! Rising Star 2010
  • avast! reseller
  • Advanced Poster
  • *
  • Posts: 722
  • Gender: Male
  • avast! Distributor & Platinum Reseller
    • Advantage Micro Corporation
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #34 on: December 30, 2011, 12: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?
Advantage Micro Corporation
http://www.advantage77.com
520-290-0595

Offline igor

  • avast! team
  • Serious Graphoman
  • *
  • Posts: 11335
  • Gender: Male
    • AVAST Software
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #35 on: December 30, 2011, 09: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.)

Offline igor

  • avast! team
  • Serious Graphoman
  • *
  • Posts: 11335
  • Gender: Male
    • AVAST Software
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #36 on: December 30, 2011, 10:07:57 AM »
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?

Offline Lefamonster

  • Newbie
  • *
  • Posts: 3
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #37 on: December 30, 2011, 02: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.
« Last Edit: December 30, 2011, 02:27:25 PM by Lefamonster »

Offline igor

  • avast! team
  • Serious Graphoman
  • *
  • Posts: 11335
  • Gender: Male
    • AVAST Software
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #38 on: December 30, 2011, 02: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.

Offline lifeson99

  • Newbie
  • *
  • Posts: 8
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #39 on: December 30, 2011, 04:11:02 PM »
I went to the Patch website that PK posted at:
     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.

« Last Edit: December 30, 2011, 04:20:25 PM by lifeson99 »

Offline igor

  • avast! team
  • Serious Graphoman
  • *
  • Posts: 11335
  • Gender: Male
    • AVAST Software
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #40 on: December 30, 2011, 05: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?
« Last Edit: December 30, 2011, 05:57:59 PM by igor »

Offline ady4um

  • Massive Poster
  • ****
  • Posts: 2676
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #41 on: December 30, 2011, 06: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.
ADD/REMOVE PROGS -> avast -> CHANGE/REMOVE -> REPAIR & REBOOT
Avast! 7 FAQ | FAQ & KB | Docs | Removal Utils | Configure Mail Shield | report FP | License Registration | UNSECURED?

Offline lifeson99

  • Newbie
  • *
  • Posts: 8
    • Personal Message (Offline)
Re: Exclusion does not work - SOLVED ! !
« Reply #42 on: January 02, 2012, 01: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. 


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


NOTE:  this ONLY applies to v6.0.1367 with the Exclusions patch applied.
« Last Edit: January 02, 2012, 03:48:50 PM by lifeson99 »

Offline igor

  • avast! team
  • Serious Graphoman
  • *
  • Posts: 11335
  • Gender: Male
    • AVAST Software
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #43 on: January 02, 2012, 01: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.

Offline DavidR

  • avast! √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 69240
  • Gender: Male
  • No support PMs thanks
    • Personal Message (Offline)
Re: Exclusion does not work after the new Avast-update 6.0.1367
« Reply #44 on: January 02, 2012, 02: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).
Core2Duo E8300/ 4GB Ram/ WinXP ProSP3/ avast! free 2014 9.0.2018/ Outpost Firewall Pro9.1/ Firefox 28.0, NoScript, RequestPolicy/ MailWasher Pro/ DropMyRights/ MalwareBytes AntiMalware Premium 2.0.1/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security

 

Google Chrome

AVAST recommends using the FREE Google Chrome™ browser.

Download Google Chrome Now