I recall a problem on Windows NT where a file operation wasn't visible to the next part of the program until I'd let some time elapse. It was essentially of the same shape as this problem. I think I solved the problem by just introducing and explicit sleep for a second or few to let the file system catch up.