Avast, or more precisely only it's filesystem shield, is evaluating binaries (both executables and DLLs) compiled in my Delphi 7 (personal) as supicious (Win32:Evo-gen[susp]). Not all of them, but enough to annoy me (~20-25%). They are catched while the delphi is saving them, effectively making compilation impossible. But when I add output folder to list of excluded files and successfuly compile them, and then scan them, they are all clear!
This happens for quite sime time, but lately, say 6 months, maybe a year, number of these false positives is increasing. Avast now marks years old binaries as malware, but they were clear all the time and did not change over night. And again, scan is clear, but should I copy them - avast interfere.
I have reported false positives many times, every time with the affected file, sometimes even with full source code. Nothing happened.
So here I am - what should I do to solve this problem? Please, do not say to add those files to exclusion lists, i have already done that, but what should I say to the users that happens to use my programs and the avast on the same system?
EDIT:
Some additional info:
- OS: WinXP Pro SP3, updated today
- Avast Free, program version 2014.9.0.2006, database 131121-1
- Delphi 7 Personal, ver. 7.0 (build 8.1)
- no, i do not have W32/Induc-A
I can upload some example binaries if it helps.