Disable 'Display PDF in Browser' in Acrobat Pro XI Just got Acrobat Pro XI and can't figure out how to disable 'display pdf in browser' as I used to be able to do in Pro 8. I tried doing the 'Manage add-ons' in IE 8 tools, but did not change anything. Firefox has a built-in PDF viewer. We'll show you how to disable it and use another PDF viewer, like Adobe Reader, instead.

1. Adobe Reader Dc Disable Open Pdf In Browser
2. Adobe Acrobat Free Download
3. Adobe Reader Dc Disable Display Pdf In Browser
4. Disable Adobe Reader Open In Browser

We have a .NET C# application that makes use of the Adobe ActiveX Controls. For versions 7-10 of both Adobe Acrobat and Adobe Reader, to use this control you were required to turn on the 'Display PDF In Browser' setting. You could do this manually from the GUI using

or programmatically by setting the registry settings directly

Which follows the SDK reference http://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/Originals.html#BrowserIntegration. Our application has been using the programmatically setting of this registry value when our customers have versions 7-10 of Adobe Reader or Adobe Acrobat. The link above also indicates that this bBrowserIntegration registry key is deprecated in XI (11). The old registry path still exists in the new versions, i.e.:

however there is no longer a bBrowserIntegration key just as the documentation indicates, it is deprecated.

It does appear that the Adobe ActiveX Control still works just fine with XI and DC as long as Display PDF in Browser is enabled, as it always has.

For versions XI (11) and DC, there are two published links that clearly show how to achieve this manually:

When testing Adobe Reader DC, if we don't complete the steps to enable the Display PDF in Browser for a new customer installation, then our application will throw a COM error and then if we enable the setting following the instructions in the link above, everything works as expected with our application, it renders PDFs using the Adobe ActiveX Control, which is similar to what we expect to see in older versions (7-10) when the registry setting was not set (see my old post and my own solution back then How to diagnose cause, fix, or work around Adobe ActiveX / COM related error 0x80004005 progmatically?).

So, the question remains, what is the expected programmatic equivalent either for the manual process in XI or DC today or the equivalent to what worked in 7-10 by setting the registry setting bBrowserIntegration accordingly. We want to be able to turn it on and then reset it to the previous setting when our application ends (so our application doesn't force the user to keep the setting just because our application needs it) which is what we do today for 7-10.

I can't seem to find any references online for how to enable/disable browser integration from a developer standpoint so our application can continue to the use the ActiveX Control and not have the COM errors show up, forcing the user to change this manually.

The primary priority is to understand the solution for DC as this represents the new paradigm for Adobe Acrobat/Reader.

Adobe Reader Dc Disable Open Pdf In Browser

1 Answer

Have you considered the use of 'Registration free' scenario? It allows to use COM/ActiveX components in your application without registering the ActiveX globally and allows to load the isolated COM/ActiveX control for your application only based on the interfaces defined in the XML manifest included along with your application.

See this post for the list of tools and this post for sample XML manifest to use Flash plugin and this step by step guide. I assume that for Adobe Reader control you should use PDF.ocx from C:Program FilesAdobeAcrobat ReaderActiveX folder.

UPDATE (July 27 2015): In the latest versions of Adobe Reader they use AcroPDF.dll and moved it into Program FilesCommon FilesAdobeAcrobatActiveX as I've checked with Adobe Reader 11. Unfortunately AcroPDF.dll throws error when trying to install it using regsvr32.exe. I suppose it checks some additional keys before initializing to protect from non permitted use (until user unblocks the control in IE). Seems like there is not way officially and programmatically walk around the requirement for user to explicitly permit PDF control for use by non-Adobe apps.

Also see the discussion regarding possible issues on x64 platform: the better and more reliable way is to use Adobe Reader control indirectly by hosting IE’s WebBrowser control that will invoke the embedded PDF viewer control accordingly.

Not the answer you're looking for? Browse other questions tagged .netpdfcomadobeactivex or ask your own question.

You can open PDFs on a web page either within your web browser or in Acrobat or Reader. Find instructions specific to each browser below.

Note:

Each browser has its own settings to control how PDFs open from a web page. Acrobat and Acrobat Reader do not include a preference setting to open web-based PDFs. To change the display behavior, follow the instructions below for your browser, or see the browser documentation on how to control plug-ins or add-ons.

Open Internet Explorer, and choose Tools > Manage Add-ons.

Under Add-on Types, select Toolbars and Extensions.

Select All Add-ons from the Show menu in the Manage Add-ons dialog box.




Note:

If you do not see the Adobe PDF Reader add-on, try the other options on the menu. For example, on some systems, the add-on appears when you select Run Without Permission.

Click the Enable or Disable button (it toggles depending on the status of the selected add-on):

Enable sets the Adobe PDF Reader add-on to open PDFs in the browser.

Disable turns off the add-on so it does not open PDFs in the browser.

Select Adobe PDF Reader, and click the Enable/Disable button.




For more information, see the Internet Explorer help topic Manage add-ons in Internet Explorer.

Microsoft Windows 10 will ship with two browsers: Internet Explorer 11 and the new Edge browser.

The Edge browser will be the default browser, and Internet Explorer 11 will be available to support legacy workflows. The new Edge browser will not have any support for ActiveX plug-ins. Therefore, the Acrobat/Reader plug-in won't work with Edge. For more information, see Change in support for Acrobat and Reader plug-ins in modern web browsers.

Use Internet Explorer 11 to open PDFs. To enable the Acrobat/Reader plug-in in Internet Explorer, see the steps in the previous section.

The Acrobat/Reader plug-in for Mozilla Firefox is based on Netscape Plug-In API (NPAPI), which is supported only till Firefox version 51. With Firefox version 52, support for NPAPI plug-ins is removed, and hence the current Acrobat/Reader plug-in will not work.

The Acrobat/Reader plug-in for Google Chrome is based on the Netscape Plug-In API (NPAPI) technology. Google announced that in April 2015 NPAPI plug-in support would be disabled by default in the Google Chrome web browser, with an override capability for advanced users. In September 2015, NPAPI support in the Google Chrome web browser was removed entirely.

For more information, see Change in support for Acrobat and Reader plug-ins in modern web browsers.

Note:

The Acrobat/Reader plug-in for Apple Safari is based on Netscape Plug-In API (NPAPI), which is supported only till Safari version 11. In Safari 12, support for NPAPI plug-ins is removed, and hence the current Acrobat/Reader plug-in will not work.

To view PDFs with Safari, you can do one of the following:

• Set Safari preferences to use Adobe Reader plug-in
• Disable AdobePDFViewer plug-in to use the default Safari PDF viewer

In the Preferences window, choose Security and then click the Website Settings button for Internet plug-ins.


Now select Adobe Reader in the list of plug-ins.

Under the option When visiting other Websites, in the drop-down list, choose Allow Always and then click Done.


Note:

This will set the browser to use the Adobe Reader plug-in to view PDFs.

You must have root user privileges to change Safari plug-ins. To display PDFs using the Safari PDF viewer, you must disable the Adobe PDF Viewer.

Log in as the root user. The root user privileges aren't enabled by default because the root user can change system files. For more information and instructions, see one of the following Apple documents: Enabling and using the 'root' user in Mac OS X or OS X Mountain Lion: Enable and disable the root user.

Type /Library in the Go to the Folder field, and click Go.

Create a new folder in the Library folder, and name it Internet Plug-ins Disabled.

Open the Internet Plug-ins folder, and move both the AdobePDFViewer.plugin and the AdobePDFViewerNPAPI.plugin into the new Internet Plug-ins Disabled folder.

Note:

If both AdobePDFViewer plug-ins are still in the Internet Plug-ins folder, drag them now to the trash. You may be asked for your name and password.

For more information on disabling or removing plug-ins, see Apple Safari help.

Adobe Acrobat Free Download

Adobe Reader Dc Disable Display Pdf In Browser

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Disable Adobe Reader Open In Browser

Legal Notices | Online Privacy Policy