I'm having some problems with Adobe Reader X under Windows 7 and it seems that I need to disable protected mode. I disabled it by unchecking the related option in edit-preferences, also I created the registry key for the local user (bProtectedMode = 0).
After doing that, the protected mode seems to be disables when I open pdf documents with Reader X, but it's still enabled when previewing documents thumbnails in windows explorer. The issue is that when I open a folder containing pdf files and left click or right click them, two AcroRd32.exe processes spawn and it seems to me that it's a protected mode behaviour (broker process + sandboxed renderer process).
I'd like to know if it's possible to fully disable protected mode so that it remains disabled even when I'm navigating directories with Windows Explorer and documents are previewed. My current Adobe Reader version is 10.1.3.
Thank you very much.
I tried restarging the app and rebooting the system after disabling the protected mode, but the problem persists.
If I open a pdf document by double clicking it, it's opened without protected mode. If I just left click or right click it in the Windows Explorer, two reader processes are raised and the behaviour is the same as if protected mode was enabled. I believe the document is opened by Reader X to preview the document and display its thumbnail.
Maybe it's just not possible to fully disable it, but I was hoping that someone could confirm or deny it. This is very easy to reproduce.
Thank you anyway.
Here's a statement that hopefully helps or at least solves your mystery:
While Protected Mode can be disabled for PDFs viewed with the product, Adobe continues to protect you when 3rd party software invokes a Reader process; that is, Protected Mode sandboxing cannot be disabled for shell extensions. For example, when you use Windows Explorer to preview a PDF in the Preview Pane, it starts a Reader process to display the preview. In such cases, Task Manager shows that two AcroRd32.exe processes spawn and that the operation is occurring with Protected Mode enabled.