JM Tech Power

Guides

How to check a download's SHA-256 on Windows, macOS and Linux before you run it

← All articles Email RSS Atom

A SHA-256 checksum is a 64-character fingerprint of a file. Change one byte and the fingerprint changes. If the fingerprint of your download is the same as the published one, you have the same file. Here is how to compare them, using the JJ Bot installer for Windows as the example. The commands work for any file that comes with a published SHA-256.

1. Get the published checksum

  1. Open the JJ Bot page and press Download for Windows (JJBot-Setup.exe). Do not run the file yet.
  2. Below the download buttons, find the small line that starts with JJBot-Setup.exe. It gives the size, then SHA-256 and 64 characters. Copy those 64 characters.

In the commands below, put what you copied in place of PASTE_HASH_HERE. They expect the file in your Downloads folder.

2. Compare it on your computer

Windows (PowerShell)

cd $HOME\Downloads
(Get-FileHash .\JJBot-Setup.exe).Hash -eq 'PASTE_HASH_HERE'

True means the file matches. False means it does not. Get-FileHash uses SHA-256 unless told otherwise, and -eq ignores upper and lower case.

Windows (Command Prompt)

cd /d %USERPROFILE%\Downloads
certutil -hashfile JJBot-Setup.exe SHA256

This prints the checksum for you to compare by eye. Keep SHA256 at the end so you get the right kind of checksum.

macOS (Terminal)

Useful when you download on a Mac to install on a PC. Keep the two spaces before the file name.

cd ~/Downloads
echo 'PASTE_HASH_HERE  JJBot-Setup.exe' | shasum -a 256 -c -

Linux (terminal)

cd ~/Downloads
echo 'PASTE_HASH_HERE  JJBot-Setup.exe' | sha256sum -c -

On both macOS and Linux, a match prints JJBot-Setup.exe: OK.

3. If it does not match

  • Check which file you tested. A second download is often saved as JJBot-Setup (1).exe, so you may be testing an older one.
  • Check what you pasted. It must be all 64 characters, with no spaces inside.
  • Start again. The installer is rebuilt from time to time, and its checksum changes with it. Delete the file, reload the page, then download and copy again.
  • Still different? Do not run it. Tell us through Feedback (no account needed), with the checksum you got.

What a match does not tell you

  • It does not prove that software is safe. The file and its checksum come from the same website, so a match shows that your copy is complete and unchanged, and nothing about who wrote it.
  • It is not a code signature. JJBot-Setup.exe is not code-signed yet, so Windows may still warn you when you open it.
  • It covers that one file. The installer downloads the newest JJ Bot when it runs. The zip and the one-line install commands have no checksum on that page.

Installing projects with jm? It checks for you

When you install a project from this site with the jm command line (jm proj install NAME), jm compares the download with the SHA-256 stored for that release before it unpacks or runs anything:

  • A match prints Checksum OK and the first 16 characters.
  • A mismatch prints Checksum mismatch, removes the download and stops.
  • A release with no stored checksum gets a note that it could not be verified, and the install goes on. To refuse those instead, use jm app install NAME --require-hash. In jm 2.12.0, jm proj install does not take that option.

Projects hosted on another website are not checked: jm gives you the link to download from.

Windows command references on Microsoft Learn: Get-FileHash and certutil. Written 22 November 2026.

Comments (0)

No comments yet. Be the first to comment!