AVG treats MSVC-compiled binaries as potentially hostile

Viruses & Threats
5

The version is: 17.3.3011, virus definitions version is: 170410-2

4

Hello Christian,
We apologize for the inconvenience. To assist you better, could you please let us know the version of AVG installed in your computer?
Thank you

1

I've noticed that with msvc 2017, AVG treats all compiled binaries as potentially hostile and must first scan them before executing.

Needless to say, this is quite annoying when it comes to developing software as every time I attempt to run a test binary for the first time, it must first be scanned. This is also cumbersome with vcpkg which installs packages that also create binaries.

The scans all return fine so it's not actively removing or quarantining binaries as they're created but it's annoying nevertheless.

Is it possible to get AVG to recognize binaries from the newest C++ compiler? I don't remember having this issue before I upgraded compilers.

2

I believe I have the same/similar problem. Everytime i run a program from the MS IDE AVG scans it delaying testing by about 10-20 secs.
AVG Built is 1.171.3.211. Only happens since this version of AVG was installed. How can I turn this behaviour off?

3

Hello Christian,
We apologize for the inconvenience. To assist you better, could you please let us know the version of AVG installed in your computer?
Thank you