01
Make the comparison reproducible
Record the publisher's filename, release version, and complete expected SHA-256 value. Hash the downloaded file before modifying it. Compare the full 64-character digest; matching only the opening or closing few characters is an incomplete check. Renaming the file does not change the digest, but editing metadata inside it can.
02
Use a baseline when results disagree
A three-byte file containing abc has SHA-256 ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. Create it without a newline or encoding prefix. If this baseline works but your download does not match, check the exact release, platform variant, and whether the publisher hashed an archive or its extracted content.
03
Separate integrity from trust
A hash comparison checks equality with the reference; it does not tell you whether a program is safe to run. An attacker who can replace both a file and its unauthenticated checksum can preserve apparent agreement. Use publisher signatures or another authenticated distribution mechanism when the origin matters.