I just started using (Process Virtualization) feature in Avast! 5 Pro Build 5.0.594.
I just want to use it with Browsers like IE8. And the problem is when I open some random web sites I keep getting a User Account Control popup for Java. And after I click yes I get another popup error message!
How can I avoid these popup messages?
Also are there any downsides to always running IE8 in (Process Virtualization)mode? Like slowdowns or other annoying things?
If there would be slowdowns or annoying things always happening then I rather not use (Process Virtualization) and in that case I can save money and just run Avast 5! FREE.
Does running IE 8 in (Process Virtualization) really make a big difference in Safety?
yeah I don’t use IE8 so I can’t confirm but I’m pretty sure that this issue you’re reporting has been mentioned already, and noticed by the Avast team. That’s a known conflict between IE/java plugin and the virtualization. I remember it was then advised to disable Java (just the add-on in IE), which might not please you ;D okay obviously the issue isn’t fixed.
Actually after some more testing I only get these popups when opening the web sites from my “Favorites menu” in IE8. If I type in or paste the address in the address bar then the web site loads fine without any popup messages about Java.
And I even get popup messages about Java when just opening a new tab or even a new window sometimes
Ok I am now also running Google Chrome build 6.0.472.0 in (Process Virtualization) mode and I am not seeing any of the popup and error messages like I always see in IE8!
I couldn’t reproduce the issue with Java, went to the site you gave…anyway, I still had a crash when opening a second time IE8 (32) virtualized. Same issue as always, the more you reopen it sandboxed, the longer it takes to open, the more chances there are that it crashes. It’s been like that for months, well on my system : (same with 32 or 64 bit version)
Given my observations it is best to use Firefox with process virtualization. However, there exists a catch. You must include not only the executable for Firefox (firefox.exe) but the container program for plugins (plugin-container.exe). The problem seems to be that some plugins that browsers use are inaccessible while the browsers are in a container. Worst comes to worst you can simply right click your browser’s desktop icon or start menu entry and select to run outside of the sandbox once.