Verify a SHA-256 checksum on Windows
A SHA-256 checksum lets you confirm a downloaded file arrived intact and matches the exact file that was published. Windows can do this with tools it already has — no extra software. Here’s how, in PowerShell or Command Prompt.
What this solves
When you download a program, you want to be sure the file wasn’t corrupted in transit or swapped for a different one. Publishers list a SHA-256 hash — a long string of hex characters — for each file. If the hash you calculate locally matches the published one, you have the exact file that was published.
What you need
- The downloaded file.
- The published SHA-256 hash, from a source you trust.
- Windows PowerShell or Command Prompt — both are built in.
Step by step
- Note the published hashCopy the SHA-256 value the publisher lists for the exact file you downloaded. Make sure it’s the SHA-256 value, not MD5 or SHA-1.
- Calculate the hash in PowerShellOpen PowerShell, then run this against your file’s path:
Get-FileHash -Algorithm SHA256 "C:\Users\You\Downloads\YTS-Control-Setup-v1.1.0-trial.2.msi"
TheHashvalue it prints is your file’s SHA-256. - Or calculate it in Command PromptIf you prefer Command Prompt, use the built-in
certutil:certutil -hashfile "C:\Users\You\Downloads\YTS-Control-Setup-v1.1.0-trial.2.msi" SHA256
- Compare the two valuesCompare the calculated hash with the published one. The comparison is not case-sensitive, but every other character must match exactly. It helps to paste both into a text editor, one above the other.
What you should see
If the two hashes are identical, the file is intact and matches what was published — you can proceed. Treat a match as your green light to continue.
Common errors
- “No such file” or a blank result: the path is wrong. Put the full path in quotes, or drag the file into the window to insert its path.
- Values look completely different: check you calculated SHA-256 (not MD5/SHA-1) and compared against the SHA-256 the publisher listed.
- A genuine mismatch: if the hashes truly differ, do not run the file. Delete it and download again from the official source, then re-check.
Limitations to keep in mind
A checksum proves the file matches the published hash and wasn’t corrupted. It does not, on its own, prove who published it — that assurance comes from code signing and certificates. So only compare against a hash you obtained from a source you trust, over a connection you trust.
The published YTS Control 1.1.0 Trial 2 values
These are the values to compare against. Each file also has its own .sha256 file beside it in the release, and SHA256SUMS.txt (opens in a new tab) lists them all together.
- YTS-Control-Setup-v1.1.0-trial.2.msi — 56,897,536 bytes
a8c7d1ccb3f9883d6273e7c53d663a7f261dcb0946de58d03513c2d9aa0295f7
YTS-Control-Setup-v1.1.0-trial.2.msi.sha256 (opens in a new tab) - YTS-Control-v1.1.0-trial.2-win-x64.zip — 70,181,080 bytes
330d71bf5650bd4db25e8c38f6b5abdb42747d7868bff5738c5b71cc8ae986e1
YTS-Control-v1.1.0-trial.2-win-x64.zip.sha256 (opens in a new tab)
The byte size is worth checking first: if the file on your disk is not exactly the number of bytes listed, the download is incomplete and the checksum will not match either.
Related YTS Control capability
Use this whenever you download YTS Control or its prerequisites — for example before running the Npcap installer. You’ll find release files via the downloads section on the home page, and the release itself is on the 1.1.0 Trial 2 release page (opens in a new tab).