1. When executing a PDF file from the file viewer program 'V' (v10 : http://www.fileviewer.com/), Acrobat Reader v8.1.4 is launched, but immediately terminates.

2. When executing a PDF file from Windows Explorer, Acrobat Reader v8.1.4 launches properly, but cannot be exited without first exiting Windows Explorer (Acrobat Reader terminates but is immediately relaunched until Windows Explorer is first terminated).

FWIW, the IE7 crashes and problems with Adobe Reader v8.1.4 are still present in v3.35.28.

I had to go back to v3.35.23.

My apologies. The strange behavior I reported is actually due to an interaction between Adobe Reader and AutoSizer, not Sandboxie. Multiple forces at work here and I jumped to the wrong conclusion. Sorry
'bout that.

tzuk,

There still appears to be a problem with Adobe Reader v8.1.4 and Sandboxie (v3.35.31). If nothing but Windows Explorer is running in the sandbox and I right-click on a PDF file and select "Run Sandboxed", Adobe Reader comes up for less than a second and immediately terminates. If IE7 is also running when I try to execute the PDF file sandboxed, everything is normal. Would you please take another look at this strange scenario.

Thank you.

tzuk,

Some additional information regarding the problem where executing PDF files by selecting "Run Sandboxed" from the right-click menu in Windows Explorer causes Adobe Reader to come up for an instant and then close unexpectedly...

This problem only occurs if nothing else is running in the sandbox. If IE7 is also running in the sandbox, there is no problem and everything is normal. It would appear that IE7 successfully loads something that is also needed by Adobe Reader, but Adobe Reader is unable to load it on its own.

This problem does not exist in v3.35.21 and prior. It started in v3.35.22 and exists in all versions since.

Thank you,

Ron

I see some of the same behavior with Adobe Reader 8.1.4 on XP SP3. Some observations...

1. Reader executes and immediately terminates if launched via the Run Sandboxed context menu command for both Reader and PDF file shortcuts.

2. IE, whether 7 or 8, is not a factor. The existence of any sandboxed process will allow Reader to execute normally via context menus.

3. As a workaround, try designating acrord32.exe as a Forced Program and do not use context menus to run Reader sandboxed.

I'm glad it's not just me.

Hopefully, tzuk will find the cause and fix it (it's a problem that was introduced in v3.35.22).

I understand the problem now. Acrord32 is (and has been for a very long time) set as a lingering program. The thing that terminates lingering programs is SandboxieRpcSs, but it never terminates programs that were already running when it itself (SandboxieRpcss) started.

Before the change in 3.35.22, "Run Sandboxed" would start Acrord32.exe first, and then launch SandboxieRpcSs, so the latter would ignore the former.

After the change in 3.35.22, "Run Sandboxed" starts SandboxieRpcSs first, and then Acrord32.exe, which of course is immediately considered a lingering program (as it is the only one "left" in the sandbox), and then terminated.

This is why forcing Acrord32.exe as nick s suggests works, because it has the end result that Acrord32 runs before SandboxieRpcSs.

Another solution is to unset Acrord32.exe as a lingering program, which may have a disadvantage of its own.

It looks like I will have to revise this mechanism a bit more in the next version.

This should be fixed in version 3.36.03.

http://www.sandboxie.com/SandboxieInstall-336-03.exe

It appears to work fine now.

Thanks a bunch!