Skip to main content
Participant
January 19, 2016
Answered

Adobe Reader Default PDF Handler Process

  • January 19, 2016
  • 2 replies
  • 2865 views

We currently use Adobe Reader XI in a Windows 7 environment but have been recently rolling out Nuance PowerPDF to supplement it. Adobe Reader XI always remains the default however some websites have had issues- we've found the solution is to open Adobe Reader, select Edit -> Preference, General and click Select Default PDF Handler. This fixes our issue by running an installer and possibly correcting whatever files were modified by PowerPDF, even though PowerPDF was never set as the default.

The problem is we need to do for over 900 users in multiple offices. Is there a command or automated way to run this process through group policy or a script? It's not as simple as just selecting a default file association, it needs to run that exactly process of whatever clicking "Select Default PDF Handler" does. Thanks!

This topic has been closed for replies.
Correct answer BChalfin

While comparing the registry of the PowerPDF install vs the Default PDF Handler process I believe I was able to find the solution to the issue- it is the result of the PowerPDF install deleting a registry key.

With Adobe XI installed, prior to PowerPDF, the following key exists:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf

It contains the following strings:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf\Extension: ".pdf"

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf\CLSID: "{CA8A9780-280D-11CF-A24D-444553540000}"

During the PowerPDF install I confirmed the entire key for HKLM\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf is deleted even though PowerPDF is set not to be the default in their customization wizard. I was able to see that running the Adobe "Select Default PDF Handler" adds it back, fixing the issue. Thankfully adding registry keys back are an easy fix.

2 replies

BChalfinAuthorCorrect answer
Participant
February 15, 2016

While comparing the registry of the PowerPDF install vs the Default PDF Handler process I believe I was able to find the solution to the issue- it is the result of the PowerPDF install deleting a registry key.

With Adobe XI installed, prior to PowerPDF, the following key exists:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf

It contains the following strings:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf\Extension: ".pdf"

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf\CLSID: "{CA8A9780-280D-11CF-A24D-444553540000}"

During the PowerPDF install I confirmed the entire key for HKLM\SOFTWARE\Classes\MIME\Database\Content Type\application/pdf is deleted even though PowerPDF is set not to be the default in their customization wizard. I was able to see that running the Adobe "Select Default PDF Handler" adds it back, fixing the issue. Thankfully adding registry keys back are an easy fix.

Participating Frequently
January 20, 2016

Can you test using the below command line? I think this would work for you.

msiexec /i <Put Reader Product code OR Full path to Reader MSI file> REINSTALL=”ReaderBrowserIntegration,ReaderPDFIntegration” DEFAULT_VERB="Read” IW_DEFAULT_VERB="Read” /qn

If you want a progress bar kind of UI then use /qb instead of /qn.

BChalfinAuthor
Participant
January 26, 2016

Hi,

I've been testing this over the last week however it doesn't solve the issue for everyone. I thought we had it as it seemed to work for some but there were many cases it didn't correct it. The only thing that works every time is when I go through Adobe Reader and click "Select Default PDF Handler". Does anyone know exactly what process runs when you click this? If I can find out the exact function of the button (everything it's checking for or modifying) we can probably figure out a way to deploy it

Thanks!

Bri