Install & Update

Install the matching app package and preserve your existing configuration and customized files.

Standard rolling package

mc0:/
└── APP_LAUNCHSTATION/
    ├── LAUNCHSTATION.ELF
    ├── title.cfg
    ├── BGM.ADP
    └── WLE-UPDATE-CA.PEM

Both standard ZIP and PSU packages contain those four files. DS34 controller packages use APP_LAUNCHSTATION-DS with LAUNCHSTATION-DS.ELF. The ELF alone can run the dashboard, but the packaged updater CA supports native verified HTTPS updating; BGM.ADP is optional for a standalone installation.

Choose your installer

Download the matching ZIP/PSU from Downloads & Releases. Extract the ZIP app folder to readable storage or use the File Browser PSU Paste command to install a PSU on a memory card. Keep a separate copy of your previous working ELF, settings and customized sidecars.

Configuration

LAUNCHSTATION retains classic LAUNCHELF.CNF support and its dashboard settings store. The saved path can be configured next to the ELF, in a selected folder or on a memory-card SYS-CONF location. See Configuration.

Google Drive remains opt-in

Linking needs no setup files: choose Link Google Drive and enter the shown code at google.com/device. Launchstation then stores a refresh token in WLE-CLOUD.TOK. Do not publish your token or include it in a bug report. Google Drive is optional for ordinary files and local MMCE history.

Native updates and rollback

The current in-app updater checks release ancestry, downloads the matching standard or DS34 PSU, validates the published SHA-256 and ELF, stages replacement and keeps a .BAK copy of the preceding executable. It restores missing only CA/BGM sidecars from the verified four-file PSU without overwriting customized ones. Existing interrupted .UPDATE or .PACKAGE artifacts require manual resolution. Restart LAUNCHSTATION to use installed code; older clients may need a one-time manual package update.

Preserve a hardware-tested baseline

If a newer rolling build regresses on your console, retain the 2026-10-08 USB-tested baseline and collect hardware details before retrying. Compiled CI success is distinct from successful console validation.