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.

107 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
  • Shaun commented  ·   ·  Report

    This is a major issue with OneDrive and SharePoint.

  • Peter Verginer commented  ·   ·  Report

    Its a pain working with sharepoint and onedrive sync and having to copy pdfs to the desktop to open them.
    We are also investigating moving to foxit only because of this everyday-problem!

  • Cristiano Rodrigues commented  ·   ·  Report

    Any updates on this @Vinod?

    We have clients on Adobe subscriptions that we'll move to Foxit if this doesn't get sorted soon.

  • Jim Kramer commented  ·   ·  Report

    For the money Adobe charges for Acrobat this should not be a "thing". Come on Adobe... get your act together.

    STILL NOT FIXED!!!!!

  • Jason Stuff commented  ·   ·  Report

    Kind of ridiculous at this point. "Currently reviewing"? How long does it take to review? Apparently 3+ years. It's not as simple as reducing file name length, many networks are locked into long file tree paths. More importantly, we shouldn't have to change file paths/lengths, this is an issue that should be fixed by Adobe.

  • Magnolia Xenia commented  ·   ·  Report

    Any updates regarding this request? It's been more than 2 years. This issue is still a headache for everyone in the business.

  • Anonymous commented  ·   ·  Report

    How is still a problem, you have has almost 2 years since the bug report regarding this issue was posted. Come on adobe, you are better than this

  • Anonymous commented  ·   ·  Report

    The issue continues to persist as I'm finding out after getting Adobe for my organization. Any update on the resolution?

  • Peter Verginer commented  ·   ·  Report

    Any progress on this? We have serious problems in the whole company because of this!

  • test commented  ·   ·  Report

    And ? You are still in progress ?????

  • nz commented  ·   ·  Report

    I don't think Adobe gives a rats *** about this issue. I'm paying $200 a yr subscription service for a **** software that a much cheaper version can take care of. Time to go with the competitor.

  • Anonymous commented  ·   ·  Report

    12 Months since you noted it as under review. Any updates yet?? This is insane!

  • 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.

← Previous 1