Skip to main content
Participating Frequently
August 17, 2017
Question

Disable File Locking in Acrobat (Windows)

  • August 17, 2017
  • 6 replies
  • 11804 views

One of the most frustrating issues I have with Acrobat is that it always locks files it opens, even if I am only viewing (not editing).  Is there a way to disable file locking?  If not, it would be extremely helpful if Acrobat only locked files when in  "edit" mode or not at all.

The situation frequently arises where an application is outputting PDFs, the PDFs open automatically in Acrobat, but if we want to overwrite a file, we have to close it in Acrobat first. Working between applications, this locking can be very confusing for users.  Most PC applications do not lock files in this way - it is up to the user.

Thanks!

-Donald Newlands

This topic has been closed for replies.

6 replies

Participant
September 17, 2024

This is old but still and issue on Windows 11. I use a little program called Lock Hunter to fix the issue with files/folders that won't move/delete on windows. Works everytime!

Participant
May 31, 2024

What if i forgot my password to unlock pdf file. how can i get password to unlock

 

 

Amal.
Community Manager
Community Manager
June 13, 2024

Hi there

 

Hope you are doing well and thanks for reaching out.

 

Adobe does not store the user's password to open the PDF file. The best way would be to recreate the PDF file from the original source file.

 

~Amal

Participant
July 12, 2023

Gee Donald, you'd think that five years would have been sufficient time for Adobe to fix their issue. However, I guess they have been too busy complicating the functionality of the application, making it even less intuitive and more non-Windows compliant. Good luck trying to use the "New Adobe" that they will "upgrade" you to without your consent. They have even taken away the ability to create Text Boxes. It's sad when knock-off programs outperform the original product. Why pay for a product when the free one does a better job?

Participant
June 14, 2021

One item that I have noticed that is causing the "File Lock" problem, and also a folder lock issue, is the Adobe Collaboration Synchronizer background process. This process starts up anytime Adobe Acrobat is run and locks files and/or folders even if the file is use is no longer open or if Adobe Acrobat is shutdown. I've had to keep Task Manager open if doing repetitve tasks involving Acrobat so as to quickly shutdown the service and move/delete the specificed file or folder. Adobe needs to address this latent locking issue; there are times that the file or folder being affected are never released (unlocked) so as to permit moving or deleting of said file or folder. I've attached a pic of the tasks that are active that need to be shutdown (yellow highlights).

Participant
June 14, 2021

[Update] I've also found that the process Adobe AcroCEF locks files and/or folders. This, too, needs to be shutdown if trying to delete a file or folder that remains locked after Acrobat is closed. Picture of highlighted process to close is attached.

N J A
Participating Frequently
March 24, 2021

The fundamental issue with Acrobat (and its associated processes), which has been present for many years, is that it does not correctly release file locks once a file has been closed. For example, generate a PDF file from any software and open it in Acrobat. Close it in Acrobat, try to rewrite that PDF, and your software tells you the file cannot be rewritten as it is already open, but it is NOT! However, go to Windows Resource Monitor's "Associated Handles" area, search for your PDF filename, and every time it is Adobe processes that are still holding the file open, even though you closed it. The only solution is to kill these processes in Task Manager, or close Acrobat altogether, every time you want to rewrite the PDF file! This is truly amateur and fundamentally bad file handling by Acrobat and its associated processes. It is the only software I have ever used that exhibits this serious error, and over many years as a technical writer it has plagued my productivity at the most critical times. Adobe: please listen and fix your badly written software; don't roll out more excuses.

harikari
Participant
March 24, 2021

I ended up making a batch file and keeping it on my desktop. It kills all instances of Acrobat. Faster than having to pull up task manager every time. 

Dov Isaacs
Legend
August 17, 2017

No, there is no way to disable such file locking. And for good reason ...

It isn't just a matter of whether Acrobat is editing the file or not. Acrobat doesn't read the entire file into memory at one time; PDF files can literally be gigabytes in size! If the file wasn't locked and it was deleted or changed while the file was open, you would end up with a situation in which Acrobat would not be able to count on the integrity of what it was reading (or unable to read) from disk. The alternative would have been for Acrobat to make a complete temporary directory of every file that it opens. That would be time and disk consuming.

Quite frankly, I'd be very wary of any applications that allow files that it currently has opened to be modified or deleted behind its back.

          - Dov

- Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
Participating Frequently
August 17, 2017

Dov,

Thanks for your reply, but I disagree. 

As long as the file is not being edited, there is absolutely no technical need for Acrobat to lock it. I would rather have an error that the file has been deleted or modified and needs to be reloaded than a nanny file lock that prevents my applications from working together.

-Donald

cakeller98
Participant
September 27, 2019
Not to mention that Acrobat refuses to let go in a timely fashion. Not only this, but acrobat should NEVER lock a file just to create a thumbnail. Light touch only! if you're making a thumbnail and lose access to the file, so what, fail gracefully. Instead what happens? I get "file is in use and cannot be moved at this time" why? because I touched the file to select it to move it! this is just poor developer behavior! not impressed and this has been a problem for over a decade!