Can't terminate Auto Sandbox - Stuck analyzing suspicious program

Why can I not terminate Avast! when it is analyzing a program. I click the terminate now but it doesn’t stop counting the duration. It’s over 30 minutes now. It is very annoying and it won’t even let me terminate with task manager. The program is a very safe script written by another programmer friend of mine that does nothing harmful. At any rate it should not get stuck on this.

Can you please fix this bug? It should allow you to at least terminate the program so you can then change settings to allow the unknown program.

It is so badly stuck I cannot even shut down the computer without a hard reset.

Thank you.

Can you right click the avast tray icon and disable shields control, then enable shields control, and get past this point?

I have heard of Polymorphic infections looking for mouse clicks during execution, to try and determine if they are being executed virtually.

This could be a new mechanism like that, and it’s waiting for a click thayt will never happen. I am thinking out load here!

Sincerely,

J.R. “AutoSandbox Guy” Guthrie

“At this point in time, the Internet should be regarded as an Enemy Weapons System!”

Thanks for the reply. I can disable and re-enable Avast but it doesn’t stop this process. I can click the little X in the top right of the auto sandbox notification window and it disappears but the process it is trying to sandbox is still stuck in the task manager and if I go back to the explorer window where the original file is, and try to click the file again, explorer stops responding and I cannot end process no matter how much I try. It becomes stuck so bad that even if I try to restart or shut down it locks up on shutdown. It seems to be trying to look for a solution but cannot find one. It doesn’t give me the option to allow the process to run.

After I restarted I made it ASK instead of always Auto sandboxing and then it allowed me to run the .exe in question.

Note again: this is a safe .exe, just unknown to Avast.

“Ask” is the correct setting here. Make sure you get that file in either AutoSandbox exclusions, or global exclusions. And “Ask” should alleviate this situation in the future. Job well done!

Thanks, but I still think it’s a bug, so that’s why I reported it.

Oh, you are absolutely right that it is a bug (well, it’s either a bug or corruption). P.K. may need a copy of that file to debug this. He is the AutoSandbox head guy at Avast software.

Sincerely,

J.R. “AutoSandbox Guy” Guthrie

“At this point in time, the Internet should be regarded as an Enemy Weapons System!”