Update and Roll Back the Desktop Operator App

Check, download, install, relaunch, verify, and if necessary roll back a desktop release.

Written By 4ALL.LIVE

Last updated 12 days ago

Move between approved signed versions without interrupting production or losing workstation readiness.

Best for: Desktop administrators and lead operators.

Before you start

Uses the signed Tauri updater endpoint at updates.4all.live; IT policy may control update access.

  • Use a non-production event for commissioning.
  • Record the current build and workstation owner.
  • Prepare a documented fallback before making changes.
  • A maintenance window with no active event.
  • The current and target version documented.
  • A tested rollback installer and access to event configuration.

Installation and updates

  1. Open About/Updates and check for an approved release.
  2. Read release notes and compare OS, audio, local-model, and workflow impacts.
  3. Do not download/install while live; stop all events and local sidecars.
  4. Download the signed update and watch progress through download and install.
  5. Allow the app to relaunch; if automatic relaunch fails, close and restart manually.
  6. Confirm version, authentication, workspace access, audio devices, updater status, and local sidecar.
  7. Run a full test event and downstream caption check.
  8. If a release-critical regression occurs, collect logs, uninstall only as required by IT, install the last approved signed build, and repeat validation.

What success looks like: The target version relaunches and passes production preflight, or the previous approved version is safely restored.

Check your setup

  • Version changed exactly once.
  • No active event was interrupted.
  • Authentication and local resources remain valid.
  • The rollback path is documented and tested.

Troubleshooting

  • Update check fails: verify HTTPS/DNS/proxy access to the updater endpoint.
  • Download stalls: preserve evidence and retry on a stable network.
  • Relaunch fails: start manually after install completion.
  • Rollback blocked by schema/config change: contact support before deleting local data.

Security and operational notes

Important: Never delete application data, tokens, or local model caches as an unplanned rollback step. Back up and escalate first.