Verifying a software download before running it is a practical way to catch incomplete transfers and files that do not match an official release. Windows 11 includes the tools needed to calculate a SHA-256 checksum without installing an extra program. The process takes a downloaded file, calculates a 64-character hexadecimal fingerprint, and compares it with a trusted value published by the vendor.
Last Reviewed: November 21, 2026. This guide follows Microsoft command documentation and distinguishes download integrity from publisher authenticity. It does not claim hands-on testing of every file format or vendor release.
Download the file from the official publisher and copy its trusted SHA-256 reference. Open PowerShell and run Get-FileHash -LiteralPath 'C:\path\yourfile.iso' -Algorithm SHA256, substituting the actual file path. Compare the complete output Hash with the published SHA-256 digest. If the values differ, do not run the file; check the version and download again. A match confirms agreement with the reference, not that an untrusted publisher’s software is harmless.
Checksum Command Comparison
| Tool | Example Command | Output |
|---|---|---|
| PowerShell | Get-FileHash -LiteralPath 'C:\path\file.iso' -Algorithm SHA256 | Algorithm, Hash, File Path |
| Command Prompt | certutil -hashfile "C:\path\file.iso" SHA256 | SHA-256 File Digest |
What SHA-256 Verification Actually Checks
A SHA-256 checksum is a short fixed-length fingerprint calculated from the contents of a file. If even a small portion of the file changes, the resulting SHA-256 digest will almost certainly be different. Comparing a downloaded file’s digest with a value provided through a trustworthy publisher channel is a useful way to detect corruption, incomplete downloads and substitution. The technique works for installation files, compressed archives, disk images, documents and many other file types.
The important condition is that the expected digest itself must come from a trusted source. A malicious download page can publish a checksum for its own malicious file, and the comparison will still succeed. Therefore, a checksum match helps verify byte-for-byte agreement with a reference; it does not by itself establish publisher identity or guarantee that the software is safe. Our What Is A Checksum guide explains the broader concepts behind integrity checks.
Understand The Difference Between Integrity And Authenticity
Integrity asks whether a file matches a specific expected version. Authenticity asks whether a trustworthy party actually supplied or approved that version. SHA-256 is strong for detecting changes when you have a reliable expected value, but it does not authenticate the publisher on its own. A digital signature may provide an additional way to validate the signer and file integrity, subject to certificate trust and signing rules.
For software installers, combine a trusted HTTPS download source, the correct official checksum, a valid publisher signature when available, and ordinary Windows security checks. No single signal replaces careful source selection. If a download page offers a matching hash but is pretending to be an established vendor, it may still be unsafe. Our Fake Software Download Button guide describes deceptive download pages and how to avoid them.
Find The Official Expected Hash First
Before computing anything, find the reference SHA-256 digest published by the software vendor or project owner. It may be on an official release page, in a signed checksums file, or alongside an operating-system ISO download. Confirm that it corresponds to the exact file edition, architecture, release number and language that you downloaded. A hash from last month’s build does not validate this month’s installer.
Avoid copying a digest from an unrelated forum or search snippet without checking its original source. A legitimate project may publish several checksums for different builds, and choosing the wrong line can produce a false mismatch. If the publisher does not offer a trustworthy hash, do not invent one or treat a hash from an unknown mirror as authoritative. The result must be compared with a value whose provenance you can defend.
Open PowerShell Without Administrator Access
Windows 11 includes PowerShell tools suitable for calculating local file hashes. For a typical file in Downloads, you do not need to run as administrator. Open Start, search for PowerShell or Windows Terminal, and launch a normal shell. On managed PCs, use the approved terminal application. Running as an administrator adds privileges that are unnecessary for reading an ordinary downloaded file.
Do not change the execution policy, disable antivirus, or install a third-party checksum application merely to run Get-FileHash. Microsoft documents the cmdlet as part of the supported PowerShell utility module. When the downloaded file is stored in a protected folder, choose an authorized location or ask the administrator for access instead of changing folder ownership.
Identify The Exact Downloaded File
Open File Explorer and navigate to the directory containing the file. Inspect the full filename, extension, size and modification date so you do not hash an older duplicate by accident. Windows may append a number to repeated downloads, producing names such as installer (1).exe. The checksum of that older or newer file may differ even when the displayed product name looks the same.
If file extensions are hidden, enable the File Explorer setting that displays them where supported. A misleading filename such as document.pdf.exe is a warning sign independent of checksum verification. Choose the exact file that you intend to install or extract, not merely a similarly named item in the same folder. Our File System explainer covers how file paths and file identity relate.
Use Get-FileHash With SHA256 Explicitly
The standard PowerShell command is Get-FileHash -LiteralPath ‘C:\Users\YourName\Downloads\Example.iso’ -Algorithm SHA256. Replace the example with the actual file path on your computer. The -LiteralPath parameter is useful when a filename contains special characters that might otherwise be interpreted as wildcards. Explicitly specifying SHA256 also makes the chosen algorithm obvious to anyone reviewing your procedure.
The command is read-only with respect to the file contents. It calculates a digest and reports information such as Algorithm, Hash and Path. Microsoft’s Get-FileHash reference documents how the cmdlet behaves. Copy the entire displayed digest, and avoid accidentally including spaces or line breaks when you compare it with the expected value.
Copy The Full File Path Safely
A reliable way to avoid typing mistakes is to use File Explorer’s Copy as path function where supported. Paste the result into the PowerShell command after -LiteralPath and check quotation marks. Paths containing spaces require correct quoting; a path like C:\Users\YourName\Downloads\My Installer.exe will not work if it is broken into separate unquoted arguments.
Do not copy a command from a download site that includes unrelated script execution or security-policy changes. The hash calculation should be a simple file-reading command. If PowerShell reports that the path does not exist, confirm the file’s location and spelling rather than opening the shell with administrator privileges or disabling Windows security features.
Read The Output Without Confusing Fields
Get-FileHash normally returns three important pieces of information: the algorithm, the hash value, and the path. Confirm that Algorithm is SHA256. The hash is a hexadecimal sequence representing 256 bits, typically displayed as 64 hexadecimal characters. The path should match the file that you intended to verify. A hash calculated from an unintended file has no value for validating the intended download.
Copy only the digest portion when comparing it with the official value. Case differences between uppercase and lowercase hexadecimal letters do not change the mathematical hash, but missing characters or altered digits do. Do not shorten the digest to the first eight characters just because it looks more convenient. The complete value is the one that should be matched.
Compare Against The Publisher Value
Place the expected SHA-256 checksum and your calculated SHA-256 value side by side in a plain text editor, or use a controlled comparison script once you trust both inputs. They should match exactly as hexadecimal values after removing irrelevant whitespace and normalizing letter case. Verify the reference’s filename again before interpreting the result.
If the values match, you have strong evidence that the local file bytes agree with the reference digest. You have not proved that the publisher is legitimate or that the program is harmless. Do not run a file solely because one website shows a matching string. For sensitive installers, continue with publisher verification, Windows security checks, and an authorized source.
Use A Controlled PowerShell Comparison
For a repeatable procedure, you can store the official digest as a text value and compare it with the Hash property returned by Get-FileHash. A normal string comparison can be made case-insensitive while preserving the complete digest. Never embed a private password or access token in a checksum comparison script, because none is required.
For example, after setting $expected to the actual official hexadecimal digest, compare $actual = (Get-FileHash -LiteralPath ‘C:\path\file.iso’ -Algorithm SHA256).Hash and then evaluate $actual -eq $expected. Replace the placeholder values; do not copy an invented hash from a tutorial. A False result means you must investigate the file or reference rather than automatically ignoring the warning.
What To Do When The Checksums Do Not Match
A mismatch means that the file bytes and reference digest do not correspond. Common causes include an incomplete download, a different software version, using the wrong architecture or language build, a mistakenly selected local file, an incorrect reference, or file modification. Deliberate tampering is also possible. A mismatch alone does not tell you which cause applies.
Do not install, run or extract a software package when its integrity check fails unexpectedly. Verify the official digest and exact filename, then delete or quarantine the suspect copy according to your security policies and download again from the authentic publisher. If the second independent copy still differs, contact the vendor. Avoid turning off security controls or using an unknown mirror just to obtain a file that produces a desired hash.
Check Whether The Reference Is For The Right Build
Large vendors may publish separate checksums for Home, Pro, Enterprise, x64, ARM64, regional editions or multiple release channels. Even files sharing a familiar product name can contain different bytes. A developer may rebuild an installer without changing its marketing label, creating a new valid hash that no longer matches an older release note.
Read the official version identifier, file size, publication date and architecture alongside the checksum. When the expected digest is from a previous release, do not assume the new file has been compromised. Find the correct release reference instead. If the vendor provides a checksum list with several filenames, match the entire filename, not just the project name.
Check Download Interruption And File Size
A connection interruption can produce a partial file, although some browsers resume downloads and verify them internally. Compare the file size shown in File Explorer with the vendor’s stated size if available. If the file remains marked as a partial or temporary download, let the transfer complete before hashing. Do not rename a partial file to the final extension to make it look finished.
If the browser says the download is complete but the hash differs, try an authorized fresh download. Avoid assuming that all mismatches come from corruption, because downloading a different version can produce the same symptom. Maintain the original mismatch record when filing a support report, but do not publicly publish private local paths or account data.
Use Certutil As An Alternative On Windows
Windows includes certutil, a command-line utility whose supported syntax includes -hashfile followed by the file and hash algorithm. An example is certutil -hashfile “C:\path\file.iso” SHA256. Microsoft documents the command on Windows 11 and Windows Server. It can provide an alternative when PowerShell is not convenient.
Do not confuse certutil’s many certificate-authority functions with the simple local hash calculation. Use only the documented hashfile operation for this task. Results from Get-FileHash and certutil should agree when they use SHA256 on the exact same file. If they do not, verify paths, algorithm selection and whether the file changed between calculations before drawing conclusions.
Understand Why MD5 Is Not The Recommended Choice
Some legacy download sites still publish MD5 or SHA-1 checksums. Those older algorithms have known cryptographic weaknesses and are not suitable for strong collision resistance. SHA-256 is the preferred general-purpose digest for the integrity checks described here when the publisher supports it. Microsoft documentation includes guidance to avoid broken hash algorithms in security-sensitive code.
Do not compare a SHA-256 digest with an MD5 digest and treat their different lengths as evidence of corruption; they are different algorithms and cannot match. If a publisher only offers an outdated algorithm, consider whether it has another supported verification method, such as a valid digital signature or a more modern checksum. Do not fabricate a SHA-256 reference from somebody else’s file.
Do Not Treat Hashing As Antivirus Scanning
The Get-FileHash command reads bytes and calculates a digest. It does not analyze whether the software contains malware, whether a macro is malicious, or whether an installer will behave responsibly. A malicious file can have a perfectly valid SHA-256 checksum and the publisher can truthfully distribute that checksum.
Keep Microsoft Defender, browser download protection, SmartScreen and organizational security controls enabled according to policy. Download from known official sources and avoid untrusted installers. Our Ransomware explainer shows why executable content deserves independent attention even when a file was transferred intact.
Understand Digital Signatures As A Separate Check
Some executable files and scripts carry Authenticode signatures that Windows can evaluate. The PowerShell Get-AuthenticodeSignature cmdlet reports signature information, which can help assess whether the signer and content meet the expected trust conditions. Not all files are signed, and some file formats do not use Authenticode in the same way.
A valid signature is not a guarantee of harmless behavior, and a missing signature is not automatic proof of infection. Evaluate the signer against the vendor you intended to obtain software from. Microsoft’s Authenticode signature command reference describes the available checks. Our Digital Signature explainer covers how signatures differ from plain checksums.
Verify Windows Installation ISO Files
Operating-system ISO files are especially important to verify because they may be large and may be used to install or repair the entire computer. Microsoft publishes Windows 11 download information and, for supported downloads, checksum verification guidance. Ensure that you use the official Microsoft download page and match the ISO edition, language and architecture to the exact reference digest.
Do not run setup from an ISO that fails an official integrity check. Re-download through the supported channel rather than altering boot settings or disabling protection. A matching checksum only verifies agreement with the trusted reference; you must still choose a legitimate installation workflow and maintain backups. Microsoft’s Windows 11 download page provides official distribution guidance.
Verify Compressed Archives Before Extraction
A ZIP, TAR or other archive may contain many individual files, but a SHA-256 digest of the downloaded archive covers its exact bytes. If the publisher provides a digest for the archive, calculate the hash before extraction, especially when it contains scripts or executable tools. After extraction, the archive checksum no longer corresponds to any one extracted file.
Do not assume that a checksum match means every included program is trustworthy. Archives can legitimately contain malicious code if the publisher is malicious or compromised. Use an appropriate extraction utility from a trusted source, inspect filenames and avoid executing scripts automatically. If an archive is password-protected, verifying its outer file checksums does not reveal or validate the safety of the decrypted contents.
Check USB Copies And Transfers
If you copy a large file from Downloads to a USB drive or external SSD, you can compute SHA-256 on both copies to verify byte-for-byte agreement. This can help diagnose storage or transfer problems. Use exact file paths and calculate after the copy is fully complete and the drive is safely connected.
A matching hash shows the copies agree, not that the original was trustworthy. If the values differ, inspect whether a copy is incomplete or whether the file was changed between calculations. Avoid modifying the original while comparing. For important backups, hash verification is useful alongside actual restore testing and safe storage practices, as discussed in our Cloud Backup Software guide.
Use A Short Verification Checklist For Repeated Downloads
For every important installer or ISO, record five facts: the official download URL, exact filename and version, the expected SHA-256 from a trusted publisher channel, the locally calculated SHA-256, and the comparison result. This produces a compact audit trail useful for personal troubleshooting and organizational deployment.
Avoid storing private usernames or entire local directory structures in a public spreadsheet. A checksum itself is not generally a password, but metadata about proprietary software and internal downloads may still be sensitive. A well-designed checklist uses the official reference as the basis, not an automatically copied value from the same untrusted download.
Avoid Online Hashing Websites For Sensitive Files
Many websites offer to calculate a checksum if you upload a file. That requires transferring the file to a third party and may expose confidential documents, private installer builds, or personal data. Windows already provides local commands, so online uploading is unnecessary for routine SHA-256 verification.
Use Get-FileHash or certutil to keep the bytes on your own computer. A website that asks for a large confidential file merely to calculate its hash offers little benefit compared with a local command. Some web tools process files entirely in the browser, but claims about implementation and privacy should be independently verified rather than assumed. The simplest secure method is a documented built-in utility.
Keep The Source And Reference Separate
A trustworthy verification depends on a reference not derived from the questionable file itself. If an attacker changes both a download and the checksum shown on the same compromised page, they can create a matching pair. For critical software, look for signatures, signed release manifests, or independent trusted announcement channels when available.
The authenticity of the reference is the center of the process. Avoid taking a digest displayed by a mirror as independent proof that the mirror is safe. Even an exact match to a legitimate official digest does not replace security updates or safe execution practices after installation.
Understand Reproducibility And File Metadata
SHA-256 is calculated from file content rather than the visible filename or ordinary file timestamps. Renaming a file alone does not change its digest, whereas changing a byte of its contents usually does. A file copied to another drive should retain the same checksum if its bytes remain identical.
This distinction helps when people compare two similarly named files or accidentally hash an older duplicate. It also explains why compression or repackaging creates a new digest even if the extracted payloads look similar. Do not expect ZIP and extracted folder hashes to be directly comparable without a documented reproducible process.
Handle Errors Without Disabling Windows Security
If Get-FileHash reports that a file cannot be read, check whether the path is correct, the download is complete, the file is locked by another process, or your account lacks access. Do not respond by disabling Defender, running PowerShell as administrator or granting broad folder permissions immediately.
If the file is protected by organization policy, ask the administrator for an approved way to access it. For a file you own, choose a normal readable location. If it is still being downloaded, allow the transfer to finish. A read-only hash should not require changing the file contents or installation security configuration.
What To Do After A Successful Check
After confirming that the SHA-256 matches a trustworthy official reference, continue with normal installer safety steps: check the publisher, verify a digital signature when one exists, read any administrator privilege request carefully, and follow vendor installation instructions. If a package is not needed, do not install it merely because its hash matches.
Keep the reference digest and version information for later support if relevant. A checksum match is one meaningful security and reliability signal, not an unconditional endorsement. Our software download safety guide explains how deceptive pages can still be risky despite polished branding.
When To Contact The Vendor
Contact the publisher when a fresh official download repeatedly differs from a checksum listed for the exact same build. Provide the filename, version, size, SHA-256 result, operating system and official page where the expected value appeared. Do not send passwords, account tokens or confidential files in a public bug report.
The vendor may have replaced a build, published an incorrect checksum or discovered a distribution issue. Avoid treating the first mismatch as automatic evidence of an attack, but do not disregard it either. Wait for a confirmed explanation or a corrected official release before relying on the file.
Frequently Asked Questions
What Is A SHA-256 Checksum?
It is a 256-bit digest computed from a file’s contents, commonly displayed as 64 hexadecimal characters and used to compare file integrity.
How Do I Check SHA-256 In Windows 11?
Open PowerShell and run Get-FileHash -LiteralPath followed by the exact quoted filename and -Algorithm SHA256, then compare the full Hash value with the official publisher reference.
Do I Need Administrator Privileges To Calculate A Hash?
No, not for a normal file that your account can read. A standard PowerShell session is generally sufficient.
What If The SHA-256 Checksums Do Not Match?
Do not run the file. Recheck the exact version, filename and official reference, then obtain a fresh trusted download or contact the publisher.
Can A File Be Malicious Even If Its Checksum Matches?
Yes, a checksum match alone does not establish publisher identity or software safety, especially if the reference comes from an untrusted page.
Can I Check A File With Certutil Instead?
Yes, Windows supports certutil -hashfile with the filename and SHA256 algorithm as a local checksum calculation.
Is SHA-256 Better Than MD5 For This Task?
Yes, sHA-256 provides stronger collision resistance and is preferred for modern security-sensitive integrity verification.
Does Renaming A File Change Its SHA-256?
No, the digest is based on the file bytes, not the filename. Changing the contents will usually change the digest.
Is Get-FileHash The Same As Checking A Digital Signature?
No, a hash compares file content with a reference, while a digital signature can provide additional signer and integrity information when correctly validated.
Should I Upload My File To An Online Checksum Website?
Usually not. Windows can calculate the hash locally without sending sensitive file contents to a third-party service.
Official Microsoft Sources
Primary documentation: Microsoft PowerShell Get-FileHash; Microsoft Get-FileHash For Windows PowerShell 5.1; Microsoft Certutil Command Reference; Microsoft PowerShell Get-AuthenticodeSignature; Microsoft Windows 11 Download Verification; Microsoft Guidance On Avoiding Weak Hash Algorithms. Hashes must be matched against a trusted value for the exact build.



