On Windows 10, my build process is copying a read-only file to several different locations. once in a few builds, the original file becomes writable and its "modified date" updates.
I'm trying to find which process or command touches the file. Are there any methods to do that? Here's my unlucky experience with sysinternals Process Monitor (ProcMon): Filter setting:
Note, the only filters are for the file path - I've deleted all the defaults. So, nothing should be hidden by ProcMon.
There is a clear WriteFile operation. Is there any reason why the system would touch the file's date?
I've posted the question here since it seems like a file system issue.