Verifying a download
You do not have to do anything. Verification happens by itself, the same way it does for any properly published software. This page exists for people who want to check by hand anyway, which is a small and welcome minority.
What happens automatically
Three checks run without you lifting a finger:
- Windows checks the signature when you run the installer. If the file was altered by anyone after we built it, the signature breaks and Windows refuses it. You do not have to do this, and there is no warning to click past when a file is properly signed.
- Your browser checks the file as it arrives. A download that was tampered with in transit is rejected before it reaches your disk.
- The installer checks itself before it writes anything. It compares what it received against what we published and stops if they differ.
Put plainly: if a file gets past all three, it is the file we built. The hash on the release page is published so the claim is checkable, not because you are expected to check it.
If you want to check it yourself
Entirely optional. Two commands, and you never need them again.
# Does the file match what we published? Get-FileHash .\BeyondGpuManager-1.2.1-x64.exe -Algorithm SHA256
Compare that against the hash on the release page. If they differ, stop and tell us.
# Who signed it? Get-AuthenticodeSignature .\BeyondGpuManager-1.2.1-x64.exe | Format-List Status
Status should read Valid and the signer should be Beyond Digital
Labs. Anything else means the file did not come from us.
Signing is not in place yet, which is exactly why downloads are closed. We would rather hold every release than ask you to click past a publisher warning. See Security for where this stands.
Why we publish it at all
"Download our installer and click through the warning" is how a great deal of malware reaches people. We are not going to train you to do that. So the automatic checks do the work, and the evidence is published in the open for anyone who wants to audit the claim rather than trust it.