A mismatched hash feels like a verdict, but it is really a question. Work through the three causes in the right order and most mismatches resolve into a corrupt download or a wrong comparison - the rest tell you the source itself cannot be trusted.
The hash check said no. Before you conclude anything, remember what a mismatch actually proves: this file is not byte-identical to the official release you compared it against. That happens for three families of reasons - the download broke, the comparison was wrong, or the file really is modified. They are tested in that order, because the first two are common and free to fix, and you only earn the third conclusion after eliminating them.
ISOs are 5 to 6 GB single files, and big downloads break quietly: a dropped connection resumed badly, a browser that declared victory early, a nearly-full disk. Test it the simple way:
If the second download matches, the story ends: the source was fine, the transfer was not. Most real-world mismatches end here.
The second common cause is comparing a genuine file against the hash of its near-twin. Windows releases differ by language (English US vs English International), by edition set (consumer vs business editions ISO), by build update, and by architecture (x64 vs ARM64) - each is a different file with a different hash. Before condemning a file, re-check the reference: does the official hash you used describe exactly the file you meant to download? The Genuine ISO Verifier helps here - instead of you supplying the reference, it identifies the file from its database and tells you what the file actually is, which often reveals you downloaded a different variant than you thought.
You reach this conclusion only after a clean re-download still mismatches the correct reference hash. Now the file itself differs from Microsoft's release - repacked, rebuilt, or tampered with - and there is no safe way to use it:
Also test your storage once: if verified-good files repeatedly corrupt on the same pen drive or disk, the drive itself may be failing - hash a known-good file twice from it and see if the value is stable.
Every step shown live — checking a real ISO with the verifier tool and with PowerShell.
▶️ Watch Full VideoNo. A hash is all-or-nothing: one different character means a different file, full stop. There is no partial credit, and a small difference in the hash can hide a large difference in the file.
The hash. File size is a weak check - padding a modified file to the same size is trivial. Size is useful only as a first screen for incomplete downloads; the SHA256 decides.
No. Nothing can reconstruct the original bytes from a hash - the hash is a fingerprint, not a backup. Re-downloading from a trustworthy source is the only repair.