Skip to main content
E
elisaw
Participant
October 5, 2010
Answered

This file is set to be launched by the PDF File. This is currently disallowed by you system administ

  • October 5, 2010
  • 6 replies
  • 42379 views

After an adobe update I'm having this problem suddenly:

This file is set to be launched by the PDF File. This is currently disallowed by you system administrator.


How do I fix this? Can someone help ?????

    This topic has been closed for replies.
    Correct answer moameen

    An easy fix is under the edit tab, go to preferences and security(enhanced) category. Add the folder path or file you wish to open via the pdf document and then click ok. It should work now. You can also disable enhanced security so that you would not have to specify trusted locations, I think.

    6 replies

    F
    freds9283053
    Participant
    May 3, 2015

    Hi.

    One work around:

    • Upload your source document, ie Word.doc into Google Docs.
    • Within Google Docs open the document and insert your link.
    • Click -> File -> Download as -> PDF document.
    • Open the downloaded PDF file from your desktop.
    • Click on your link - works fine.

    Its a phaf, but one way round the problem.

    K.Daube
    Community Expert
    K.DaubeCommunity Expert
    Community Expert
    August 2, 2023

    The problem stroke again on Windows 11. Links in a PDF did not work any more - so I applied the following what was proposed in this thread:

    Regedit: HKLM\SOFTWARE\Policies\Adobe\Adobe Acrobat\2017\FeatureLockDown\cDefaultLaunchAttachmentPerms

    Key: tBuiltInPermList.

    Value: contains a long list of extendsion including the problematic one (.ini in my case):

    version:1|.ade:3|.adp:3|.app:3|.arc:3|.arj:3|.asp:3|.bas:3|.bat:3|.bz:3|.bz2:3|.cab:3|.chm:3|.class:3|.cmd:3|.com:3|.command:3|.cpl:3|.crt:3|.csh:3|.desktop:3|.dll:3|.exe:3|.fxp:3|.gz:3|.hex:3|.hlp:3|.hqx:3|.hta:3|.inf:3|.ini:3|.ins:3|.isp:3|.its:3|.job:3|.js:3|.jse:3|...

    Replace the :3 by :2

    |.ini:2|

    A brute force method would be to rename the key to !_tBuiltInPermList ...

    Now if you click on a link to such a file (D:\System_ddd\DDDcontrol.ini), you get a message, which you can avoid in the future:

    Use the Open button...

    J
    jmkolb
    Participant
    January 30, 2012

    A Fix that worked for me: Hopefully you to!

    If you go into the registry (regedit) and look under hkey_LOCAL_MACHINE - Software -  Policies - Adobe - Acrobat (which ever version you have) - (version Number) - FeatureLockDown and then in cDefaultLaunchAttachmentPerms you will see the registry key tBuiltInPermList. You can edit the data in that field to open which ever type of file extension you may have a link for.

    For Example: I had someone who coudlent open a .txt file. So i went in and added |.txt:2 to the list (the | is the shift \). i am not sure what the 2 really means but it then gave me the are you sure you want to open the file and i clicked okay and it went through fine. I tried putting a 3 instead of a 2 but that didnt allow for it to open.

    I hope this helps everyone who has been having this issue. i found many pages saying there was a registry fix for this but untill i went through myself i have yet to see them. Let me know if this works for you also

    J
    JL-Padua
    Participant
    March 5, 2012

    Thanks jmkolb! It worked for me. I remove ".exe:3|" from the string and now I can run .exe from within ,pdf files.
    I used Adobe Reader X v10.1.2

    T
    tomhix
    Participating Frequently
    February 11, 2011

    I, too, depended on this functionality and have not been able to disable it.  I'm trying to launch a web URL to an ASPX page.  Does anyone have a way to defeat this so-called feature?  Something that worked well now is a liability.

    Any help is appreciated.

    E
    elisawAuthor
    Participant
    February 12, 2011

    I simply started using Foxit instead.

    T
    tomhix
    Participating Frequently
    February 12, 2011

    You cannot access Geopdf capabilities with Foxit.

    T
    tmkilani
    Participant
    January 12, 2011

    Guys, the solution is as that simple.. Trash this stupid ass Adobe Reader and download a respected pdf software.. Foxit Reader, Believe me this is the best solution

      ~graffiti
      ~graffiti
      Legend
      January 12, 2011

      Foxit is fine as long as you don't want the ability to use static and dynamic forms, reflow, read-out-loud, digital signatures,  strong encryption, rights management, redaction, geo-spatial tagging, 3D  rendering, Flash, collaboration, reviews, and portfolios.

      There's more but I'm tired of typing...

      E
      elisawAuthor
      Participant
      January 12, 2011

      I've been using Foxit instead of adobe reader since I started having

      problems and I am happy with it..

      A
      Adobe Employee
      Ankit_Jain
      Adobe Employee
      October 19, 2010

      Hi,

      This is a deliberate fix by Adobe to prevent your system from being vulnerable to security attacks. Hence, any link that tries opening any executable file has been blocked with the error message you just mentioned.

      The following links have more details on the same:

      http://news.softpedia.com/news/Adobe-Finally-Fixes-Launch-Bug-145757.shtml

      http://www.adobe.com/support/security/bulletins/apsb10-15.html

      Ankit

      A
      Anonymous
      November 24, 2010

      So what can we do about this?  I work at an international school where there are PDF "books" that include examples that are launched by clicking a link.  These links now fail, and I do not know how to enable the launch feature. The message states that "This is currently disallowed by your system administrator", who happens to be me.  Teachers are blaming me for the loss of functionality, and I need to know how to re-enable it.

        AbhigyanModi
        Community Manager
        AbhigyanModiCommunity Manager
        Community Manager
        November 24, 2010

        What kind of files does the PDF point to?

        W
        Write_U_R
        Participant
        October 18, 2010

        I would venture to guess - having discovered last week that our help document's once-working links to some departmental folders no longer seem to work - that you are running Reader 9.3.3 or newer.

        Apparently a change was made to Reader to prevent a link to an executable and who knows what else.

        But my links merely take internal users to an internal folder, and not to executables or other specific files.

        So why they stopped working is a mystery to me. 

        I also don't understand why I can't seem to use Enhanced Security --> Privileged Locations to get around this by setting trusted sites, but so far, no luck.

        Maybe someone else can elaborate on this.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices