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.
We are currently reviewing the request for LongPath support and will update the thread.
Peter Verginer commented
Any progress on this? We have serious problems in the whole company because of this!
And ? You are still in progress ?????
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.
12 Months since you noted it as under review. Any updates yet?? This is insane!
long paths work fine with Free PDF-XChange Viewer
is there an update? in 2020 and this is still a dang issue.
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
For whatever absurd reason, Adobe Reader Touch does open long path files without a problem
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.
2. Disable Protected Mode in Adobe Reader DC.
Menu : Edit \ Preferences \ Security (Enhanced) - Untick Protected Mode.
Exit Adobe Reader for changes to take effect.
Definitely needed feature! Please implement using proper libraries to enable long path support.
Is adobe going to address this anytime this century?
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!
FoxIT PDF maybe.
Absolutely crazy this is an issue.
Does anyone know of a PDF software that supports long file paths?
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
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
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.
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.