v1.0.5 · signed installer · Windows

The installer is the whole story.

One file. Standard office hardware. First chat in about five minutes from download to activation.

CHANNEL — production VERSION — v1.0.5 TARGET — Windows 10 / 11 · x64 SIGNATURE — Authenticode, self-signed (see SmartScreen note) SHA-256 — published at release, on the release page
01 — System requirements

Standard office hardware. No GPU required.

OSWindows 10 or 11
Memory8 GB RAM (16 GB recommended)
Disk2 GB free
MicrophoneOptional — voice is local; text works without it
GPUNot required
02 — Activation flow

What to expect.

Download and open

You download the installer. You open it. Windows may show a SmartScreen warning first — see below.

Give your email

Email auto-activation via Jade Seal. No license key to copy, no form to fight.

Start

Activation takes about nine seconds. You can start typing or talking immediately.

v1.0.5 closes the manual license-form bug from earlier builds — the legacy entry point is fixed in this release.

03 — SmartScreen

What you'll see, and why.

Windows shows a warning the first time you install, because the installer is signed by us and not yet through Microsoft's vendor signing program. The warning is expected. Click More info → Run anyway.

It goes away in v1.1, when the signing chain migrates to Azure Trusted Signing. We would rather tell you about the click-through than pretend it doesn't happen.

04 — Verify the installer

For the sovereign builder.

# hash check — compare against the value published on the release page Get-FileHash .\BlueSpark-Setup-v1.0.5.exe -Algorithm SHA256 # signature check — confirm the Authenticode signature Get-AuthenticodeSignature .\BlueSpark-Setup-v1.0.5.exe | Format-List

The SHA-256 value is published alongside each release artifact, never inside it. Same artifact, both channels: direct download and GitHub Releases.