Page 1 of 1

[.08] Bug report? v Sandboxie 4.01.04 and Adobe XI

Posted: Wed Mar 20, 2013 11:33 am
by Prophet
Background:

Windows 8 64 bit
Windows Firewall
Sandboxie 4.01.04
Adobe Reader XI
Avast 8 Free
Internet Explorer 10 Desktop


IE, when sandboxed can't open Adobe PDF pages. I tested it on the IRS.gov website. I got the following numbers that might be an error code at the end of the message "103:103" and with Sandboxie version 4.01.03 I got a DDE timeout/ not responding message.

The avast 8 issues however seem to be resolved with IE 10 or at least improved. Chrome is working. I lost two downloads with chrome (one corrupt, one failed) but I couldn't repeat the problem. Adobe seems to work in Chrome.

Also since v 4.01.04 issues with VMware 9 seem to have resolved. No, I wasn't sandboxing the VM ware, but the virtual machines became glitchy in the Sandboxie/Avast quagmire. I also did several tweaks to Avast so this may not have been a Sandboxie issue at all.

I know v 4.01 is a work in progress and I appreciate all of the great work being done here... I'm just reporting what looks like a bug. When there's a fix or work around let me know.

Thanks and best success ever!

Posted: Wed Apr 17, 2013 8:17 am
by henri
Hi

Nobody can't open pdf in IE10, only when sandboxie; this don't happen in Google and firefox .

See with your eyes.

Posted: Wed Apr 17, 2013 3:29 pm
by tzuk
I will look into this.

Posted: Wed May 01, 2013 12:23 pm
by Gast
The problem persists with version 4.01.07 (x64)

Posted: Thu May 02, 2013 2:32 pm
by henri
Confirme!

Posted: Tue May 07, 2013 4:23 pm
by tzuk
I apologize for the late response with this problem. This will be fixed in the next beta version, 4.01.08.

Posted: Sun May 12, 2013 2:24 pm
by tzuk
This should be fixed in version 4.01.08.

Posted: Mon May 13, 2013 4:10 am
by henri
Many thanks Tzuk!

Posted: Mon May 13, 2013 5:34 am
by henri
Sorry Tzuk. See this post please http://www.sandboxie.com/phpbb/viewtopic.php?t=15458

The problem seems transferred too Chrome.

Thanks.

Posted: Mon May 13, 2013 2:33 pm
by Gast
For IE10 it is fixed in 4.01.08. Thank you very much!