Windows 10. Downloaded audacity-win-2.2.2.exe from Fosshub today, noted the SHA256 signature, opened up the file Properties-File Hashes in Windows Explorer, and there it only shows CRC-32, MD5 and SHA-1 hash values. No sign of SHA256.
Is the SHA256 hash hidden somewhere else in the Windows Explorer file Properties ?
Audacity-win-2.2.2.exe checksum match problem
Forum rules
This forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Re: Audacity-win-2.2.2.exe checksum match problem
This page has a link to a checksum calculator.
Re: Audacity-win-2.2.2.exe checksum match problem
Thank you. I already tried the calculator but the Download page tells me to use SHA-256 and this calculator doesn't get me any further.
Re: Audacity-win-2.2.2.exe checksum match problem
Direct link to the checker: https://md5file.com/calculator
Ensure that the option "SHA-256" is selected (click on picture below to expand):
Ensure that the option "SHA-256" is selected (click on picture below to expand):
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: Audacity-win-2.2.2.exe checksum match problem
Thank you. I had already been there and done that but I think it's finally dawned on me that that calculator is producing a SHA-256 hash which the Windows Explorer Properties function can't or won't and that it is then up to me to compare the calculator-produced hash with the "signature" on the Fosshub site (I presume "signature" is the same as "hash") by going through the two visually and character-for-character (i.e. there's no simple two-slot system for matching the two hashes). Is that correct ?