To create and verify bulk checksums i use total commander but for single file checks i use the built in crc check from 7zip.
You can find them on the internet in tons of them, craftsmen have produced them a lot. But you can always use Windows' own simple command line feature Example Code: certutil -hashfile "<full path to file with file name and extension>" MD5 or in real life certutil -hashfile "C:\Users\Public\example.txt" MD5 You can use MD5, SHA1, SHA256, SHA512, etc (try yourself) Here is my test result, just for example Code: certutil -hashfile "F:\OfficeProPlus2021Retail.img" SHA1 Microsoft Windows [Version 10.0.19044.1682] (c) Microsoft Corporation. All rights reserved. C:\Windows\system32>certutil -hashfile "F:\OfficeProPlus2021Retail.img" SHA1 You'll get SHA1 hash of F:\OfficeProPlus2021Retail.img: e429862c1f9288cd8f723a09e9176919147fc19f CertUtil: -hashfile command completed successfully.
Powershell: Code: powershell -c "Get-FileHash PATH_TO_ISO -Algorithm SHA1" Just open a CMD window, for example: powershell -c "Get-FileHash C:\ISO\en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso -Algorithm SHA1"
I'd recommend RapidCRC (from OV2). It doesn't add a new tab in the properties menu like the other ones, but adds an option in the right-click menu of any file. It also supports creating checksum files and also registers the extension should you want to double-click on checksum file and check. I'd recommend it if you regularly need to create or check checksums. For checking from time to time, I'd say to use 7-zip's internal checksum verifier.
Nor have you accidentally noticed that it is more than terribly old and rudimentary. Also, MD5 hasn't been used officially for more than 10 years and CRC32 - thank You, but no, my Dear!
Yeah, I don't get it either?!? I'm responding to this because it sounded like @kaljukass thought that MD5 and CRC32 is not still relevant as of this day. Well my friend you have not been in my shoes, every hash and checksum value matters to me since my terrible data loss 2008 and I refuse to let my data be CRC32, MD5 or SHA1 unchecked. This is totally unrelated to HashCalc, but I will not part of this invaluable tool for as long as I live (might vary if it's still supported in future versions of Windows) or else famous last words.
Jpsoft TCC (replacement for cmd.exe) has the "hash" algorithm implemented internally. Good enough for me.