> ## 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.

# Player files and downloads (Windows GUI setup)

> Where Pickcel player installers come from on an on-premise server, their download URLs, and how BrightSign is patched with the server address

Player installers are **not** bundled in the Windows installer. They are copied out of the `pickcel/backendv5` image into the workspace at `dist/public/players/` during setup, and refreshed on update.

> [!NOTE]
>
> **Dashboard only** installs skip this entirely — there is no backend image, so no player files.

## Download URLs

Replace `<server>` with your server's IP or domain. If you set a custom **Public port**, it goes straight after the host — `10.0.0.5:2001`.

| Player | Download URL | Config file |
| :- | :- | :- |
| Windows | `http://<server>/players/core/windows/pickcel-digital-signage-v<version>.exe` | — |
| Tizen / Samsung | `http://<server>/players/samsung/Signage.wgt` | `sssp_config.xml` |
| LG | `http://<server>/players/core/lg/com.lg.app.signage.ipk` | `manifest.json` |
| BrightSign | `http://<server>/players/core/brightsign/autorun.zip` | `app.json` |

> [!WARNING]
>
> The Windows player filename carries a version that tracks the backend image and changes after a player refresh — it is not a fixed URL. List `<workspace>\dist\public\players\core\windows\` to get the current filename before sending anyone a link.

## Refreshing them

Player and app files come down with the backend image, so they update when the images do. On the dashboard, **Check Updates** → **Refresh Apps/Players** re-syncs them from the current backend image without changing any image version.

> [!NOTE]
>
> The Linux CLI equivalent is `pickcel-cli --online --refresh-static`.

## BrightSign server patching

`autorun.zip` contains a `config.json` that must point at your server. The app patches it automatically:

* **When** — after setup, and again after any IP, protocol or port change
* **What** — `server` and `updateUrl` are set from `SERVER_NAME` in the workspace `.env` (including the custom port, if set); `protocol` is set to `http` or `https`

The LG `manifest.json` is patched the same way, with the full server URL.

### Verify the patch

From PowerShell on the server:

```powershell theme={null}
$zip = "C:\ProgramData\Pickcel\pickcel-server\dist\public\players\core\brightsign\autorun.zip"
$tmp = Join-Path $env:TEMP "bs-check"
Expand-Archive -Path $zip -DestinationPath $tmp -Force
Get-Content "$tmp\config.json"
```

On Linux, the same check is a one-liner:

```bash theme={null}
unzip -p <workspace>/dist/public/players/core/brightsign/autorun.zip config.json
```

Expect `server` to match your current server address. If it shows an old address, re-apply the config in **Settings** or run an update — either re-patches the zip.

***

## Related

> **[Keeping it up to date](/on-premise/windows-gui-setup/updates)**
>
> Image updates and Refresh Apps/Players.

> **[Troubleshooting](/on-premise/windows-gui-setup/troubleshooting)**
>
> Apps/players 404, BrightSign pointing at the wrong IP.

> **[Quick reference](/on-premise/windows-gui-setup/reference)**
>
> Ports, containers, workspace contents.

> **[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.