Hi!
Is there a way to disable those DAMN reputation services??? Previous versions had an explicit option to do so, but that option is gone in newer versions.
I have disabled cybercapture AND hardened mode and I STILL GET “Filerep:mlaware” false positives, I’m sick of it!
Is there a way???
Have you tested file at www.virustotal.com ?
you may post link to scan result here
If you think detection is wrong, you may report it to avast lab
How to report info:
https://forum.avast.com/index.php?topic=14433.msg1289438#msg1289438
I report ALL FP I find, but the latest I couldn’t because the file is 95MB (max size allowed is 50Mb, so I’m screwed). But, anyway what I want to do is DISABLE THOSE DAM FILE REP SERVICES, like it was possible in previous versions.
Ok, found the option, thanks!. Another feature missing is the ability to add a file to the exclusions without specifying its exact location,
e.g. *\file.exe would exclude file.exe from the analisys, no matter where it’s located.
I must say I’m pretty disappointed since the new interface was introduced. less and less control for the user.
You’re welcome.
No you are not, if you used the link i posted you will find that there is a avast FTP server option
Please note that disabling the use of reputation services diminishes Avast detections (i.e. the protection) significantly as more and more files are detected by cloud only.
As for the exclusion option - exclusions are a dangerous thing, and the ones with wildcards double so, so we are certainly not adding such an option. An experienced user can add the wildcarded path easily (manually).
I know what I’m doing, I’m not some newbie.
the new interface does not allow the use of wildcards. whenever I try to use a wildcard, avast automaticallt thinks it’s an URL, not a path…
You may not be a newbie, but Igors comments are also there for the guidance of others who may be reading this topic (currently Read 207 times in only 8 posts).
OK, that is a bug.
see? thats’s what I’m talking about. I tried to enter “*\file.exe” as a test, and avast added TWO entries to the exclusions:
http://\file.exe/
https://\file.exe/
that IS NOT what I wanted. I wanted to exclude file.exe from the basic shields no matter where it is located.
Yes, It is a bug, and it is NOT FIXED IN v19.8. I just tried to add “file.exe” to the exclusions, instead avast added TWO URLS, instead of the filename I want to exclude. PLEASE fix this.
Care has to be taken in the use of wild cards as it could be leaving a large hole in your security.
Why not be more selective and use of the single character wild card you could try this string “?*\file.exe” (without the quotes) that would be any-drive letter\any-folder\subfolder\file.exe, etc.
EDIT: Where are you trying to enter this ?
EDIT2: OK I found where I think you were trying to do this and the above failed, because I did it wrong, it should have been “?:*\file.exe” (again without the quotes) I missed the colon this worked in the exclusions just fine.