Repository navigation
Releases and Recovery
Rolling latest contains four installable packages: APP_LAUNCHSTATION.zip, APP_LAUNCHSTATION.psu, APP_LAUNCHSTATION-DS.zip, APP_LAUNCHSTATION-DS.psu. The DS variant includes the inherited DS34 controller drivers; use standard packages for ordinary PS2 controllers.
A standard install folder has LAUNCHSTATION.ELF, title.cfg, WLE-UPDATE-CA.PEM and BGM.ADP. The DS package has LAUNCHSTATION-DS.ELF and its own APP folder. Keep customized configuration and sidecar files when upgrading.
Choose Tools > System > Check for updates, directly below About Launchstation, in a build with native HTTPS support.
Update checks, commit ancestry comparisons and package downloads use saildot4k/Launchstation on GitHub. Builds compiled with the previous NathanNeurotic endpoint need one manual installation of the corrected matching ZIP/PSU package before they can use this update source. Preserve existing settings and custom sidecars when installing it.
If an older build reports TLS handshake: X509 ... (-9984), install the corrected ELF and the updated WLE-UPDATE-CA.PEM beside it from the matching package. The old bundled CA file lacks Sectigo Root E46, used by GitHub's API and website when checked on October 26, 2026. Replacing only the ELF leaves that outdated file in use. Back up a custom CA bundle before replacing or extending it. Certificate date errors also require the PS2's date and time to be correct; verification remains required.
A native check verifies ancestry so that older/divergent releases are refused. It selects a matching verified PSU, downloads it over trusted HTTPS and verifies the published SHA-256 digest, validates the packed ELF and stages replacement. It can install missing only CA/BGM sidecars from a verified four-file PSU; existing custom sidecars remain untouched. The updater reserves 100 KB of extra space and finishes writing verified replacement files before deleting and replacing the installed ELF and metadata. It creates no backups. The popup reports each update stage. Restart to execute the installed build.
An installed commit matching the published release reports Launchstation is up
to date. Could not verify update order indicates missing build identity or
a failed ancestry check, rather than a successful no-update result. Earlier
PS2BUILD releases omitted githash.h and identified their commit as local, so
they could not establish update order even when current. Install a matching
package from a corrected build and restart once; an ELF without its own commit
ID cannot safely update itself. Corrected builds report Update check needs
build information when this metadata is missing. Check the commit displayed
in Build information when diagnosing an affected install.
If .UPDATE or .PACKAGE remains from an interrupted attempt, the updater refuses to overwrite it. Preserve the original ELF and settings, inspect the incomplete staging files and resolve the conflict manually; do not delete them blindly. Old updater versions that expect the retired package format may need one manual new-package install.
The 2026-10-08 preserved USB-tested baseline remains available separately from the moving latest tag. A passing Actions build is not a guarantee of console acceptance; retain a known-good binary if you need rollback.
The site is generated from docs-site/; a documentation-only merge can update the rolling release's commit/build metadata without changing runtime source.
Record release tag, full commit SHA, package SHA-256, PS2 console model, device topology (especially multiple USB drives), controller type and the first observed failure stage. Avoid risky hot-unplugging or overwriting your last good app/settings backup.
LAUNCHSTATION repository · Live documentation · Release downloads
Maintained from documentation sources. Do not edit generated pages directly; propose changes in the source repository.