> Source: Onevium official documentation > Article: Install and update Onevium > Original URL: https://onevium.com/docs/installation > Language: English > Updated: 2026-09-09 > Applies to: 1.1.22 > Feature status: Released --- # Install and update Onevium Choose the right desktop release, open the app, and verify an update without losing track of your work. ## Choose an official installer Open the [Onevium 1.1.22 release](https://github.com/Onevium/Onevium/releases/tag/v1.1.22) and choose an installer under Assets. These are the formats actually published for this version. | System and architecture | Package | | ----------------------- | --------------------------------------------------------------- | | Apple silicon Mac | `Onevium-1.1.22-arm64.dmg`; a matching `.zip` is also available | | Intel Mac | `Onevium-1.1.22-x64.dmg`; a matching `.zip` is also available | | Windows x64 | `Onevium-Setup-1.1.22.exe` | | Linux x86\_64 | `Onevium-1.1.22-x86_64.AppImage` or `Onevium-1.1.22-amd64.deb` | | Linux arm64 | `Onevium-1.1.22-arm64.AppImage` or `Onevium-1.1.22-arm64.deb` | Version 1.1.22 has no Windows arm64 or RPM installer. `latest*.yml` and `.blockmap` files support the updater; they are not installers. ## Check your system and existing work - **Mac:** open Apple menu → About This Mac. Choose arm64 for Apple M-series chips and x64 for Intel. - **Windows:** open Settings → System → About and inspect System type. This version's installer targets x64. - **Linux:** run `uname -m`. `x86_64` maps to x86\_64/amd64; `aarch64` or `arm64` maps to arm64. On Debian/Ubuntu, `dpkg --print-architecture` also identifies the DEB architecture. Before upgrading, save files and finish the current task or record where to resume. An ordinary update does not require deleting app data. See [settings and data](https://onevium.com/docs/settings-and-data) before making a backup. ## Install and launch ### macOS 1. Download the `.dmg` for your chip and open it. 2. Drag Onevium into Applications. If replacing an existing copy, quit it first and confirm the replacement. 3. Launch Onevium from Applications, not from the mounted disk image. The `.zip` is an alternative distribution for the same architecture; normally prefer the `.dmg`. ### Windows Run `Onevium-Setup-1.1.22.exe`, complete installation, and launch Onevium from the Start menu. Save your work before updating rather than continuing in the old window during installation. ### Linux: AppImage Open a terminal in the directory containing the downloaded file. For x86\_64: ```bash chmod +x Onevium-1.1.22-x86_64.AppImage ./Onevium-1.1.22-x86_64.AppImage ``` For arm64: ```bash chmod +x Onevium-1.1.22-arm64.AppImage ./Onevium-1.1.22-arm64.AppImage ``` AppImage runs directly without a package-manager installation. ### Linux: Debian / Ubuntu Run the appropriate command in the installer directory: ```bash sudo apt install ./Onevium-1.1.22-amd64.deb ``` For arm64, replace the filename with `Onevium-1.1.22-arm64.deb`. Launch Onevium from the application menu afterward. On first launch, complete the app's account sign-in or license activation. Model access is a separate step; see [Connect providers](https://onevium.com/docs/providers). ## Check for and install updates Open **Settings → General**, locate the Onevium version row, and click **Check for Updates**. | What you see | Next action | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | Download & Install | Start the download and wait for it to finish. Restart when you are ready to end the current work | | Restart to Update | Save your work, restart, then check the version again | | Download Manually / View Release | Open the official release, download the correct package, quit the old app, and install the update | | An update error | Retain the error details. You can download manually from the official release; an error does not mean the update was installed | The available action depends on the running environment and update state. Do not infer that updates are always automatic or always manual from the operating system alone. ## Verify the running version After reopening, check **Settings → General** for the running version. Open an existing project and conversation to confirm files and history are visible. A working app window does not establish model connectivity; complete the [text and tool checks](https://onevium.com/docs/providers#check) too. ## Troubleshoot installation | Symptom | What to do | | ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | The installer will not run | Check system, architecture, and the complete filename. Do not run `.blockmap` files or update manifests | | AppImage lacks execute permission | Run the `chmod +x` command above in the file's directory | | AppImage reports a missing runtime library | Record the named library. On a supported Debian/Ubuntu environment, the matching DEB may be an alternative; dependencies differ between distributions | | The old version still appears | Confirm you launched the installed application rather than another copy in Downloads | | The system blocks launch | Verify the official release source, then use the operating system's per-app approval flow. Do not disable system protection globally | | Conversation history is missing | Check the system user and app copy first. Do not overwrite the old data directory with an empty one | ## Next steps [Connect a model provider](https://onevium.com/docs/providers), then follow [your first task](https://onevium.com/docs/getting-started) to open a project and verify the workspace.