Please understand that it isn’t enough to say it’s a FP. The software I distribute with this DLL goes to people who also use Avast. In addition, I can’t get Avast to ignore it (as a FP) per UI.
Avast is hitting on a DLL from Kellerman Software (and the installation exe), but according to VirusTotal, Avast is the only vendor that is.
Hit is:
Antivirus Result Update
Avast MSIL:GenMalicious-BWD [Trj] 20150117
SHA256: 104e99152e9d1c6662e52f2c156833beee8376f42ed7cb27ef56f65719464411
File name: NET-Logging-Library.exe
Detection ratio: 1 / 57
Analysis date: 2015-01-17 03:22:41 UTC ( 0 minutes ago )
Thanks for writing. But as I said in the OP, adding it to the exclusion list of an individual workstation is not a solution-or even a fix. I distribute software with this FP to others.
Adding files, directories, etc. to Avast 2014/2015 Free has never worked, and even reporting doesn’t work (the links don’t “do” anything when clicked). When I add manual exclusions and re-open settings, they are gone.
So my request is to update Avast’s definitions to be as accurate as the other 57 on VirusTotal.
Thanks!
pat
P.S. I didn’t see a place at the blog URL you gave to submit a FP.