Skip to content
← Acrobat for Windows and Mac

Feature request / Bug report

Acrobat for Windows and Mac: Other

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Add proper LongPath support

Adobe fails to open files when a file path & name exceed MAX_PATH. Windows no longer has a hard path character limit if the LongPathsEnabled key is set in the registry. See https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file#maximum-path-length-limitation

Modern applications are adopting this new standard with the mentioned file management hooks provided by the OS.

Adobe is falling behind in this regard. Please add proper Long Path support.

114 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Sam shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • asdf commented  ·   ·  Report

    long paths work fine with Free PDF-XChange Viewer

  • SHaun commented  ·   ·  Report

    is there an update? in 2020 and this is still a dang issue.

  • Anonymous commented  ·   ·  Report

    I could not believe that adobe does not have compatibility with this.... It sould like really easy to fix! And it is still under reviewing (facepalm)...

    The only solution is to disable the startup protection...

  • Benjamin Groves commented  ·   ·  Report

    For whatever absurd reason, Adobe Reader Touch does open long path files without a problem

  • Carl commented  ·   ·  Report

    I have found partial workaround (Requires Windows 10)
    Solves part of my issue with long paths in OneDrive synced folders. At least now I can get to the pdf although I now get this message to which I just choose skip to: The source and destination filenames are the same.

    Be interested to know if below fixes the issue for others?

    1. Enabled long path support in Windows and reboot.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
    LongPathsEnabled=1

    2. Disable Protected Mode in Adobe Reader DC.
    Menu : Edit \ Preferences \ Security (Enhanced) - Untick Protected Mode.
    Exit Adobe Reader for changes to take effect.

  • Anonymous commented  ·   ·  Report

    Definitely needed feature! Please implement using proper libraries to enable long path support.

  • nz commented  ·   ·  Report

    Is adobe going to address this anytime this century?

  • Anonymous commented  ·   ·  Report

    You just lost a customer to Foxit! This issue should have been fixed last millenium! Novell NetWare had long path support since the '90's!

  • Carl commented  ·   ·  Report

    FoxIT PDF maybe.

  • Anonymous commented  ·   ·  Report

    Absolutely crazy this is an issue.

    Does anyone know of a PDF software that supports long file paths?

  • Zoli commented  ·   ·  Report

    Adobe is playing sleeping beauty. It shouldn't be an issue handling long paths in 2020, unless you got stuck in the last century. Adobe is still scrambling to get its acts together although Windows enabled long path support years ago.

    Lucky there are others who moved on from the NT era.

  • Anthony McGlin commented  ·   ·  Report

    Any update on this? It's starting to cause a lot of errors using SharePoint. Sure would save a lot of support calls.

  • Tim Gahnström commented  ·   ·  Report

    Are there any updates on this? Every day it is causing extra administrative work in our organisation.
    Storing documents in sharepoint and not beeing able to open them and sign them in adobe reader doe to long path names is most unfortunate.

  • Martin commented  ·   ·  Report

    I just had a Client call me about this issue, they were about to uproot and change their entire naming and structure scheme because of this.

2 Next →