Links in PDF stop working after updating to Reader 11.0.11

[CJMartin249]

After updating to Adobe Reader 11.0.11, links in PDF files we have stored on SharePoint that link to other PDFs on SharePoint no longer work. There is no error. Nothing happens when clicking on them. This is a serious issue, as these documents link device and parts information. We have to roll back to 11.0.10 to restore functionality.

[Rave]

Hi Christopher,

Thank you for reporting this issue.

I will check at my end and get back to you.

Regards,

Rave

[kip_jaxxon]

Please also see similar issues reported here:

Since upgrading to 11.0.11, relative cross document links while viewing PDF in the browser are no lo...

destination links not working in acrobat pro 11.0.11 when viewed within a web browser (firefox; inte...

[Rave]

Hi,

This browser workflow has been purposely blocked because of security bug.

We allow destination that starts with http: or https. Also if the path is a platform path (non-string) we block it.

We are investigating more on it. I will keep you updated on the same.

Regards,

Rave

[CAIDave]

Rave

We are experiencing the same issue.

We use FrameMaker to generate 100's of PDF files every day. FrameMaker creates PDF GoToR and GoTo links (via Postscript/Distiller) with named destinations (e.g. G143567) for our links. We have over 500,000 files (created over the last 15 years) with these types of links in them and this latest patch to Acrobat X and XI has broken all of the GoToR links on our web site. We can't really use URI links because the PDF files are used both on the web and offline.

I didn't understand where you would put the HTTP or HTTPS in a GoToR link that would get past this blocking. And would that then just start acting like a URI link which we can't use?

It also isn't reasonable for us to go and change all of these 500,000 files because they are encrypted and not allowed to be changed after they are published to the web.

Thanks

[dand97702251]

I didn't see this anywhere in the release notes or documentation.  I also looked in known issues and didn't see this mentioned.

Perhaps I missed something?  Is this acknowledged as something adobe will fix or what?  Lack of communication is not helpful.

Anyways, we are affected by this issue as well.  For the time being we have had to roll back clients to 11.0.10.  So hopefully this will be resolved soon?

[Rave · Accepted solution]

Hi Dan,

Please try creating the following registry entry and set its value to 0 and check if it works for you.

For 11.X

Reader:

HKLM\Software\Adobe\Acrobat Reader\11.0\FeatureState\3836780

Acrobat:

HKLM\Software\Adobe\Adobe Acrobat\11.0\FeatureState\3836780

Disclaimer: The registry contains system-related information that is critical to your computer and applications. Before modifying the registry, be sure to make a backup copy of it (Windows 7,Windows Vista). Adobe doesn't provide support for problems that can arise from improperly modifying the registry. Adobe strongly recommends that you have experience editing system files before you modify the registry. For information on the Windows Registry Editor, see the documentation for Windows or contact Microsoft Technical Support.

Regards,

Rave

[jconnorton]

We are also having this issue. Basically it breaks access to detail information on our website, going into hundreds of PCs and editing the registry is not an option. Is a fix coming soon ?

[CJMartin249]

The registry FeatureState value has not resolved the issue. The linked documents are still not opening. A couple other things we have determined.

If we open the PDF files in Adobe Reader directly, the hyperlinks to the other PDF documents do open. The issue is only observed when viewing the PDF files in Internet Explorer/Reader plugin.

I'm not sure if it matters, but the documents were created with BlueBeam Revu 2015 eXtreme.

Chris

[jimob77]

Rave wrote:

We allow destination that starts with http: or https. Also if the path is a platform path (non-string) we block it.

Rave, we have an internal server that hosts all of the documents and guidelines for our company. This server uses a proprietary protocol pw:\\ and we need our PDFs to be able to link to documents on this server. I used to be able to launch these types of links in a PDF by reversing the slashes (as pw://) but now Acrobat 11 will not launch any of our server links!!! Rather, it just brings up an empty browser window now...

This is a HUGE impact to our organization as this server is a critical central repository for us! How can I get this to work without going into the registry and modifying code strings?? Certainly I cannot instruct over 3,000 people to do this in order to make PDF links work, as that is both unsustainable and also a security risk in itself sending a bunch of people into their registries!!!

[Guest]

Use something like FlexPaper if you would like the links to work in all cases. Adobe Reader was never meant as a way of browsing PDFs online anyhow. Have a look here:

FlexPaper - The web pdf viewer solution

[dan_aka_jack]

On Linux (Ubuntu 15.10), using acroread 9.5.5, I could not open web links (which all start with http:// or https://) from PDF docs.  I tried control-clicking but no joy.

I found I could make web links work by going to Edit -> Preferences -> Trust Manager -> "Internet Access from PDF Files outside the browser" -> "Change Settings".  Then change the setting to "Allow all web sites".  I can now open web links from PDF files.   Opening web links only works in firefox, not google-chrome (you set the browser in Preferences -> Internet -> Select Browser -> Browser Executable).

[FrySteven]

I work for a large fortune 500 company having the same issue.  All relative pdf-to-pdf links are not working inside any web browser since the May security update to Reader X, XI and DC.  We too have hundreds-of-thousands of pdf files created over the years that have relative pdf-to-pdf links.  The links work within the stand-alone acrobat program, but not through a browser running the acrobat plug-in.  We have used relative pdf-to-pdf links for years.  That way we can deliver the files on CD-ROM, intranet or the internet as long as the files stay in the same folder relative to one another.  This issue is causing huge ramifications for our company.  The pdf-to-pdf links were all created using Adobe Acrobat Pro 7, 8, 9 & 10 and have worked wonderfully through web browsers for years. All of our employees access the files through the intranet using a web browser.  Anyone with the security update is unable to access the links.  I don’t think it is reasonable or acceptable to have 20,000+ employees role back to the pre-security update version.  Our IT department has been working on the registry “fix” suggested, but the unofficial “fix” has been unsuccessful for us so far. I also don’t think it is reasonable or acceptable to disallow this feature without giving an option to turn the new security feature on/off within the reader plug-in.  Give us a check box and a warning about the security risks if you need to, but please allow this feature. 

[FrySteven]

Update June 25, 2015:

  It appears that the Adobe May (2015) update to X, XI and DC changed the acrobat.dll and some files in the plug_ins folder.  We are running Abobe Acrobat Pro X.  We tried substituting a working acrobat.dll and the plug_ins folder from a working copy (not updated) of Acrobat 10.  This change allows pdf-to-pdf links to work in the Internet Explorer browser with the updated version of Acrobat X Pro, but it is unstable.  This is definitely a problem/feature that adobe has coded into their dll files/software.  What I don’t understand is that all of our pdf-to-pdf links were created using Adobe’s Acrobat Pro with the linking tool.  The Adobe software made the relative links, but now Adobe has decided that relative pdf-to-pdf links made with their own software are no longer allowed inside a web browser.

[FrySteven]

Rave/Adobe Staff,

What is the status of this issue?  Please advise.

[FrySteven]

Rave/Adobe Staff,

Is there a phone number I can use to get a live person who will answer my questions?

[AdriàAdell]

Here is the solution:

Since upgrading to 11.0.11, relative cross document links while viewing PDF in the browser are no lo...

[donovandragon]

This is a major reason why we use PDFs. This is huge. The fact nobody has addressed this issue shows Adobe doesn't care. Why? Is it considered a security issue to click on a hyperlink in a PDF? I bet somebody got freaked out about it. Adobe was doing so good. They had a highly useful product and now they are cutting it off at the knees. SNAFU

[ericcaS84]

Is there a fix for version DC (15?)

[brucea51118126]

Folks,

Have tried the registry changes - to no avail.

Is there a version of Reader that will allow internal links (to other parts of same file) to function?

This featured used to work, but now it doesn't.

Either need a functional Acrobat Reader product or will need to look to non-Adobe solutions.

Any help/assistance will be much appreciated.

Bruce

[AnandSri]

Hello Bruce,

We apologize for the inconvenience caused, as per the description above, the links to PDF is not working, Is that correct?

What is the version of the Adobe Reader is installed? to identify refer to Identify the product and its version for Acrobat and Reader DC

What it the version of the operating system installed? Is these PDFs are saved on SharePoint or any network drive or local drive?

is it specific to one PDF or with all the PDF files?

Make sure that you have the latest version of Adobe Reader installed, check for any pending updates of Adobe Reader from help>check for updates, reboot the machine after updating Adobe Reader and see if this brings any difference.

let us know how it goes and share your findings.

Regards,

Anand Sri.