> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pickcel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Keeping the installation up to date (Windows GUI setup)

> The two independent update mechanisms in the Pickcel On-prem CMS Manager: installer updates and Docker image updates

There are **two independent update mechanisms**. Updating one does not update the other.

| | Updates | Triggered from |
| :- | :- | :- |
| **Installer update** | The desktop app itself | Refresh-arrow button in the window header |
| **Docker image update** | The CMS containers | **Check Updates** on the dashboard |

***

## 1. Installer update — the desktop app

The refresh-arrow button in the window header — tooltip **Update Installer** — checks the feed for a newer build of the manager.

![Installer update dialog reporting the app is up to date](https://mintcdn.com/pickcel-92c6a68f/OpfNjz-SPUbEFD8a/images/on-premise/windows-gui-setup-09-installer-update.png?fit=max\&auto=format\&n=OpfNjz-SPUbEFD8a\&q=85\&s=d5832f308c9bdbe151bb5d26c227fd88)

| State | What you see |
| :- | :- |
| A newer build exists | **"Installer update available"**, with the current and new version. Accepting downloads the `.exe`, runs it silently and quits the app — relaunch from the Start menu when it finishes. |
| Already current | **"You're up to date"**, with the current version. |
| Offline / feed unreachable | An error, but only on a **manual** check. The automatic check at launch stays silent instead. |

Nothing about your deployment changes: the workspace, containers and data are untouched.

> [!NOTE]
>
> Linux equivalent: `sudo pickcel-cli update-cli` (add `-y` for non-interactive).

### Which release channel is this build on?

Press **Ctrl + Shift + U** at any time. A toast reports the environment and the feed URL baked into that installer.

![Ctrl+Shift+U toast showing the build environment and installer update source URL](https://mintcdn.com/pickcel-92c6a68f/OpfNjz-SPUbEFD8a/images/on-premise/windows-gui-setup-10-update-source.png?fit=max\&auto=format\&n=OpfNjz-SPUbEFD8a\&q=85\&s=afe21fb8b79e85f07fff1bce2e12c4ff)

| Environment | Base URL |
| :- | :- |
| Dev | `https://dev.internal.pickcel.com/players/onprem-cli/` |
| Test | `https://test.internal.pickcel.com/players/onprem-cli/` |
| Stage | `https://stage.pickcel.com/players/onprem-cli/` |
| Prod | `https://console.pickcel.com/players/onprem-cli/` |

Each feed serves an `exe-version.json` manifest:

```json theme={null}
{ "version": "1.0.9", "file": "pickcel-on-prem-setup-1.0.9.exe", "environment": "dev" }
```

> [!WARNING]
>
> Check this before troubleshooting a customer install. A build only ever updates from its own feed, so a customer on a `test` build will never receive `prod` releases. Anything other than `prod` is a pre-release build.

***

## 2. Docker image update — the containers

**Check Updates** on the dashboard compares the images your workspace is pinned to against Docker Hub.

What happens, in order:

1. Reads the image versions recorded in the workspace
2. Tests Docker Hub connectivity
3. **If Docker Hub is reachable** — fetches the latest tags and compares them
   * Something behind? An **Update to Latest (Online)** dialog lists each image with its current and latest version. Confirm to pull and restart.
   * Everything current? You get **"All images are up to date!"** and the adjacent button becomes **Refresh Apps/Players**.
4. **If Docker Hub is not reachable** — falls back to an **Update from TAR Files (Offline)** dialog, where you supply newer TAR files instead. Download the latest **[amd64.zip](https://console.pickcel.com/players/onprem/current/amd64/amd64.zip)** for them.

> [!NOTE]
>
> **Refresh Apps/Players** re-syncs the app and [player files](/on-premise/windows-gui-setup/players) from the current backend image without changing any image version. Safe to run when static assets look stale; it is not an upgrade. The Linux CLI equivalent is `pickcel-cli --online --refresh-static`.

Images tracked: `webserver`, `backend`, `mongo`, `console`, `admin`, `libreoffice` (when the Office app is enabled) and `dashboard` (when a dashboard server is installed).

> [!TIP]
>
> An update also re-patches the BrightSign `autorun.zip` and LG `manifest.json` with the current server address — see [Player files](/on-premise/windows-gui-setup/players).

> [!WARNING]
>
> Updating images restarts the containers. Do it in a maintenance window — screens lose their connection to the CMS while the stack comes back up.

***

## Related

> **[Dashboard operations](/on-premise/windows-gui-setup/dashboard-operations)**
>
> The rest of the dashboard's buttons.

> **[Resetting the installation](/on-premise/windows-gui-setup/resetting)**
>
> When an update leaves things in a bad state.

> **[Troubleshooting](/on-premise/windows-gui-setup/troubleshooting)**
>
> Symptoms and fixes.

> **[All setup paths](/on-premise/windows-gui-setup)**
>
> Back to the scenario picker.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.