Windows Installer (real progress + zero-click updates)
Two layered Windows install artifacts: a branded bootstrap stub that is the primary download and shows real byte progress and a measured time left while it downloads, verifies and installs, and the full NSIS installer kept for offline installs and as the engine auto-updates drive. Covers the fresh-install wizard, the zero-click update apply, and uninstall — including what uninstalling does on macOS and Linux, where there is no uninstaller and nothing prompts you about the data left behind.
On this page
What it is
TWO Windows install artifacts, layered (2026-08-15):
Omniscio-Installer-<version>.exe— the branded bootstrap stub (~2MB), the PRIMARY download. A fully custom frameless Omniscio window in the brand Aurora/glass language (soft aurora backdrop, the orb + OMNISCIO wordmark drawn LIVE so they're crisp at any DPI, an install location you can edit OR pick with a Browse button — it opens the native Windows folder chooser (preselecting your current folder) and appendsOmniscioto the folder you choose, so you never type a path — and one Install button; the exe + taskbar carry the orb icon): it checks the drive has enough free space first, then downloads the current release from the update feed with a real byte percentage AND a real measured time-left, verifies its SHA-512 against latest.yml BEFORE running anything, installs silently per-user with an honest "working" animation (no fabricated time), then shows a "You're all set" screen with a Launch button — the Discord-style one-click experience with zero Windows-wizard chrome. Failures (offline / checksum mismatch / installer error / a too-full drive) show a plain-English message with a Try Again button and a "Get the full installer instead" link. Its Windows file-properties metadata (product name, company, description, version) is generated from the samepackage.jsonthe Setup exe reads and compiled at packaging time, so right-click → Properties shows the same identity on both downloads rather than the blank panel it showed through 0.1.114.Omniscio-Setup-<version>.exe— the full NSIS installer (~450MB), no longer listed on the download page (since 2026-09-01 — visitors kept picking the slow download when the stub gives the same install). It still ships with every release: the stub's "Get the full installer instead" link reaches it for offline installs, and it is the engine the stub + auto-updates drive silently. From 2026-10-12 the Windows build no longer packs the native binaries of the platforms it cannot run on (macOS, Linux, Raspberry Pi, Windows arm64/ia32) nor the demo/test folders several published packages carry — 45.6 MB off the packed payload, with the macOS and Linux installs unchanged. Re-engineered 2026-08-14 from first principles: the old fake "bouncing" progress bar over an empty log (with copy apologizing that "that's normal") and the forced clicks on every auto-update are gone.
Where to find it
The installer lives on the Omniscio download page, where the branded bootstrap stub is the one Windows download. The full NSIS installer is no longer listed there; if the stub cannot finish, its "Get the full installer instead" link opens the release page that carries it. Updates arrive through the in-app update banner, and uninstalling goes through Windows "Add or remove programs".
How it behaves
What a FRESH install looks like (the full NSIS wizard)
Welcome — branded "Welcome to Omniscio" page (Omniscio sidebar art), two short sentences, Next. No license click-through page.
Who it's for — "all users" (needs admin) vs "only for me" (no admin needed; the default for a fresh per-user install).
Folder choice — pick the install location (deliberately kept so users can avoid OneDrive/locked folders — see the Mark Cebul incident in the installer contract).
Install with REAL progress — a determinate progress bar with live percentage and megabyte counts ("Unpacking files 65% (1187 / 1825 MB)...") over a visible log that narrates each step (unpack, file moves, shortcuts, registration) as it happens.
On a machine missing the Microsoft Visual C++ Runtime, this step ALSO offers to install it — an optional one-time item, since Omniscio already ships the copy it needs. Windows may ask for permission; choosing Yes finishes it. Setup never waits on that prompt for more than five minutes: if it goes unanswered the wizard carries on and the log says the runtime was skipped, with a note that it can be installed later.
Finish — "Run Omniscio" checked by default; a Safe Mode launcher shortcut is also created inside the install folder (runs the same exe with
--safe-mode).
What happens when Omniscio is already open
Running the manual installer while Omniscio is open works — it just asks first. The stub checks for a running Omniscio before it downloads anything, and once more right before it hands over to the silent setup. You get one question that names Omniscio and says exactly what to do: quit Omniscio from its tray icon, then click OK. The stub waits for it to go, installs, and starts Omniscio again from the Done screen — quitting it properly first is also what brings your sessions back after the restart. Cancel puts the window back on its Idle screen with nothing downloaded. If Omniscio is still open after a second ask, the stub says so plainly and installs nothing, instead of pretending it worked. Exactly one thing it will not do is force-close Omniscio for you: that would skip the app's own shutdown work, which is how sessions and file locks get lost.
The silent setup itself has its own running-app handling, and with nobody watching it a silent run
can end without installing a thing and still exit 0. So the stub no longer trusts a zero exit
on its own: after the setup finishes it reads the installed Omniscio.exe's file version and
reports a mismatch — with the "Get the full installer instead" fallback — rather than showing
"You're all set" over an install that did not happen.
What an AUTO-UPDATE apply looks like (zero clicks)
Clicking Restart Now on the update banner (app-update-notifications.md)
quits the app and runs the same installer with --updated:
- The welcome and folder pages are SKIPPED — it goes straight to the live-progress screen.
- An update upgrades the Omniscio that is already on the computer, where it already is — a
"just me" install stays a "just me" install in the same folder, and a leftover machine-wide
entry from an old copy cannot drag it into Program Files. That takeover is what locked a user
out of the app on 11/12, so the installer now decides from the copy it finds on disk: an install
for everyone still updates in place, and nothing creates a second copy (the installer contract's
install-mode-follows-the-install-that-exists). - When the install finishes, the completed page auto-advances and Omniscio relaunches itself — the user clicks nothing from "Restart Now" to the updated app being back.
- The quiet path is unchanged: an update that applies on app QUIT (the "Later" flow) runs silently with no window at all.
- The bundled server files (the
resourcestree, which carries the app bundle AND the hook scripts Omniscio runs) are staged beside the live copy and swapped in as one step, so an update can never leave a mix of files from two builds. If the live copy is momentarily busy, the old tree is left whole and the new one is copied over it rather than lost — and on the next launch Omniscio checks every module its own startup needs and says plainly, in one line, if any is missing.
When a silent update fails
An update applies as --updated /S with the old app already quit, so on success NSIS is what
puts the new copy back in front of the user (--force-run). On failure nothing does — and
nothing inside the installer can be made to.
That is measured, not assumed. Every failure route in the effective templates ends in a bare
Quit, and Quit terminates without running a callback: the locked-file retry loop bottom
(include/extractAppPackage.nsh → AbortExtract7za: Quit), the persistent "cannot close the
running app" case (include/allowOnlyOneInstallerInstance.nsh → MessageBox … /SD IDRETRY then
Quit), and include/installUtil.nsh (SetErrorLevel 2 + Quit). .onInstFailed runs when an
install SECTION aborts, and no template Abort sits inside the install section — so a
.onInstFailed handler compiles and can never fire. The repo's patched templates must not be
forked for this; a handler there would be dead code certified by a green test.
What the user gets instead is the in-app net: if the relaunched or half-applied tree cannot
start, startup-boot-health.ts counts the starts that never reached a window, and the update
rescue offers a route to a working version (see
app-update-notifications.md § When the app cannot start). The
rescue also detects a shared, all-users install it cannot write to up front and says to download
the latest installer and run it as an administrator.
The cases the installer itself cannot cover — antivirus quarantining it, a file it cannot
replace, a refused elevation prompt, a spawn that never starts — are now covered from the app
side. Every handoff to the installer (Restart Now, an idle auto-install, a quit-time install, a
hard exit, and the rescue's Install the fix) first starts a small watchdog
(installer-relaunch-watchdog.ts) that outlives the app. It is a detached, windowless
PowerShell — the one spawn shape measured not to pop a console — and it:
- waits for the app to exit, then for the installer process (named from the pending file the updater downloaded) to finish, with a twenty-second settling window after it goes;
- counts that budget in polls it actually observed, and resets it whenever the installer is using the CPU. So a machine that slept, a shutdown that overran, or an installer still unpacking is never mistaken for a stalled one;
- ends a stalled installer — one still running after ten observed minutes of making no progress — and only for a handoff that must bring the app back (the idle auto-install, the pre-window fatal paths and the startup rescue's Install the fix, where the alternative is a machine held closed by a wizard nobody is standing in front of). It confirms the process actually died before going on, and if it did not, it reports the failure instead of launching an app into a live installer. A handoff made while a user quit never ends or races a running installer;
- then starts the installed exe if no app process started after the original died, retrying while the exe is briefly absent and confirming that a new app process actually appeared. That is the new build when the install landed and the old one when it did not, so the user is never left with nothing; on the old build the next boot says plainly that the update did not install (the first failed attempt) and the won't-stick detector reports the repeat;
- stays out of the way after a successful quit-time apply: any handoff made while a user quit is in flight — the quit itself, or the force-exit backstop of a shutdown that overran — asks it to relaunch only if the on-disk version did not change, so someone who chose Quit stays quit;
- arms nothing at all when there is no known installer file, so an ordinary quit can never become a surprise relaunch.
The install itself stays visible, exactly as the progress-display contract requires: an update skips the welcome and folder pages, shows the live progress screen, and relaunches from the finish page without a click.
The mechanism and its invariant are in the app-update apply contract, invariant I16.
Choosing the all-users option on the wizard's scope page is the only way to reach the non-writable state — the default is a per-user install, and an update never chooses all-users.
Uninstall
Windows "Add or remove programs" → Uninstall. On a real uninstall (not an update) it asks
whether to ALSO delete your data (sessions, settings, caches) — defaulting to No so a
reinstall keeps everything. Data moved via the DATA_DIR override must be removed by hand
(the prompt says so).
Uninstalling does NOT remove your sessions' working copies. An isolated session works in a
git "worktree" — a private copy of your project — created in a <your-repo>-worktrees folder
beside the repo it belongs to, not in Omniscio's data directory. The uninstaller cannot see
that folder, so every worktree survives it, and each one until it is removed still holds a
branch and any uncommitted changes that session had. That is deliberate (they belong to your
repos, not to Omniscio, and a reinstall should find them intact) but it means a machine you are
trying to reclaim disk on will keep that space until you clear the <repo>-worktrees folders
yourself — one per project you have run isolated sessions against. Delete a folder only after
checking that its branch's work has landed or been saved; anything committed only there lives
nowhere else.
On macOS and Linux there is no uninstaller, and no data prompt either. Both platforms ship as a drag- or double-click-to-run artifact, so removing the app is a manual action and nothing else is installed alongside it:
- macOS — the
.dmgis a drag-install; uninstalling is moving Omniscio from Applications to the Trash. - Linux — the AppImage is self-contained; uninstalling is deleting the
.AppImagefile you run. (Make it executable first withchmod +x; that is the whole install.)
Your data is left behind on every platform, and nothing prompts you about it. Sessions,
settings, caches and logs live in a data folder OUTSIDE the app — ~/Library/Application Support/omniscio
on macOS, ~/.config/omniscio on Linux, %APPDATA%\omniscio on Windows (data-folder-recovery.md
has the full picture, and Settings → General → Data Folder shows the exact path on your machine).
The Windows uninstaller is the only one that ever offers to clear it; on macOS and Linux you delete
that folder yourself. That matters beyond disk space: the EULA makes uninstalling the act of
terminating the agreement and says your locally stored data remains on your device until you delete
it, so a mac or Linux user who uninstalled has ended the agreement and still holds every session.
Session working copies are separate again. The <repo>-worktrees folders described below sit
beside your repos and survive uninstall on every platform, for the same reason.
Related
App Update Notifications covers the in-app update banner whose Restart Now button drives the zero-click apply described here. Portable Backup covers the one-file encrypted export and import that is separate from the uninstall prompt's offer to also delete your data. Claude Code on Windows is the guide to getting Claude Code and Omniscio running on Windows.
Last verified 2026-10-22