Take the 2-minute tour ×  I'm currently investigating a problem
with my company's build server; roughly 1/10 of the builds fail
due to a file being locked. It's a Windows 2003 virtual server
running on top of VMWare. The server is not alone in the issue,
with other servers experiencing similar problems, but it's the
most pronounced as the build system accesses vastly more files
more frequently than most others.  Attempts to identify the
process locking the files have failed; by the time we run a
program like Process Explorer, there are no locks present on the
files in question.  I've tried running Process Monitor, but
there's such a volume of information over the thousands of files
used by the build system and it's not easy to identify what
specifically has locked a file at the time the error occurs.
Are there any tools or techniques that we can use to identify
the process locking these files?  share|improve this question Is
the file locked or just opened ? Have you tried disabling your
AV ? –  Stephane Nov