A WinRAR SHA-256 mismatch means the file you measured does not match the bytes represented by the expected hash. Before drawing a conclusion, check whether the expected value belongs to the same download source, version, language and architecture.
We found a concrete example: the two official sites served different English x64 installers carrying the same filename and version. This guide records what we measured and separates those observations from things we did not test.
Two official downloads, two different files
On 30 September 2026 (UTC), we followed the English 64-bit WinRAR 7.23 links from win-rar.com and rarlab.com. We downloaded each file separately and calculated its SHA-256 locally.
| Check | win-rar.com download | rarlab.com download |
|---|---|---|
| File | winrar-x64-723.exe |
winrar-x64-723.exe |
| Exact size | 3,849,112 bytes | 3,775,056 bytes |
| Calculated SHA-256 | f435b24d4c2c5342c4f7c0143ef358f0f425b7b8a0972dd34d9dcf94789e9c4d |
8ff0daf3ed564cc743c0e23ff2e253997ffc74460f9673f0b6dd037b2db4ce7b |
| Publisher digest comparison | Matches the SHA-256 shown on win-rar.com | No corresponding per-file digest found in the RARLAB download listing; this is our local measurement |
| Windows signature result | Valid; Authenticode; CN=win.rar GmbH |
Valid; Authenticode; CN=win.rar GmbH |
These results apply to the files retrieved in this check. We inspected their signatures on Windows 11 Home, build 10.0.26300, using PowerShell 7.6.5. We did not run either installer, compare installed contents or investigate the cause of the packaging difference. A valid signature does not substitute for those tests or for a malware assessment.
11 October 2026 recheck: the same difference remains
We followed the linked English x64 7.23 downloads again on 11 October 2026 (UTC). The win-rar.com copy was still 3,849,112 bytes, with SHA-256 f435b24d4c2c5342c4f7c0143ef358f0f425b7b8a0972dd34d9dcf94789e9c4d; it matched the digest displayed in that publisher listing. The RARLAB copy was still 3,775,056 bytes, with our locally measured SHA-256 8ff0daf3ed564cc743c0e23ff2e253997ffc74460f9673f0b6dd037b2db4ce7b. We did not find a corresponding per-file digest in the inspected RARLAB listing.
Both files reported version 7.23.0 and returned Valid / Authenticode with signer CN=win.rar GmbH on Windows 11 Home, build 26300, using PowerShell 7.6.5. Their hashes and sizes agree with our separate September 30 observation above. This new check measured downloaded files and read signatures; it did not run the installers or establish why the packages differ. Exact source URLs, byte sizes, hashes and signature observations.
Scope: this guide concerns a downloaded installer’s SHA-256. A “checksum error” reported while extracting a RAR/ZIP archive is a different problem; this comparison does not diagnose or repair that archive.
Choose the next step from the reference, not the filename
| Situation | Decision |
|---|---|
| You downloaded from win-rar.com and the exact 7.23 English x64 entry’s expected hash differs | Keep the installer unopened, check you selected that file and entry, obtain a fresh official copy, then compare again. If it still differs, ask the publisher with the source URL, byte size and calculated hash. |
| You downloaded from RARLAB but compared against the win-rar.com entry | You used a reference for another source. Record the difference and inspect the source/signature separately. Changing the expected value merely to obtain “Match” does not verify the file. |
| You know only the filename, or a checker recognises the name | Obtain an exact trusted reference. The filename alone cannot distinguish those two official files. |
| The supplied hash matches | The bytes agree with that reference. Check the reference’s source and the Windows signature separately; this is not an application security audit. |
How to investigate your own mismatch
- Keep the installer unopened. Record its source URL and the link you followed. The filename alone cannot identify the expected contents.
- Match the build. Confirm 7.23 versus a beta, x64 versus another architecture, and English versus another language. A checksum from a different build is not a useful comparison.
- Read the expected value at its source. For a win-rar.com download, use that site’s value for the exact entry. Do not silently substitute the hash from a different site.
- Calculate the complete file’s hash. Wait for the download to finish, then select that exact file in our local SHA-256 checker or run the command below.
- Inspect the digital signature separately. Follow our Windows signature guide and check the result on your machine.
- If the exact comparison still fails, stop. Obtain a fresh copy from the publisher and compare again. If it remains unexplained, ask the publisher about the version, URL, byte size and calculated hash.
Get-FileHash -LiteralPath "C:\Downloads\winrar-x64-723.exe" -Algorithm SHA256Changing the path to your actual download is essential. Two files with the same name in different folders can give different results. Do not change the expected hash merely to make a check pass.
What this comparison establishes
The measurements show that those two retrieved installers were different byte sequences. The signature check recorded the status and certificate identity returned by Windows. Only the win-rar.com file was compared with a checksum displayed by its publisher.
We cannot infer from this check why the files differed, whether their installed output would be identical, or whether an unrelated file with a similar name is trustworthy. If your source is unfamiliar, verify that source before using any checksum it supplies.
For release-versus-beta information and the 40-day trial, see our WinRAR software entry. Our verification methodology explains the difference between reviewing a publisher page, measuring a downloaded file and actually testing an application.
