Skip to main content
New Participant
October 6, 2020
Answered

"There was an error while opening this document. The path does not exist."

  • October 6, 2020
  • 14 replies
  • 184559 views

When double-clicking a PDF in Windows 10 File Explorer, Acrobat gives the above error message.  The same problem occurs when choosing "Open With..." from the context menu and choosing Adobe Acrobat.  Choosing "Open With..." using other applications such as Firefox or Chrome does not produce any error.  Choosing "Edit with Adobe Acrobat" from the context menu opens the file without error.  Opening the file from within Acrobat using File/Open does not give any error. The problem is recent, reproducible, and persisted after doing a repair installation of Acrobat.

Correct answer Ian219169983t0l

I had the same problem with Acrobat Pro DC (32-bit) in a dropbox folder. I fixed the problem by shortening the folder name.

14 replies

New Participant
July 6, 2025

That error usually shows up when Acrobat struggles to resolve file paths passed by Windows Explorer—especially if the path is too long, contains special characters, or uses odd formatting. Opening from within Acrobat works because it bypasses Explorer's path handoff.

 

To fix it:

  1. Clear Acrobat’s recent file cache:
    Go to Edit → Preferences → Documents → Clear Recent File List. This removes any corrupted temp links.
  2. Reassociate PDFs cleanly:
    In Windows Settings → Apps → Default apps, unassign then reassign Acrobat as the default PDF viewer.
  3. Test locally:
    Move the PDF to a local path like C:\Users\YourName\Documents to check if deep folder nesting is the issue.
  4. Run as Admin + Repair Again:
    Run Acrobat once as administrator, then use the repair function again to reset shell integration.
  5. Use Long Path Tool:
    If the file is buried under a deep directory structure (often >260 characters), Explorer won’t pass the full path cleanly to Acrobat. Long Path Tool can help detect, move, or rename these files safely — resolving the issue without editing the registry or guessing where things break.

 

Still stuck? Use Process Monitor to trace how the path is being passed from Explorer to Acrobat. It often confirms if the root cause is path depth or encoding.

New Participant
August 16, 2024

Hi Everyone, 

I have the same issue when opening PDF on sharepoint site, is there working fix for this issue.

 

The adobe version i am using Adobe Pro 2020 .

New Participant
August 7, 2024

This topic is old but it will be useful for those who come across it via Google. 
https://www.youtube.com/watch?v=MnKNR1qlX5s

New Participant
July 24, 2024

I HAVE A SOLUTION

File can't be accessed or deleted because the name is too long

So all you need to do is change the file name

Only Adobe can't access it so just use another program to change the name to something shorter and you'll be able to access/delete it

I used the free WPS Office program and used "Batch rename" to change the file names and they all worked like normal after that

Participating Frequently
June 6, 2024

Just use longpath tool, it is helpful. 

New Participant
December 1, 2022

Hi ,

I just resolved this for a user. This issue is caused by the 255bit limit placed by the windows file system. This needs to be adjusted in REGEDIT, to select the long option by changing a '0' to a '1'. Log into Regedit as an admin, Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem select LongPathsEnable, change the word value to '1', restart your computer and that should be it

New Participant
January 9, 2023

Nope, it still does not work. IS ADOBE's problem.

Amal.
Community Manager
Community Manager
January 10, 2023

Hi @Judithhhhh 

 

It's actually not a filename limit that is imposed by the operating system, but a path limit. Your path (that's all the directories plus your filename) can only be a certain length.

 

Please go through the correct answers marked in the similar discussion below:

https://community.adobe.com/t5/acrobat-discussions/acrobat-not-allowing-longer-file-names/m-p/13101483#M372727

https://answers.acrobatusers.com/Is-file-length-limit-Adobe-Acrobat-Pro-q191982.aspx

https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file

 

Regards

Amal

New Participant
July 20, 2022

The "answer" in unacceptable.  Cannot open or save any PDF's - pretty basic fuctions and renders acrobat useless if neither work.  Asking me to rename all of my files / download all pdfs on sharepoint to open them is not acceptable.  Also it's unable to save files on my desktop with spaces - truncates the name at the space and does not save in PDF format.  Was using acrobat cloud yesterday and it all worked just fine.  Now on the desktop version and nothing works.  Please help.

 

New Participant
August 9, 2022

I am still having this issue on Windows 11, 64x. Adobe PDF version 1.4. This error is a real significant nuisance. Given the number of pdf documents I work with (hundreds per day), it's requiring me to rename and deal with this error at least 20% of the time. Please help/fix, adobe. 

Ian219169983t0lCorrect answer
New Participant
November 24, 2021

I had the same problem with Acrobat Pro DC (32-bit) in a dropbox folder. I fixed the problem by shortening the folder name.

New Participant
October 18, 2021

I have the same problems. Works in download folder, does not work in Dropbox folder. I can open the file in Chrome without problems. 

Acrobat Reader version is 2021.007.20099

Amal.
Community Manager
Community Manager
October 29, 2021

Hi there

 

We are sorry to hear that. Please check out the MS help page i have found and see if that works, as it seems to be some issue with MS https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#enable-long-paths-in-windows-10-version-1607-and-later

 

Regards

Amal

New Participant
October 29, 2021

This is the 21st century, Adobe! this is a problem one would expect from the old days of DOS. Get with it Adobe, this really isn't rocket science. If Windows allows a folder / file specification, your product which is supposed to the gold standard should take it. People are telling you that they can't open files because Adobe can't handled the directory / file name. That's an Adobe problem and your support keeps saying "look over there .. ". The problem is not over there. It's ADOBE

Inspiring
September 19, 2021

Well windows 10 long path support is needed.

New Participant
October 28, 2021

Yeah, I mean it's pretty clear this is a bug .. Adobe, just FIX IT. Pretty straightforward.