Acrobat Reader DC long file path

[Guest]

As an organization, we are using Windows 10 with the "LongPathsEnabled" registry entry set to 1, as posted here: Enable Long Paths in Windows 10, Version 1607, and Later 

This has helped us with moving long pathed files and opening them in Microsoft Office programs.

However, Adobe Acrobat DC (and Acrobat Reader DC) still cannot open files with paths longer than 255 characters. We have tested this in multiple scenarios and have found that Acrobat has this problem with any long file path. The file simply won't open or opens a blank document. If you copy the document to a short path, it opens flawlessly.

I have found several similar threads here , here and here . All mention it's a file path limitation of Windows. That is simply no longer the case. As seen in the top link, Windows 10 now supports file paths up to 32,767 characters. 

As linked in this thread here , user avn1 has correctly deduced that Adobe has not updated Acrobat to recognize the new MAX_PATH restrictions. That thread has several more responses but none from Adobe employees.

Could you please advise when Adobe plans to add long file path functionality to Acrobat products? Or at least acknowledge that you are working on it, please?

[ryszard_7560]

Hope it will be fixed soon at least. I would like to add sth from me - NTFS system has supported longer filenames from the very beginning, problem lied only in Windows Api. I know that Microsoft patched the issue even for Windows 7, and I would risk to say that even XP SP3 with additional fix had no issue to operate on files which paths were longer than 259 character.

As for Adobe Reader DC - this issue appears only if You try to open pdf file with double click from explorer window. Reader has no issue to open such files opened directly in Reader. Or in windows explorer, You must no double click the pdf file but right click and choose "open with adobe" option. Then Adobe Reader will open it without problems.

[BRossow]

Could everyone kindly quit referring to LongPathTool as a solution? It's a third-party workaround, and even that is dependent on your organization's policies allowing it to be installed, which many (like mine) won't without a full legal and security review. The solution is for Adobe to fix their software.