Avast 2014 conflicts with Microsoft Visual Studio 2013

[erwinbantilan]

Hi,

Everytime i compile a program on Visual Studio 2013, Avast detected the compiled program as malware that make Visual Studio 2013 unusable..

The only workaround I do, is to disable temporarily the Avast in order for the compiler to works..

Any settings on avast to disable automatic scanning and detection on specific folders?

Hope this will fixed very soon!

Thanks!

- Erwin

[JuninhoSlo]

You can try this:

Open Avast-Settings-Active Protection-File System Shield-Scroll button-Exclusions-Add-Browse-Add Microsoft Visual Studio 2013 map (Program Files)-OK-OK-That,s it


Send FP detection to Avast lab

[NoelC]

Excluding parts of the system aren't really a valid long-term workaround.

But you may never get relief if you don't report the false positives back to Avast, and it now seems to be easier to do than it used to be.

If you don't get prompts that lead you through it, get into the Virus Chest and submit from there.

For a while it was doing the same thing for me, by the way, reporting some kind of Evo:Gen problem, but that seems corrected.

-Noel

[lukor]

Go to Settings / Active Protection / Deepscreen - and disable that.


If you create new apps (compile) they simply can not get any reputation on our cloud servers. Frequently this in itself is enough for the app to be targeted suspicious by deepscreen. DeepScreen simply isn't a feature for someone who compiles its own programs.

[ank91]

i have MS VISUAL STUDIO 2008 + SQL SERVER 2008 R2 + NET BEANS + APACHE TOM CAT+ MY SQL + WAMP SERVER installed on my XP machine.
and MS VISUAL STUDIO 2010 on my W7 laptop.

and never face any problem with avast 9 or avast 8.

[dj1.nc]

@lukor

I really wish you were right, but simply turning off DeepScreen in Avast 2014 is not enough.  I make multiple apps in Visual STudio 2012, and I can tell you that even with Deep Screen off, Avast will still pop right up and destroy the compiling process by saying the .exe is a virus (the crazy "evo-gen [susp]").  The only way I can get Avast to stop doing that is to manually enter-in exclusion directories for every directory where I create apps!  ...or make an exclusion for some high-level folder.