I am using Acrobate Pro version 9.5.1 on a Windows 7 64 bit machine.
Once I have created a PDF, I find I am unable to move or delete the file. If I reboot the machine, I can delete or move the file, but as soon as I open a PDF, the problem is back until I reboot again.
It appears others have had the same problem, but I don't see any solutions. Does anyone have any suggestions or workarounds?
Good day Joe,
A few questions for you:
The file is on my desktop (C:\Users\Joe Parsons\Desktop). Files saved to different locations behave the same way. Trying to open a PDF on that machine using another machine on the network, users cannot save using the same name.
I can move or delete files after rebooting the machine, but once I have opened any PDF, the problem returns.
Thanks for replying. I am at my wit's end here!
Check that no parts of AA are left running after you close it. If AA still has a running part, it may not have released the file back to Windows. Of course, it may be an issue with the 64-bit OS which I am not very familiar with, other than it has caused a lot of different problems for folks.
I have disabled preview. I am pretty sure the PDF files are somehow reserved, and that is why they can't be moved or deleted. If I reboot, I can move or delete them--until I launch Acrobat, then the prblem is back until I rebott again.
I recommend using this program called "Unlocker", available here:
It allows you to find out which application has a "lock" on a file and even
unlock it or kill the process.
You can check the process which has locked the file by using a utility "handle.exe", you can download it free from : http://technet.microsoft.com/en-us/sysinternals/bb896655
Open this exe in command prompt and give the filename as parameter e.g
C:\Documents and Settings\username\Desktop\ handle.exe "C:\Documents and Settings\username\Desktop\xyz.pdf"
Now it will list the procees which has handle of the file. Try killing the process and then deleting or moving the file. But this is not the right solution to kill the process everytime. I am interesting in knowing that which process is locking the file. If possible, please share the file.