Unexpected file opening error: File info is not identical with opened file

@andrewkroh Very interesting. Does it still pick up the file on the next scan or do the tests fail? Any chance to compare the identifiers in the registry to the ones from the OS? Could it be that one of the 3 identifier changes when fetching the file info or if the file is opened? Because the reading and opening are so close together, it's very unlikely that this happens on a common level without the commands actually causing it.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.