ErrorTimeStamp can occur when file has not changed

Under certain scenarios, RomVault can trigger an error during scanning which shows "ErrorTimeStamp". Its my understanding that RV checks the timestamps of all files in a directory to determine which files have changed and need to be hashed in that directory. It appears that sometimes a file's actual modified time as shown by viewing the properties of the file can differ from the time shown in the Windows Explorer directory view. I believe this discrepancy is causing the ErrorTimeStamp error to occur consistently even if the file has not changed.

Cannot reproduce consistently, but here is what I observed:

1. Downloaded a file with JD2, which failed and was left in a "invalid download" state and was named with a ".zip.part" extension

2. Scanned the file and error occurred

3. Confirmed that the modified timestamp of the file matched exactly what was logged in the cache using the fileDateTime.exe debugging application

4. Noticed that the modified time in the windows directory view differed from the file properties

5. Tried to rename the file to confirm it was not locked

6. Noticed that upon renaming the file, the directory view timestamp for that file was updated to the proper time

7. Renamed file back to the original name

8. Rescanned, and this time the file was properly hashed without error

Expected behavior:

• If they are not already, ideally timestamps should be taken from the same source for all RV actions. ErrorTimeStamp should not occur if the file did not change.

(screenshot)