If you have reason not to trust the LastModified date, you can turn it off (Compare Options > Date & Time > top option) but obviously that will then miss any genuine LastModified differences....
It doesn't use hashing unless you tell it to (Compare Options > 'Use slower...') but even if you set that in 'standard mode', if it has already detected (what it thinks is) an obvious difference, it won't waste time hashing. But if you turn off date/time comparison and the size is also 'not different', it will hash-compare if told to. There's also an option to 'always hash' but this could be overkill, as it will then also always hash even if the file-size is different.
(This latter option is designed for use with profiles that are equipped to store hash values, such as SmartSync, so that those slots are always populated, even if it is 'obvious' files are different right now because of date/size differences - but next time it might not be so obvious, so you need the hash value from 'last run' to have been stored - and so on)
Bear in mid that hash-comparison is much slower, and your time might be better spent figuring out why whatever process is 'guilty' of changing those dates & times and stop it. A normal copy process should preserve LastModified...
It doesn't use hashing unless you tell it to (Compare Options > 'Use slower...') but even if you set that in 'standard mode', if it has already detected (what it thinks is) an obvious difference, it won't waste time hashing. But if you turn off date/time comparison and the size is also 'not different', it will hash-compare if told to. There's also an option to 'always hash' but this could be overkill, as it will then also always hash even if the file-size is different.
(This latter option is designed for use with profiles that are equipped to store hash values, such as SmartSync, so that those slots are always populated, even if it is 'obvious' files are different right now because of date/size differences - but next time it might not be so obvious, so you need the hash value from 'last run' to have been stored - and so on)
Bear in mid that hash-comparison is much slower, and your time might be better spent figuring out why whatever process is 'guilty' of changing those dates & times and stop it. A normal copy process should preserve LastModified...