Avast 5 Pro Sandbox Broken

by malwarekilla on February 8, 2010

I was working on my Avast 5 pro pre-video testing when I got this lovely message below.

020810 1555 Avast5ProSa1 Avast 5 Pro Sandbox Broken

For some reason I can’t launch Internet Explorer 8 sandboxed. The context menu just says “Run Outside the Sandbox” and if I try to add a process manually I get the message above.

I’ve tried this on 2 different boxes with the same result. I’m using build 5.0.396. I know I’m not the only one because I’ve found other threads with people having the exact same issue as myself (and on the same build).

{ 8 comments… read them below or add one }

Dieselman February 8, 2010 at 5:39 pm

Sandboxie and Avast Free is all you need.

malwarekilla February 8, 2010 at 6:06 pm

Yeah, looks like it. I would be really pissed if i had bought the pro version.

Vilmis February 8, 2010 at 8:01 pm

I found Avast 5 very unstable. When I used it sometimes it wasn’t updating for days. Don’t trust it anymore. Sorry for fans.

idontlikemalware February 8, 2010 at 8:08 pm

Oh my, I’m surprised that avast puts the avast 5 pro on the market that it doesn’t work fully. I guess, they have to go back to the drawing board.

Buck February 9, 2010 at 2:49 am

Avast 5 Pro Sandbox hasn’t worked since the first release. Hard to believe Avast would release a new version and one of the best features of the program isn’t working. The sad part is Avast even new the sandbox wasn’t working properly and still released it. Doesn’t speak well for them.

matty February 9, 2010 at 5:34 pm

please don’t install avast 5 with chrome, kaspersky, and several other scanners found win32.trojan.krap.au somewhere in it. it turns out google is spying bigtime like rising and zonealarm programs.

GTR February 9, 2010 at 10:37 pm

When I tried Avast! 5 Pro the sandbox worked fine. Could be a update problem. Not tested with IE8.

Rednose February 9, 2010 at 11:11 pm

If you would have taken the effort to vist the Avast! forum you could have found out that we ( the community ) were aware of a IE virtualisation bug, and that a fix was in the pipeline. So try the pre-release 5.0.415 build, that should have fixed it.

Greetz, Red.

Leave a Comment

Previous post:

Next post: