Self written program blocked

Avast Free Antivirus / Premium Security
1

Hello,

I have written a C# application and it seems Avast is SILENTLY blocking opening of the exe.
If Avast is active no notification appears of any kind, but when I look in the autosandbox.log file if find entries of my exe:

10.11.2015 16:26:56	Autosandbox candidate: C:\Program Files (x86)\flk\flk Client\flkClient.exe
	[Source: http://flk.oberbauer.co/flk/Download.ashx]
	[Opened by: C:\Program Files (x86)\flk\flk Client\flkClient.exe]
	[Reason: 0x00020000]
	 --> Result: Sandboxing (NG component is not installed)
	 --> Instrumentation: Instrumentation inside sandbox requested

Why is my file blocked at the moment the file should only open a small login window, but that never appears if Avast is active.

Hope someone can guide me in a direction to solving this problem. Thanks in advance.

Regards
Paul

2

upload your program and scan it here www.virustotal.com if scanned before, click rescan for a fresh result

Post Link to scan result here

3

What OS/SP ?
What exact version of avast ?
What is your application supposed to do ?

4

I have almost the same problem. I have several installers (created with the old Wise Installation System 9) signed, tested and properly working weeks ago. Some of them not work now. I see the UAC warning “Do you want to allow …” and after I click Yes nothing happens. The installer executable appear in Task Manager under Background Processes, but not in apps. The installer works if I disable shields or disconnect from internet. Virustotal not see problems. I not understand why some installers still work, but others - not.
Windows 8.1 Pro 64-bit Avast Free Antivirus 10.3.2225 definitions 151111-2
autosandbox.log
12/11/2015 05:58:17 Autosandbox candidate: C:\Users\uuu\AppData\Local\Temp\GLB9459.tmp
[Source: local://*D:\aaa\Setups\aaa-64bit-INSTALLER.exe local://*C:\PROGRA~2\WISEIN~1\Wise32.exe ]
[Opened by: D:\aaa\Setups\aaa-64bit-INSTALLER.exe]
[Reason: 0x00020000]
→ Result: Sandboxing (NG component is not installed)
→ Instrumentation: Instrumentation inside sandbox requested
Any idea what happens?

Regards
iHoo

5

I had the same thing happen today and wondered why I didn’t get the usual DeepScreen warning. So, I updated to v151111-2 (free version) and the problem went away.

HTH,
Rick

6

I’ve had the same issue with an app I wrote myself many years ago that had “password” in the file name (wondering if this was the trigger that caused Avast to consider it a threat and block it) so I just added the file path and name to the Avast exclusion list for this password maintenance app, problem solved.

7

Hello,
create a ticket in https://support.avast.com and attach the detected sample(s), please.

Milos

8

Same problem here. I uploaded a few samples with the ticket. Not every program is blocked, but most are.

Gilbert

9

Sample uploaded, the problem still exist with 151112-1 definitions.
Thanks, iHoo

10

I thought I had the problem fixed by updating the version when it was released on the 12th, but later that day it happened again, so after 10 years with Avast I decided to switch to another antivirus. Sad, that.