Guest101, I started looking into this and I do see some strange behavior, I hope I can figure this out soon and post another update.

Edit Guest101 please go into Sandbox Settings > Resource Access > File Access > Full Access, and add these two:

\Device\NamedPipe\AIPC_SRV\pdfshell_*
\Device\NamedPipe\AIPC_SRV\AcroSBL_*

I'd like to know if these two make some difference for you.

Thank you for your reply.

After adding these two lines everything works much better now. (The two AcroRd32.exe processes in the sandbox get closed after 2 seconds now and the file properties show up also.)

I hope you can add this to the next beta. Thanks again.

Thanks for the confirmation Guest101. I will be adding this in the next beta build.

Added in version 3.51.05.

Thank you for the new beta release. Sorry for annoying you again, but the trouble with the new Adobe Reader is not gone.

With protected mode off everything works much better now, but following problems occurs:

- If you have an unlucky timing while opening a PDF file by using a double click, Sandboxie clears the sandbox and the Reader shows up for a second only. If you click on a PDF file two AcroRd32.exe processes get started and after a few seconds closed. If you double click the PDF file right in the moment the two processes get closed, Sandboxie starts cleaning the sandbox and the problem occurs.

- If you open the settings dialog of the Reader, Sandboxie shows following error message once: SBIE2205 service not implemented: CM_GDNRP (00000014)

With protected mode on following additional problem occurs:

- Some PDF files need extreme long time before showing up now. (And a second AcroRd32.exe process is open again.)
Please check this with following PDF file: http://denon.de/DE/Downloads/Pages/InstructionManual.aspx?FileName=DocumentMaster/DE/Bed_AVR-2310.pdf


I hope you find a solution for this. Thanks again.

You really shouldn't apologize, it's not an annoyance and I'm grateful that you keep up with recent beta build and can identify new problems.

In this case, as it happens, I broke something in the lingering process mechanism in version 3.51.05. Sorry about that. This causes AcroRd32.exe processes to be terminated without prejudice and I believe this is what is causing your first and third problems.

As for getting CM_GDNRP (00000014). That is due to Sandboxie not correctly implementing the entire array of hardware management functionality. I plan to revisit this area of Sandboxie at some point, but until then, this message will probably stick around as an annoyance. Sorry..

Hi Tzuk! Thanks for your reply. Ok, I will wait for the next beta build (.06) and report my test result after the release. As the massage "CM_GDNRP" appears after opening the settings dialog only, it is no real problem for me.

Please try version 3.51.06.

The first problem seems to be history. I'm not able to reproduce it anymore. With the protected mode disabled the Reader works perfect now. Thanks!

But the third problem still occurs. If the protected mode of the Reader is enabled, some of the PDF files (like my example above) need extreme long time before showing up. (And there is a second AcroRd32.exe process always. Could this the Readers own sandbox?)

I tried your PDF on 64-bit Windows 7 and did not see any problems. But looking in this topic now, I see you're on Windows XP so maybe something is different there. I'll take a look at this again.

Yes, I'm using Windows XP SP3 (32-bit) and a user account without administrator rights. It seems that only protected / restricted PDF files show this problem.

Like many on the net- I did Not like Adobe Reader 10 X, with their new sandbox technology... -
Not only did it fail to work in old sandboxie 3.50, it was very slow outside too (bloatware).
Then many of the easily accessed user-friendly features of 9.4.1 were hidden (Find, Save as, Toolbar...).

I Uninstalled Air & 10x (CCleaner...), and downloaded/ 9.40 from FileHippo (no Air or McAFee in download).
On reboot I immediately went into Edit/Preferences/Update & permanently disabled auto-check for Updates (only way to keep 10x out).
I then went to its' Java folder, and disabled that Security vulnerability (per Windows Secret Newsletter).

I then Googled & downloaded the latest 9.4.1 security update, reboot & installed it/reboot.

Guest101, I'm afraid I am still unable to reproduce the problem. I tested on a standard user account in Windows XP SP3 with a forced AcroRd32.exe. I double-clicked the Bed_AVR-2310.pdf file and the forced Adobe Reader opens almost immediately in the sandbox. It takes about a half second to one second longer than a normal/unsandboxed Adobe Reader to open, but I can't really consider this excessively slow. What kind of a delay are you seeing?

Ok, I try to describe my procedure in a better way:
- Disable forced programs in Sandboxie.
- Open Adobe Reader, enter the settings dialog and activate the protected mode.
- Enable forced programs in Sandboxie.
- Open Windows Explorer and double-click the PDF file.

Now the forced Adobe Reader opens immediately in Sandboxie and on the taskbar. But it shows a white screen only and not the PDF document. It takes about 2 minutes before the PDF document shows up and the Reader works normal again. It seems that this only happens with protected/restricted PDF files, because all other PDF files show no delay.

(With the protected mode disabled this problem does not occur.)

The protected mode is on by default so I didn't have to do steps 1-3 but step 4 sounds like just about what I've done. Can you produce a Resource Access Monitor log for this step 4? It lists DLLs in use so that may point to some other software that plays a part in this.

http://www.sandboxie.com/index.php?ResourceAccessMonitor