Annoying false positives: Win32-Evo-gen [Susp]

[REDACTED]

This is getting really annoying now, and i am considering going back to avira just for this one issue:

The false positive heuristics is way to aggressive, e.g. with this line in my c# project

Code: [Select]

MessageBox.Show("Test", "Caption", MessageBoxButtons.OKCancel);avast is happy, however when i want to grab the result (which button was pressed)

Code: [Select]

var result = MessageBox.Show("Test", "Caption", MessageBoxButtons.OKCancel);uppon compilation avira (latest version as of 17th december 2015) reports that my executable is infected with Win32:Evo-gen [Susp] and only lets me chose between blocking actions (move to virus container, delete, prevent access) and there is no ignore-this-false-positive option!

This is just one of 50 times i have gotten this annoying false positive because of bad heuristics. Please fix this.

See https://ideone.com/XO92Bm

[Eddy]

uppon compilation avira (latest version as of 17th december 2015)

Unless you mean avast, talk to avira.
Latest avast version is not from 17th december, but from 1st december
https://forum.avast.com/index.php?topic=179855.0

It is not a false positive since it isn't detected as malware.
Win32:Evo-gen [Susp], avast says it is suspicious, not malicious.

Why not simply set a exclusion for your working folder ?

[REDACTED]

Unless you mean avast, talk to avira.

Yes, i meant avast of course. 

Latest avast version is not from 17th december, but from 1st december

"With latest virus signatures files available, AS OF today, the 17th of december."

Why not simply set a exclusion for your working folder ?

Or you could improve your product.
Edit: So your solution is to disable the product, rather than fixing the issue in the first place.

[Eddy]

Latest VPS (signatures) is not the same as latest avast

It is not my product.
I'm just one of the many users of avast and one of the few(?) who is trying to help other users here.

I suggest you submit a sample to avast so they can have a look at it :
https://www.avast.com/contact-form.php?subject=VIRUS-FILE

No, I did not say to disable avast.
I suggested to add a exclusion for your development folder.