Checking a download

You do not have to do anything. The checking happens by itself, the same way it does for any properly published software. This page is here 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 file when you run the installer. If anyone altered it after we built it, Windows notices and refuses to run it. You do not have to do anything for this to happen.
• 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 reference code on the release page is published so that claim can be checked, not because you are expected to check it.

If you want to check it yourself

Entirely optional. One command in Windows PowerShell, and you never need it again. Right click the Start button, choose Terminal, go to the folder you downloaded into, and paste this:

# Does the file match what we published?
Get-FileHash .\BeyondGpuManager-1.2.1-x64.exe -Algorithm SHA256

It prints a long string of letters and numbers. Compare it against the reference code on the release page. They should be identical. If they are not, stop, do not run the file, and tell us.

Nothing is open for download yet, because the applications are still in development. This page is here so you know what will happen when they are. See Security for where things stand.

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.