Installing OrOrbit
If your OS shows a warning, that's expected for early builds. Here's why — and how to get past it.
Why aren't OrOrbit applications signed?
Thanks for being one of the early users!
Code signing isn't free — Microsoft requires paid certificates from authorized vendors. Until OrOrbit grows enough to fund one, our installer will trip a SmartScreen warning the first time you run it.
The good news: signing only proves who published the installer, not what's inside. OrOrbit will be source-available under the Elastic License 2.0 at launch — you'll be able to audit every line that runs on your machine.
Windows
Two clicks past the warning and you're in.
Run the downloaded .exe.
When the blue "Windows protected your PC" popup
appears, click More info, then
Run anyway. Approve the standard UAC prompt and
the installer takes over from there.
Auto-updates inside the app work the same way — you'll see the UAC prompt each time, but no SmartScreen popup after the first install on the same machine.
Smart App Control
Windows 11's Smart App Control (SAC) blocks unsigned installers outright with no bypass — and SAC is the future of Windows app trust, so this matters. It's opt-in on fresh Windows 11 installs and most users today don't have it on, but adoption is climbing.
If SAC is enabled on your PC, you have two options: disable it (a one-way toggle — you can't turn it back on without reinstalling Windows) or wait for OrOrbit to ship signed builds. The fix is on our roadmap; until then, the SmartScreen click-through path above only works for users without SAC.
Verify your download
Optional but recommended. Each release publishes a
SHA256SUMS.txt
file alongside the installers; compare your downloaded file's hash
against the entry in there.
certutil -hashfile OrOrbit_x.x.x_x64-setup.exe SHA256