Technical Anshu
Tutorials Blog
🔑 Hash Check

Windows ISO SHA256 Hash Check Step by Step and Where to Find the Official Hash

The hash check fails most people at one place: finding the correct official hash to compare against. This page walks the whole check slowly - calculate, locate, compare - and warns about the one trap that makes fake ISOs look genuine.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ Step by step
🎥 Watch the full video — the verifier tool and the hash check, shown step by step

A SHA256 hash is a 64-character fingerprint calculated from the file itself. Your half of the job is easy - Windows calculates it with one command. The other half is where mistakes happen: the reference hash must be for the same version, edition set, language and architecture, and it must come from a source that is independent of whoever gave you the ISO. Do both halves right and the answer is certain.

Before You Compare — The Four Things That Must Match
✅ Same Windows version — for example 24H2 is not 23H2
✅ Same edition file — Consumer editions ISO is not the Business editions ISO
✅ Same language — English (United States) is not English International
✅ Same architecture — x64 is not ARM64
⚠️ One difference in any line = a different file = a different hash
Four checks before comparing. Most false alarms come from comparing against a hash for a slightly different file.
1

Step 1 — Calculate Your File Hash with PowerShell

Open the folder containing the ISO, click in the address bar, type powershell and press Enter. Then run:

  1. Get-FileHash .\YourFileName.iso -Algorithm SHA256
  2. Wait for the result - a 5 to 6 GB ISO takes under a minute on most PCs
  3. Right-click the output to copy the hash exactly; do not retype it

The Command Prompt equivalent is certutil -hashfile YourFileName.iso SHA256. Both give the same value; certutil prints it with spaces in older Windows versions, which is cosmetic only.

2

Step 2 — Find the Official Hash for Your Exact File

Microsoft publishes SHA256 hashes for its downloads. Where you will find yours depends on how the file was released:

  1. Software download pages - the Windows 10 and 11 download pages on microsoft.com list file details for the ISO downloads offered there
  2. Volume Licensing / Microsoft 365 admin portal - businesses downloading through their agreement see the SHA256 next to every product download
  3. The Genuine ISO Verifier database - the tool from the video carries hashes of known genuine Windows and Office releases, which is why it can give a verdict without you searching at all

If Microsoft's consumer page does not show a hash for your exact file, the verifier tool's database or your licensing portal are the reliable fallbacks - not a random forum post.

3

Step 3 — Compare Without Fooling Your Eyes

Sixty-four hex characters are designed to be compared by pasting, not by reading:

  1. Paste your calculated hash and the official hash into a blank Notepad window, one per line
  2. Check the lengths first - both must be exactly 64 characters
  3. Compare in blocks: humans are good at spotting the first block that differs
  4. Case does not matter - uppercase and lowercase versions of the same hash are the same hash; some tools print one way, some the other

One different character anywhere means a different file. There is no such thing as a near match.

4

The Same-Site Trap — Why a Matching Hash Can Still Lie

Here is the trap this whole topic exists for: a fake-ISO site knows people check hashes, so it prints a SHA256 on the download page. But it prints the hash of its own modified file. Your calculation matches their printed hash perfectly - and proves nothing, because both numbers came from the same untrusted source. The reference hash only has value when it comes from somewhere the ISO supplier does not control: Microsoft's own pages, your licensing portal, or an independent verifier database. If the only place a hash appears is the site that handed you the file, you have checked the file against itself.

🔴 Remember the independence rule: file from one place, hash from another. The moment both come from the same page, the check is theatre — it looks careful and proves nothing.

🎥 Watch the Complete Video Guide

Every step shown live — checking a real ISO with the verifier tool and with PowerShell.

▶️ Watch Full Video
❓ Common Questions (FAQ)

Get-FileHash gives an error that the file is in use or missing. What now?

Usually the path is wrong - the command looks in the folder PowerShell is currently in. Run cd to the folder holding the ISO first, or drag the file into the PowerShell window to paste its full path. If the ISO is open in a mounting or burning tool, close that tool and retry.

Is SHA1 or MD5 matching good enough?

No. MD5 and SHA1 are old algorithms with known collision attacks - a modified file can be crafted to match them. Microsoft publishes SHA256 for current releases; always compare SHA256 when it is available.

Where is the official hash for a Windows 11 English International ISO?

It differs from the US English file, which is the classic false alarm. Get it from the same Microsoft download page for that language variant, your licensing portal, or let the Genuine ISO Verifier identify the file from its database.

This guide is based on the Technical Anshu video on verifying genuine Windows ISOs • Stuck on a step? Ask in the video comments — you will get an answer there 🙏