Julian how do you start Reader? I click Run Sandboxed on the desktop shortcut and it opens fine. Also when AcroRd32.exe is set as a forced process. I checked with Drop Rights both on and off, on 64-bit Windows 7, I tested with a new installation of Reader X version 10.0.0.

As a forced process.


I tried this all but didn't help.

Hmm, may or may not help, but have you tried deleting your sandbox first before trying to run Reader X sandboxed?

Thank you for the new beta.

But sadly a sandboxed "Adobe Reader X" still shows errors on my XP (SP3, 32bit). Opening only the Reader by using its icon works perfect now. But if you open a PDF file some errors will occur.

If is "Protected Mode" turned on, one of my tested PDF files needs a extreme long time before showing in the reader now.

Another error occurs after closing the Reader (with "Protected Mode" turned off), because the Reader always tries to restart every few minutes. The Reader doesn't show up, but with "Sandboxie Control" you can see that there is a restart of two AcroRd32.exe processes. Also deleting the sandbox or killing the processes using the "Task-Manger" didn't stop this strange behavior.

Of course the sandboxes were clean.
Creating a new sandbox doesn't help either.

Will try a complete reinstallation of Sandboxie.

I tested the new beta version with the "Adobe Reader X" ("Protected Mode" ON) a little bit more:

I opened one PDF file by using a double click. Everything works fine. The only strange thing is that "Sandboxie Control" shows three AcroRd32.exe.
After that I tried to open 3 other PDF files by using double clicks, but no new Reader windows appear. "Sandboxie Control" shows ten AcroRd32.exe now. After waiting about 5 minutes all Reader windows pop up. After closing all Reader windows "Sandboxie Control" still shows two AcroRd32.exe. I have to use "Terminate All Programs".

I hope you can find a solution for this. Thank you.

I found the trigger for the strange restart behavior! If you click (no double click!) on a PDF file in the "Windows-Explorer" two AcroRd32.exe processes get started. It looks like the Reader wants to start a pre-caching or something like this. I think this causes the other problems I wrote above. Please check this. Thank you very much.

Julian, I'm not really sure what to tell you. I think in a general sense the problem was fixed, and you'll probably need to experiment a bit and find the cause of this specific behavior in your specific system.

Guest101, are we talking about a regular Windows Explorer window, or a sandboxed Windows Explorer?

from my point - works here also on my personal build portable AR_X.

Seems to solve everything for me.

But may I ask what was the solution? Do you turn off Adobe's protection on the fly? If so, how did it solve the PDF upload issue?

Tzuk, it is a regular Windows Explorer window (not sandboxed). In my sandbox settings "AcroRd32.exe" is set as a forced program.

(The PDF files for testing have to be on a local hard drive. On network drives the pre-caching of the Reader doesn't start.)

Additionally to the clean reinstallation i uninstalled Online Armor and now it works as expected.
Will try out if OA was guilty at a later time.

@Guest101: Here Adobe Reader behaves normally when starting PDFs with Explorer.

Strange, I have 4 PCs with XP SP3 here and all of them show this behavior. The only thing I changed from the standard settings of the "Adobe Reader X" is that I have disabled the autostart of "Reader_sl.exe" and "AdobeARM.exe" with msconfig.

lwc, I'm not sure how it fixes your upload problem as I never got around to testing it. The problem was conflicting sandbox mechanism and I had to make sure the Sandboxie mechanism comes on top and overrides the other one.

Are there any news about the behavior with the "Windows Explorer"? I think what I described as "pre-caching" has something to do with the file properties: If I click on the PDF file with the right mouse button and select "file properties" the properties under the tab "PDF" are blank always.