OS Mastery Simple OS learning for a global audience Start Here

Verify Download Integrity

Check a file hash before you trust or use an important download.

Task guide

Verify Download Integrity

Use this when a download matters enough that corruption or tampering would be a real problem.

A hash check turns vague trust into evidence. It helps you confirm that the file you received matches the file that was expected.

Files and Storage 15 min both
Open domain Open related problem
Safe first move Get the expected hash from a trusted source. Do not trust a hash from the same untrusted source as the suspicious file.
See the model File Lifecycle and Delete-Recover Map Fix a live problem Drive Mounts but Files Cannot Be Read Safely
Use this when

Use this when a download matters enough that corruption or tampering would be a real problem.

Goal

Confirm that the file you downloaded is the file you meant to trust.

Safe sequence

  1. Get the expected hash from a trusted source.
  2. Calculate the hash of the local file.
  3. Compare the values exactly.
  4. Trust the file only if the values match.

Move on when

  • You can calculate a hash on your platform.
  • You can compare it correctly.
  • You know what a mismatch means.
Before you start
  • Get the expected hash from a trusted source.
  • Use the exact file you intend to verify.
  • Do not rename or re-save the file in a way that changes the contents first.
Verify with
  • The calculated hash matches the trusted published hash.
  • You can state which algorithm was used.
  • You can reject the file safely if the hashes do not match.
Avoid these mistakes
  • Do not trust a hash from the same untrusted source as the suspicious file.
  • Do not keep using a file when the hash does not match.
  • Do not confuse a matching file name with matching file contents.
Quick reference
File Lifecycle and Delete-Recover Map

See what usually happens after create, edit, move, delete, archive, and recovery decisions so troubleshooting stays calmer and safer.

 Get-FileHash

Open command lookup for this task.

 sha256sum

Open command lookup for this task.

 certutil

Open command lookup for this task.
Move on when
  • You can use a hash to verify an important file.
  • You can explain why integrity checks belong before trust.
  • You can stop using a mismatched file.
Reflect before you leave
  • Why does a matching file name not prove the file is safe?
  • What would you do differently if the hash did not match?

Review this task again in about 1, 7, 21 days.

Learn deeply
M04 - File System Architecture: How Your OS Organises Data

Understand the map of the file system well enough to recognize Windows drive-letter paths, Linux root-tree paths, and the difference between a file name and the data behind it.

 M09A - File Metadata, Hidden Files, and Links

Understand file metadata, hidden files, shortcuts or links, and why the path you see is not always the full story behind a file.

 M26B - Recovery-Safe File and Storage Workflow

Learn the safe response order for file and storage trouble so you protect data before cleanup, repair, or recovery actions.
Practice it
LAB-FS-10 - Links, Hidden Files, and Metadata Checks

Inspect metadata, hidden state, and links so file confusion turns into a structured check instead of a panic reaction.
See the model
File Lifecycle and Delete-Recover Map

See what usually happens after create, edit, move, delete, archive, and recovery decisions so troubleshooting stays calmer and safer.

What to do next

Best next step Learning

Open the lesson path when you want the full explanation behind the task.

Open now
Practice

Use labs to turn this task into repeatable skill.

Open now Troubleshooting

Use problem-first help when the task is part of fixing a live issue.

Open now