March 3, 2026

Launcher Executable Compatibility (.exe, .bat, .cmd), Hidden Environment Access Key Fix, Installation Path Fix, Previous Install Location Detection


Desktop Launcher

Executable Format Support: .exe, .bat, .cmd

NEW - App Platform Settings - Executable extension dropdown

Game executables are no longer limited to .exe files. You can now configure .bat and .cmd files as your game's primary or secondary executable in the Dashboard, and the desktop launcher will handle them correctly.

Supported formats:

Format
Description

.exe

Standard Windows executable

.bat

Windows batch script

.cmd

Windows command script


Possible Previous Install Locations

NEW - App Advanced Settings - Possible Previous Install Locations

When a player opens the launcher and no local installation is found, the launcher will now search a list of possible previous install locations to try to locate an existing game installation. If found, the launcher links to the existing files instead of requiring a manual locate or full re-download / installation.

How it works:

  1. Configure possible install locations in App Advanced Settings on the Dashboard

  2. When the launcher starts and no installation is detected in the current app, it searches the configured paths for the app

  3. If a valid installation is found at any of the configured locations, the launcher uses it automatically as the installation path

  4. Launcher verifies the files, if everything is up to date, can launch the game immediately

Key details:

Aspect
Detail

Configuration

Set from App Advanced Settings in the Dashboard

Search behavior

Launcher checks each configured path sequentially

Fallback

If no previous install is found, the user has to locate the installation manually

Multiple locations

Support for multiple paths — useful for games previously on other drives

How to test it:

  1. Close the Desktop Launcher

  2. Press WIN + R and type %LOCALAPPDATA%\GameLauncher\Settings

  3. Delete the apps.json file

  4. Open the launcher again

If the launcher automatically detects the installation, the path you configured is working!


Fixed — Launcher Failing to Start .exe Executables (Converted from .bat)

An issue was discovered where the configured executable was actually a .bat file, causing a startup error (Launch failed) when the launcher attempted to run it. This has been fixed — the launcher now properly handles and starts the configured file regardless of its original format.


Fixed — Hidden Environments with Access Keys Not Appearing

Previously, even after entering the correct access key, the environment did not appear in the desktop launcher environment dropdown on some PCs. This behavior has been fixed and valid environments are now shown as expected.


Fixed — Incorrect Installation Path Resolution

Previously, if a user chose a custom directory such as C:\Game, the launcher incorrectly searched for the game inside C:\Game\Production. This has been fixed so the launcher uses exactly the path selected by the user without appending unintended subfolders.


Need Help? Check out our Help Center or join our Discord Community!

Last updated

Was this helpful?