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?

[_Spiros_]

I have DC Pro. April 2024 and it still appears that Acrobat has issues resolving/opening/processing pdf files with long path names, (specifically in network locations). I have to copy files to local or short network folder to be able to process files. I was not able to combine files, or run a batch actions. This is unacceptable for a premium product.

[qs104]

I have the same issues here. Is there any other ways to solve this?

[Rickey36552389i3yy]

LongPath files are too irritating - the errors that come with them just get on my nerve  - so  I started using LongPath Tool. It is effective. 

[Ana36766357xsrx]

I researched a lot, read every article but was not able to find anything. Recently, I downloaded the Long Path Tool and it has helped me, it has some issues but that can be overlooked. 

[andij14]

It's 2024 and this is still an issue for me with Adobe Acrobat Pro. There are no updates available, I'm at the latest version.

[mojtaba342775741tqc]

same issue here

[Martin36362310x29j]

Hey, did you try the tool? 

[gordons66548100]

Still having issue on the LongPath files - July 2024

[Patryk33964463512m]

Still having the same problem, and note that it's definitely Adobe since the file can be opened in Chrome or any other app just fine.

[Jeremiah5EA7]

Still having the same issue.  Beyond frustrated with Adobe at this point. 

[naomielvira]

I also have the same problem which happened exactly after downloading Acrobat Reader.... It is absurd that now over 2 years later nothing has been done about this problem.

[Meenakshi Negi]

Hi naomielvira,

Thank you for reaching out, and sorry about the delay in response.

Please ensure that the application is updated to the latest version. In Acrobat Reader, go to Menu > Help > Check for updates. For more information, refer to the following help document: https://adobe.ly/4i38ItH. 

If you still get the same error, please let us know where the file is saved and how you are opening the document.

Thanks,

Meenakshi

[carl_6430]

Wow we wait for updates for years and then the replsponse is check for updates!!!

#notascoobydo

[enqu!re]

It is now 2025.  I am using Acrobat Reader 24.005.20320 and no updates available…

It is a long way from the 8+3 limits on file names, hurrah!  As I understand it, the soft-limit on path length in Windows 11 is 250 characters.  The path length for the PDF I wish to open was close to that limit (but still under).  In deference to Acrobat, I re-jigged the directory structure and now the path + file length is 183 characters (206 characters including spaces) – so well under the 250 character limit. Yet, still the problem persists…  How come?  If and when this annoying bug be fixed?!?
~~

[reece_1244]

Can I add that with O365, which is becoming standard for companies who are also Adobe's main customers, long path's are implemented by the IT teams. This is becoming common practice and users have no control of this. As such, the lack of supportability is going to drive customers away to find other alternatives. If you can't open a file, you're pretty stuffed, or save where you need to. Workarounds are time consuming and user's patience is not what is was, please review and support ASAP!

Thank you. 

[Bobleponge]

I concur. Sharepoint seems to love long paths & Acrobat still hates them. This is the longest-running nightmare ever.

[sally_8191]

You're absolutely right — Windows 10 has supported long file paths since the 1607 update (with LongPathsEnabled set to 1), and many apps, including Microsoft Office, now handle extended paths just fine.

Unfortunately, Adobe Acrobat DC and Reader DC still rely on older APIs that respect the legacy MAX_PATH (260-character) limit. That’s why you’re seeing files fail to open or load as blank when stored in deeply nested directories — even though the OS supports it.

In the meantime, one effective workaround we’ve used is LongPathTool. It helps locate, manage, and open long-path files that Acrobat struggles with. We use it to temporarily move or rename files to a shorter path before viewing. It's not a permanent fix, but it avoids breaking workflows while waiting on Adobe to modernize path handling.

Hope Adobe acknowledges and updates their path support soon — this is becoming increasingly critical in enterprise environments.

[BRossow]

We're running into the same issue with the current version of Acrobat (yes, all updates installed). I'm working around it by mapping some of the deeply nested SharePoint folders to drive letters, but seriously? This needs to be fixed. Shouldn't have to navigate to different drives to open and save documents.

[Tariq Ahmad]

Hello, 

Sorry for the troubled experience. 
A bug has been logged for this issue. If the product team requires any further information to triage this issue we will keep this discuss updated. 

Thank you for your patience and support. 

Best regards,
Tariq | Adobe Community Team

[BRossow · Accepted solution]

Actually ... enabling long file paths in the Windows registry fixed the issue. It was enabled on the computer I was referencing which should have been identical to the one having the issue, but it wasn't. Would delete my comment above if I could. Sorry for the false alarm.

[Carl039]

@tariq can you share the link where we can track progress of this bug report?

Having waited 5+ years I have my reservations the fix won't be quick. 

[Tariq Ahmad]

Hi @Carl33217513vw80, 

I can share a bug number; however, that is not publicly accessible. 

Also, this issue was primarily caused by the OS side and can now be seen with Acrobat, but in certain areas only. On the OS side, Microsoft has provided the registry. 

If you want to know the progress of the bug in the future, you can private message me. To send a private message, click on the envelope icon in the top right corner.  

Best regards,
Tariq | Adobe Community Team

[Carl039]

@tariq, this is a long standing issue and although enabling LongPathsEnabled in the registry can help a little the problem still reoccurs when the likes of Foxit PDF opens the same file without issue. 

[Tariq Ahmad]

I understand. As I mentioned, product engineering has opened the bug. I will contact you if we need any help in triaging or reproducing this issue. 

Thank you for your patience and support.

Best regards,
Tariq | Adobe Community Team