When saving let's say Excel spreadsheets, the hash changes even if the spreadsheet content doesn't change. Why? about hashcheck HOT 5 OPEN

This concerns the internal structure of Excel documents. A relevant MS forum would be a more appropriate place to ask.
HashCheck is already doing what it's supposed to do. I don't think there's anything else HashCheck can or should do.

from hashcheck.

An Excel workbook keeps metadata for the creation time, last save time, and the last person to save it; this is separate from the similar attributes stored by the filesystem. Even if you have not changed the contents of a workbook, re-saving it will change at least the last save timestamp, which changes the on-disk representation of the file, which changes the resulting hash.

I think you would be better served by an application that can specifically understand and compare Excel workbook files and potentially ignore that embedded metadata vs. HashCheck which, like most any hashing utility, doesn't care about the format of its input files and simply treats them as opaque byte streams.

from hashcheck.

HashCheck only includes file content, not metadata.

It's Excel's problem that it changes the file content even when no visible content is changed. This can happen, for example, when there's a volatile function in your workbook.

from hashcheck.

from hashcheck.

from hashcheck.