title: Releasing Windows file share locks
body: <p>This problem crops up every now and then at work. Our build machine can have it's files accessed via a normal windows file share. If someone browses a folder remotely on the machine, and leaves the window open overnight, then the build fails (as it has done now). The explorer window left opened points at one of the sub folders in the source tree. The build deletes the source, and does a clean checkout before building. The delete is failing.</p>
  
  <p>Right now, I'd like to get the build to work. I'm logged in from home, and I'd rather not reboot the build machine. I'm unable to get hold of the person whose machine is looking and the files, and I can't remotely reboot their machine.</p>
  
  <p>When a windows share has a lock, the locking process is System, so I don't think I can kill it, as with normal locks.</p>
  
  <p>Does anyone know a way to release the lock on a shared folder without having to reboot the machine?</p>