The .exe I'm building is currently recognized by Avast as "File might be dangerous". It is not a false positive because the antivirus software finally doesn't find any virus in it, but just an alarm saying that this file has been "rarely downloaded".
I've contacted Avast but they don't seem to offer a solution except sending them the .exe for whitelisting.
Things I have tried, but that didn't solve the problem:
Have proper
resource.rc
file in Visual C++, with details about the .exe:BLOCK "StringFileInfo", VALUE "CompanyName", "MyCompany\0"
, etc.Use
makecert
,certutil
,signtool
as detailed in this answer: How do I create a self-signed certificate for code signing on Windows?
Things that won't work:
Add to local avast exclusion (I can't ask every customer to do this!)
Redo a "Submit file to Avast Lab for scan" for each new build of the .exe. It's not scalable to have to re-submit the .exe to Avast (and all other 50+ antivirus software!) for each new build.
Paying $200 per year for code-signing (it might work, but I don't find it fair to have to give a $xxx ransom per year just for being whitelisted)
Are there common solutions that can help to avoid "Rarely downloaded file / File might be suspicious" antivirus alarms?
Note: I've read How to prevent my .exe to be recognized as malware?, how can I make my software not to be discovered by antivirus?, but it did not really cover the topic here.
Note2: I've read these guidelines, etc. but it did not currently help.