Author: timbojones
Subject: handle.exe misses loaded dlls
Posted: 21 March 2014 at 11:47pm
I have found several instances where a process (e.g. robocopy, p4) fails because it can't overwrite a dll file, after handle.exe reports no files in use in the directory. We have worked around this in most cases by also looking for processes running in that directory, but this workaround is insufficient when the exe loading the dll is running from another directory.
Subject: handle.exe misses loaded dlls
Posted: 21 March 2014 at 11:47pm
I have found several instances where a process (e.g. robocopy, p4) fails because it can't overwrite a dll file, after handle.exe reports no files in use in the directory. We have worked around this in most cases by also looking for processes running in that directory, but this workaround is insufficient when the exe loading the dll is running from another directory.
Is there some secret handle.exe argument or another tool that can detect dlls that are locked without having a handle open to them?
I know that tasklist.exe can detect whether a particular module is in use, but I would prefer not to manually enumerate all the modules in a directory.
I want a tool that I can run to determine whether a directory is clear to be removed or replaced, and if not, which processes are preventing it.