Two files can have the same name and different contents. Conversely, renaming a file does not necessarily change the bytes inside it. A cryptographic file hash gives you a compact value to compare when the question is whether the content matches a reference.
Compare the same algorithm
Microsoft documents Get-FileHash as a PowerShell command for calculating a file’s hash. Its default algorithm is SHA-256. When comparing a result with a publisher’s value, check that both were calculated with the same algorithm and for the exact same download.
The command reads the file; it does not need to launch the downloaded program. A harmless local example is Get-FileHash -LiteralPath 'C:\Downloads\example.zip' -Algorithm SHA256. Substitute the path to the file you intend to check and compare the complete value, not just its opening characters.
Get the reference from a trustworthy place
A match is only as useful as the reference you compare against. Copying a hash from an unrelated repost does not establish that it came from the software publisher. Check the official distribution page and its explanation of the download.
If the values differ, stop and investigate the version, file choice, and download. Do not edit the published reference to make the check pass. It is reporting a mismatch, not offering a repair.
Keep the conclusion narrow
A matching SHA-256 value is strong evidence of matching file content. It is not a malware scan, a review of the program’s behaviour, or a reason to run software you did not intend to install.
Our guide to downloaded versus installed files separates the next decisions. Hash comparison answers one useful integrity question; source trust and the decision to execute remain separate checks.