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

[Bruce5FB0]

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.

[RLDenney]

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

[Thomas Bødtker15C2]

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

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

Regards

Amal

[RLDenney]

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

[Adam L2]

This is excalty correct. I just had this happen to me. Never had an issues until today. This is all on Adobe.

[Neal23279516rq1l]

This is still ongoing and its still only Adobe documents at the root cause. All other documents are fine. This really needs sorting. It's not a Microsoft issue, its Acrobat failing to open the file correctly when there are long folder extentions.

[Ian219169983t0l · Accepted solution]

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

[Charles25324682pjhh]

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.

[Mitchell25585644i19k]

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. 

[n303n]

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

[Judithhhhh]

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

[Amal.]

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

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

[sheril29837924]

b.s. - shortening the file name fixed the problem

[Theta28825504ay96]

I found the origin of problem. It is in the certain characters you use in the system path that leads to the PDF, not the name of the PDF itself. I am from Croatia and have used croatian letter "Đ" in the path name. When moving from Dropbox to OneDrive our entire company files one of our computers in the company was using Win 10. Others were using Win 7 and Win 11. The one with the Win 10 had an issue with letter "Đ" upwards in the path that leads to the PDFs that did not want to open. Other letters were an issue too.
I did the LongPathsEnabled hack, it did not work. Other files were opening fine, even deeper inside the structure so it was a real puzzle. ONLY PDFs have this problem. 
Rename the folders that lead to the folder that contains the PDFs.
Copy one PDF upwards in the structure until you can open it. Look at the folder it came from and remove any non-english or special characters and then copy the PDF again inside the folder and see if it works. Try renaming the folder name and PDF name until you figure out what the problematic character is messing Acrobat reader.
Why this happens I don't know, but to me it only happens on Win 10 and when Acrobat Reader and OneDrive come together.