Verifying a download in 10 seconds: Get-FileHash discipline

The habit is the control

(Get-FileHash .\ProofTune-0.1.0-preview.1-win-x64.msi).Hash
# compare against the value published beside the download link

Lowercase vs uppercase is irrelevant (.ToLowerInvariant() before comparing if scripting). What's not irrelevant:

• Always SHA-256 or stronger. MD5/SHA-1 checksums still scattered around older vendor pages are legacy at best, misleading at best-dressed-up.
• Get the hash from the vendor page, not a mirror. The authenticity chain goes vendor → hash → file. A forum post re-hosting both doesn't have it.
• Mismatch = delete, full stop. Not “quarantine until later” — a file whose bytes disproved its label shouldn't be on your disk to accidentally double-click next month.

Perfection is a two-second ceremony per download; every candidate build you get from the preview page ships with its hash public for exactly this pattern.

ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.