Tjyylli

You have to disable Avast DeepScreen:

Open Avast user interface>Settings>Antivirus uncheck, Enable DeepScreen.

It is now a much smaller option on the same page, (6th one down)

The option is harder to find (in my opinion) for the different version I have (version in the image).

In Avast Premier 2017, disabling Hardened Mode does nothing! Instead you have to disable CyberCapture as shown below:

As others have mentioned, the culprit is DeepScreen. It's especially bad if you have Avast set to Silent/gaming mode because then you can get unexpected/bizarre behavior and have no idea why. (I spent an entire day debugging the installer for a program I'm developing because it suddenly started running twice every single time I launched it--DeepScreen is very forgetful--and only succeeding on the the second run.)

Going under Settings, Update, Details, you can turn off popups for the majority of them--the annoying update-related popups, which should make it easier to work undisturbed, play video games, etc. But DeepScreen popups still pop up!

CANNOT DISABLE DEEPSCREEN: I've tried disabling DeepScreen entirely (under Settings, Antivirus), since it's so disruptive, but this checkbox appears to have no effect.

Unfortunately, the only way I currently have of disabling DeepScreen (in Avast 2014.9.0.2021) is to disable all shields! And I'm not even sure that this is working, since I sometimes get DeepScreen popups even with all shields disabled. Avast can't be prevented from starting with Windows during boot, so maybe uninstalling Avast is the only solution.

[Note: I'd appreciate upvotes if possible, so I can get enough rep to participate here at SU via comments. My rep from stackoverflow doesn't apply here, sadly. Those feeling extra generous could upvote 253935 too... :)]

As you are using Avast double click on the Orange Avast Orb.
Select Settings, and then select Antivirus.
Scrolling down the Screen you will see Exclusions.

If you select Exclusions and the directory you are compiling to.
you will be able to compile from any directory you exclude.
Without any troubles.

If none of these worked as they didn't for me try this.

Open Avast > Settings > Components > Files System Shield > Customize > Exclusions > Add the path > OK > OK and you're done.

I Added a file path exclusion for my entire dev folder d:dev* and this worked using Avast Professional 2017:

1. Right-click Avast icon in the system tray


2. Select Open Avast user Interface


3. Click Settings at the bottom left of the window


4. In the General tab scroll down to the Exclusions entry


5. Enter a folder name in the File paths tab e.g. d:dev* (Every file and sub folder of the dev folder will be ignored)


6. Click ok, bottom right and the changes will be applied immediately

I didn't change Enable Cyber Capture or any other setting

I have tried all of the other solutions, like adding an exclusion or deep screen exclusion or exclusion to File System Component shield or disabling deepscreen, etc. The only solution that works for me is to stop the Avast service in services.msc or Computer Management/Services.

I create D:ProjectDir then put source code or solution under this directory.

Open Avast > Settings > Exclusions > File paths and add D:ProjectDir*bin**

this is safer than adding rule D:ProjectDir* because avast will scan source code for example in D:ProjectDirmyapp but not compiled app located at

D:ProjectDirmyappbinDebugmyapp.exe

D:ProjectDirmyappbinReleasemyapp.exe

With new avast (2018) Exclusions is enough you don't need to disable DeepScreen

if still not work your app is truly Virus you need to disable or uninstall Avast :lol:

At the risk of annoying the more experienced participants:

• Xonatron is correct, CyberCapture is the culprit - at least in my case, too;


• AFAIK, CyberCapture is enabled by default, so it seems to me this presents the problem with Deployment, since the end users will likely have exact same issue, now on their machines with the already-compiled programs... twice: once during the installation, and the second time when the program will run for the first time. Asking every potential user to disable CyberCapture doesn't seem feasible, so it seems this thread does Not have a resolution yet...


• AND YET... How come CyberCapture doesn't affect any other programs except for the Visual Studio-compiled ones? I'm yet to download anything that would trip CyberCapture's "15 seconds of Death" behavior, and yet my own VB Net programs always do trigger it. On every install and every first run. Bummer.

Now on to the annoyance: I do not have enough reputation to pose this as a Comment, so, unfortunately, chiming in as an Answer - apologies. Experienced people here may be able to edit/rectify this somehow.

Bottom line: I don't think this question has been resolved yet. But would love to hear of solutions/workarounds, if any.

Here is an addition to @PhilG 's answer:

Go into

(example of a working avast settings).

In the picture above you can see Exclusions. Add a new file path under File paths tab.

If you want to only exclude an .exe file, add its path under CyberCapture tab.

Done all the things above (including scanning/excluding the directory/exec where the exec is located) but 20 second after starting, avast kill it. No message, no quarantine, but i have found a way to circumvent the problem:

1. stop all avast agents


2. start the exec.


3. reactivate all agents.

everything is ok until next boot.

But if i can't find any valuable solution, i'll kill avast definitly !