49
7
I've been practicing my C# lately on a new system. Compiling is fine, however when I try to run the generated .exe
file, avast! thinks it is malware and runs it in the sandbox for a while (and it doesn't work in the sandbox as it should work normally), and only when it has finished scanning it will it let me run it normally.
When I try to run it again, most of the time the same process happens, whether I make changes to the code or not.
Is there any way I could play around with Avast's settings to stop it attacking my programs?
Note: I'm dealing with very simple, command prompt programs here.
5The comments here are terrible. Pointing fingers at OP instead of simply helping, or "it works for me!". The very idea that the program is only being scanned because "it's doing something dodgy" is crazy -- how does Avast know if it's doing something dodgy if it hasn't scanned it yet? :) Personally I get this all the time on a wide variety of programs I've compiled myself for whatever reason.e.g. SumatraPDF I suspect it's because these files are signed or 'installed' in any way. – Pod – 2016-11-14T09:23:14.577
Instead of making exclusions for our own computers, is there a way to submit files to Avast with a claim that "I compiled this and it's safe" to hopefully get it flagged as safe in their screening thing? – endolith – 2019-10-10T19:42:59.347
6have you tried setting an exclusion folder for your root code folder? – DiskJunky – 2013-02-22T17:34:40.247
I have never, ever dealt with a problem like this. Either your EXE is doing something strange, or you need to dump this Avast app. That said, looks like you're not the only person why may have encountered this. I found several related links using [this Google search](https://www.google.com/search?q=.net+avast&rlz=1C1CHFX_enUS375US375&aq=f&oq=.net+avast&aqs=chrome.0.57j0l3j62.6537&sourceid=chrome&ie=UTF-8#hl=en&rlz=1C1CHFX_enUS375US375&sclient=psy-ab&q=.net+c%23+executable+avast&oq=.net+c%23+executable+avast&gs_l=serp.3...8576.11646.0.11748.14.14.0.0.0.4.179.1801.0j13.13.0.les%3B..0.0...1c.1.4.
– None – 2013-02-22T17:35:53.443Weird. I run Avast and I'm a .NET developer for a living as well as doing a great deal of development at home in my spare time. I've never had Avast complain about one of my apps. – Pete – 2013-02-22T17:57:05.683
Disable Avast from scanning the directory where your .exe file is located. The fact your .exe is being blocked by Avast means your doing something nasty or odd enough Avast is flagging it. A normal program would not do this. – Ramhound – 2013-02-22T18:43:44.627
@Ramhound how would I do that? – Bluefire – 2013-02-22T19:05:00.543
@Bluefire - I don't use Avast because of quality issues. Normally I would just read the manual and follow the directions. – Ramhound – 2013-02-22T19:40:43.863