Autosandbox - It's a Bug? - NOW I GET A BSOD

Yesterday I’d this problem with SBC SP1 and Avast BP 6.0.1253.
A client tryed to run a secure program from the server SBS 2003.
This program was autosendboxed from avast on server.
The problem is this: on the server appeared the window that ask if open in the sandbox or not, but all the client in that moment couldn’t access to the file server, it’s seemed blocked!
Then I went to server and I see the autosandbox window… and I checked to open the program normally.
After that, the clients were allowed access to the file server normally.
Is the second time this has happened but now I’ve added an exclusion for this program.

Is a bug?

Thanks

Bump…

Hi,

please could you give us more details about this problem? What is that program which avast! wants to autosandbox? Autosandbox pop up should not appear if some user is running any program from the server. I have also tried to reproduce this here in avast! lab and dont see any problem.

thank you very much

First of all, I didn’t check if with the newer version the problem is still.
Second, the program is a stupid dictionary that you can find here (but I don’t remember if is the same version installed on my server)
http://www.dejudicibus.it/dizionario/programma/ita_programma.zip
I try to explain more clearly:
1.this program is installed on a shared directory present on my server.
2.A client try to run this program from the shared folders.
3.Now a window of avast autosanbox appears on server side, but during this period all the other client can’t access to any shared folder present on my server
4.I went on the server and closed autosandbox dialogue
5.All client now can access on the shared folders on my server.

I think that the autosanbox appears also on the client side… but I don’t know becouse I can’t ask all people If they had tried to open the program.

Tomorrow I’ll make some test with the newer program 6.0.1324

Thank’s

Today I tryed to open the program that I have reported with last post, directly from server, but from terminal server: I got a BSOD…
I will send to ftp.avast.com/incoming, minidump and full memory dump, I hope will help you to resolve this problem.
After this BSOD, our network can’t access to our server.
I have uninstalled Avast Business Protection from server and now It works…this evening I’ll try to reinstall avast on our server (Win SBS 2003)

I just had the same problem today, so I can confirm this issue.

On 1st computer (win7 Ent. 64bit) I had .exe file which was then open through a shared folder on 2nd computer.
1st computer has Avast installed. Avast version is Free edition v 6.0.1289

2nd computer (win7 starter 32bit) at that time had McAffee antivirus trial installed (new computer with OEM installed software, although 2nd computer later had McAffee replaced with Avast but the result of the later test repeat was the same)

Opening of the .exe file on the 2nd computer was taking a long time (minutes) which I eventually canceled.
Shared folder was accessed through UNC path with direct access to C drive on 1st computer as in:
\computer1\c$\Setup\dpt\DPT.exe

1st computer had locked screen so I didn’t even see the message from avast about opening in sandbox. When I later tried to log into 1st computer I was unable to do so. The screen remained black and computer was unresponsive. It was answering to TCP ping commands but any other access was not possible (neither file share access, nor RDP connection). In the end I had to power cycle the 1st computer!
I suspect that opening Avast sandbox dialog while the screen was locked might have contributed to unresponsive computer.

The file that I was trying to open which was triggering the sandbox dialog is Dead Pixel Tester from
http://www.dataproductservices.com/dpt
Download here: http://www.dps.uk.com/download.php?file=4