That’s not completely clear at the moment… could be 7.
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?
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:
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.
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.
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.
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.
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.
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.
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?
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.)
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.
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.
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.
