x64
VeraCrypt_Setup_x64_1.25.9.msi
- SHA-256
- 206d31c2ed1a2b0390d4dfa12e74a9b9dae88658d1f9bfa1bb433b23e2b24fd8
VeraCrypt · earlier release
The URL IDRIX published for this release, and the SHA-256 of every file in it, so you can prove the copy you have is that one and not something else wearing the same name.
VeraCrypt is now on version 1.26.29. An older build stops getting security fixes, so install one only when you have a reason: a plugin that broke, a machine that cannot run the new one, a bug you need to reproduce. If you just want VeraCrypt, take the current version.
VeraCrypt_Setup_x64_1.25.9.msi
Windows does this without installing anything. In PowerShell:
Get-FileHash .\VeraCrypt_Setup_x64_1.25.9.msi -Algorithm SHA256
Compare what it prints with the value above. If they match, your copy is byte-for-byte the one IDRIX published. If they do not, it is a different file, whatever it is called and wherever it came from. Paste a hash into the verifier and it will tell you which release it belongs to.
If PowerShell is blocked by policy on the machine, the same thing works from plain cmd with certutil -hashfile VeraCrypt_Setup_x64_1.25.9.msi SHA256. On macOS or Linux it is shasum -a 256 VeraCrypt_Setup_x64_1.25.9.msi.
Publishers retire old releases, and we do not host copies, so a link from an earlier version can stop working without notice. Two ways it fails: an honest 404, or — more confusing — the server answers normally but hands you the current downloads page instead of the file. If what arrives is a few kilobytes of HTML rather than an installer, that is what happened.
The hash on this page stays useful either way. It still identifies VeraCrypt 1.25.9 wherever you find a copy, which is the whole point of publishing it: you can accept a file from somewhere else and still prove it is the one IDRIX built.
Every VeraCrypt release we index · where this data comes from