This question already has an answer here:

Sometimes, while trying to edit a file, the editor says "cannot write to file because is taken by another process". So, is there a tool which takes an input a file name (with its path) and tells which process has taken it with write-only acces?

If not, what is the thecnical reason that cannot be answered?

I ask this because is so annoying that the message does not inform what is the damn process locking the file and cannot understand why the OS programmer didn't give that obvious vital information. Thanks!

marked as duplicate by Run5k, Ramhound, fixer1234, Journeyman Geek windows Aug 3 '18 at 2:34

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    We are always glad to help, but this question has been asked many times before. – Run5k Aug 2 '18 at 20:00

Without installing another software, nor programming a power-shell script, the fastest solution was answered here...


  • While we appreciate your feedback, it isn't really appropriate to post a previous answer as a new one. It would be better to simply accept the Possible duplicate that I proposed. – Run5k Aug 2 '18 at 20:34
  • Sorry. I referred to the second answer to the question because the accepted answer were more complicated (the script). In fact, maybe I saw that question and answer before (I saw a lot more here and in other websites), and was really frustrating not having the simpler one (which really is not that simple for something so common and obvious). Maybe that's why this issue is so many times asked. We are guilty of losing our patience, for those not patience enough to report which process is locking a file (it's like throwing an argument out of range exception without mentioning the name). – Néstor Sánchez A. Aug 3 '18 at 8:00

Not the answer you're looking for? Browse other questions tagged or ask your own question.