I completely skipped Win 8 and its successors, so I didn’t encounter this problem until now. That it’s persisted so long, through three major revs or so, is pretty pissing.
The basic problem is that you cannot delete PDFs that have been created or viewed any time recently, “recently” sometimes being days if the system hasn’t been restarted. There is some fundamental interaction between the OS and this file type that locks the file with an unidentified process - and closing every app that might use a PDF and trying to kill processes that might be related doesn’t work very often.
Since I sometimes create a dozen PDFs in a short time while proofing work, I hate having to specify a new filename each time, then have sometimes-large files clog my hard drive for days. This is Microsoft and Adobe… if any pair of software companies could work out a mutual bug, ya’d think…
There are various workarounds and some point a finger at Win 10’s Reader… except that many of us don’t even have that applet installed. Nor does disabling preview and info windows, which greatly reduces file management capabilities anyway.
The only solution is to use Shift-Del, which sends files directly to bitstream hell instead of the recycle bin… and I have long since learned to love the two-stage delete system and how many times it’s saved my hasty ass.
I guess this is really a micro-pit, because there’s no known fix and both companies just kind of shrug and smile when users complain about it. Such a stupid, pointless little glitch to have happened at all, much less to persist through three major revisions of an OS.
There are many links and discussions but most are under “Win 8” as the problem isn’t new in Win 10. It also is a bit hit-or-miss, with some folks having no problems and others unable to delete a single PDF without jumping through hoops. If there’s any consensus on the cause, I can’t find it - although every discussion has a fairly smug, “This is the cause… do this.” Which does not work for everyone who comes along, so the real problem has to lie elsewhere.
Some solutions work for some users, others don’t. For me, if a PDF ends up “locked,” absolutely nothing short of Shift-Del will get rid of it. Even a reboot does not always cure the problem. The added PITA for me is that I have to rename PDFs fairly often, and this lock won’t let that happen.
It’s not Windows Reader; I don’t even have it installed.
It’s not Explorer Preview or Detail pane; I spent a couple of reboot sessions without those useful tools and it still happened.
It’s nothing to do with a browser - my workflow doesn’t include one and I never use FF to open PDFs on my system (on the web, yes).
Closing every app that could conceivably get a hook into a PDF, and sweeping for stealth programs in Task Manager, and closing the odd process that seems to be related… nada.
Some of these do fix things for some users. Not me, boss.
What’s the usual content of your PDFs? What were they created from? Are they really large, like 50+ meg?
I ask because I have similar problems with working with PDFs made from MS Word documents that include a lot of scans. They take forever to open and forever and a day to save after I make comments and annotations. If I have to delete them, I sometimes have to reboot to clear memory first.
I keep begging the content developers to convert the original doc to PDF instead of scanning all its pages and inserting them into Word doc templates, but no dice.
Almost entirely work proofs or print submissions created in Adobe Creative Suite, and no, they rarely exceed 3-4MB.
I can see PDFs being created or managed by third-party tools, especially shareware or the like, being a problem. That Win 10 + up-to-date Adobe tools does it is… irritating. Especially as it’s persisted for a couple of years with no real determination of the cause or a fix on any level.
I could not delete a PDF yesterday, even with Shift-Del, apparently because Explorer preview had it locked.
The number of otherwise knowledgeable users who (1) really don’t understand what a PDF is or how best to use the format and (2) insist on pounding huge image files into Word docs is far too high.
I’m guessing the Windows Indexing service is busy in the background reading and indexing the PDF. I’m not entirely sure what the service name is in Windows 10, but that might point you in the right direction.
I never had the problem with Win 7, in perhaps five years and several iterations of the Adobe suite. From the online ranting, it seems to have begun in force with Win 8.
I don’t even have Adobe Reader installed; I use Acrobat Pro as a regular working tool and substitutes aren’t an option.
Other than a general anti-Adobe and -MS rant, this isn’t much help. There *are *no substitutes for the Adobe toolset, and I have none of the MS applets installed (such as their version of Reader).
The problem is at some fairly low level with the OS’s control of this, and only this file type. People have been bitching about it for two full years and the official suggestions for fixes are between useless and laughable… while most community suggestions basically boil down to “bang on it until it works.”
If it is a case of just using a different PDF reader, then just to say that it is possible to use the PDF readers built into Firefox or Chrome. Either can be used as the default PDF reader. They do the job OK.
It has nothing to do with PDF readers. It has to do with something at the OS level, or with a stealth app/applet/service, locking PDFs against changes (deletion, moving, renaming) even when no reader or browser is involved.
Ah, missed the edit. I grabbed Unlocker and tried it - “No locking handle found” on several problem files. It did allow the override functions for delete, rename, etc. so it was worth the time to install, for occasional such problems. Thanks!