Almost there.

Three steps, and one surprise worth expecting

1. Find the file

   BytesnareDesktop-0.1.0-arm64.msi, 1,601,536 bytes, in your Downloads folder.

2. Open it

   Double-click. Windows will ask you to confirm that you meant to run an installer.

3. Expect a warning

   You will see the screen below. Read the next section before you decide what to do about it.

Windows will warn you about this file

We would rather you heard it from us than met it alone, so here is what is coming and why.

This build is signed, and you may still see that screen. A signature is not a reputation. Microsoft’s own guidance is that a validly signed application is still “flagged as unrecognized until reputation accumulates”, which takes weeks and hundreds of installs. What the signature changes is the line that matters: where an unsigned build says Unknown publisher, this one names Triop AB. If it says anything else, do not run it.

We are telling you this in advance because a security product that acted surprised by its own warning screen would not deserve the install.

Check the bytes before you run it

Every file we publish has its SHA-256 printed here and in an artifact manifest listing what the package contains and the hash of each file inside it. Verify before you install:

Get-FileHash .\BytesnareDesktop-0.1.0-arm64.msi -Algorithm SHA256

c284048844239cfed6d77ac676c654f307785efa0dd313bce86fa2f3d20fdc27

A signature tells you the file came from us. The hash tells you it is the exact build this page is describing. They answer different questions and it is worth having both.

While that downloads

What you are installing is the desktop application — the window onto an endpoint’s status — and not the engine. On its own it will tell you it cannot reach a service, because there is no service on the machine to reach. The install page has the full account of what goes on the machine and what comes off again, and what it does not do is the honest half.