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