Adding Standalone Windows Games, Executables, and Shortcuts

Not every Windows game comes from a storefront that LaunchBox can scan. Older PC games, fan games, freeware, source ports, portable titles, and locally installed programs can all be added manually while still using LaunchBox metadata, media, playlists, play tracking, and game-management features.

Choose the correct launch target

A Windows game folder may contain several executables. Use the same target that produces a successful launch outside LaunchBox.

• Game executable (.exe): use this when the game starts directly and does not require a separate launcher.

• Launcher executable: use it when it performs required sign-in, patching, configuration, mod selection, or prerequisite checks.

• Windows shortcut (.lnk): a good choice when the shortcut already contains the required target, arguments, or Start in folder.

• Batch file (.bat or .cmd): useful when several commands, a specific working folder, mounting, or companion programs are required.

• Protocol address: storefronts and other launchers can use targets such as steam://... instead of a file. Enter one directly in Application Path only when you know the launcher's supported URI.

Test outside LaunchBox first

1. Start the intended executable, shortcut, or batch file from Windows.

2. Confirm that the game reaches its menu and can exit normally.

3. Note any required launcher login, command-line arguments, administrator prompt, mounted media, or unusual startup folder.

LaunchBox can reproduce a known-working launch, but it cannot repair an incomplete installation, missing runtime, broken mod, invalid license, or launcher account problem.

Add one game manually

1. Select Add in LaunchBox to open the Add Game window.

2. On Metadata, enter the title and set Platform to Windows. A custom platform is also fine if its Scrape As value is Windows.

3. Select Launching.

4. Set Application Path to the executable, shortcut, batch file, or supported protocol address that starts the game.

5. Enter Application Command-Line Parameters only if the target requires them.

6. Under Launching > Emulation, leave Use an emulator to play this game (primarily for console games) cleared for a native Windows program.

7. Search the LaunchBox Games Database if a matching Windows release exists, review the match, add any desired images or media, and save.

8. Select Play and confirm the launch.

When emulation is enabled, LaunchBox treats Application Path as the ROM file and disables the native application's command-line and configuration fields. That is not the correct setup for an ordinary Windows executable.

Drag-and-drop import

You can drag files or folders from File Explorer onto the main LaunchBox window. For executables, Windows shortcuts, batch files, media, and other items Windows can launch directly, choose None of the Above when the wizard asks What type of game files are you importing? Then select Windows as the platform and review the final game list.

Do not choose ROM Files for native Windows games; that route is designed to associate imported files with an emulator. A typed protocol address is not a file that can be dragged from Explorer, although a Windows shortcut containing that address can be imported.

Application Path and relative paths

Launching > Application Path is the target LaunchBox starts. File-based imports store paths in LaunchBox's path format, which can be relative to the LaunchBox folder. The manual editor also accepts a valid relative path or an absolute path.

For example, a game stored inside a portable LaunchBox installation might use:

Games\Windows\Example Game\ExampleGame.exe

Windows folder separators must be preserved. A relative path helps only when the target moves with the same LaunchBox folder structure. Games installed elsewhere, shortcuts with absolute targets, launchers, registry entries, services, and save folders may still be machine-specific.

If a game or drive moves, correct Application Path in the game editor. For a planned bulk move, use LaunchBox's ROM/file path-changing tools where applicable and verify a sample before changing the entire platform. Directory monitoring can update paths for some detected file moves, but it should not replace a backup or migration plan.

Command-line parameters

Put switches and arguments in Application Command-Line Parameters, not inside the Application Path field. Preserve quotation marks required around values containing spaces, use syntax documented by the game or launcher, and test one change at a time.

If a .lnk shortcut already contains arguments, begin with the LaunchBox parameter field empty. Adding a second copy can duplicate or conflict with the shortcut's embedded arguments.

How the working directory actually works

LaunchBox does not provide a separate working-directory field for a native game's primary application. When it starts a normal file target, LaunchBox automatically sets the working directory to the folder containing Application Path.

For D:\Games\Example\Example.exe, the working directory is therefore D:\Games\Example. This is suitable for most games.

If a game works from a shortcut but fails when its executable is selected directly, use the shortcut and check its Windows Target, arguments, and Start in values. If a special startup sequence is needed, use a trusted batch file that explicitly changes directory before starting the game. Keep that shortcut or script in a stable location because LaunchBox launches the stored item itself.

Windows shortcuts

LaunchBox can launch and import .lnk files through Windows shell handling. A shortcut may contain a target, arguments, a Start in folder, and an icon. Compatibility settings can also apply to the target executable through Windows.

• Test the shortcut by double-clicking it before adding it.

• Keep the shortcut in a stable location after LaunchBox stores its path.

• Remember that copying the shortcut does not copy its target.

• Inspect its properties after moving computers; the target and Start in paths may be absolute.

If a shortcut points to a storefront protocol, keep the required client installed and signed in.

Batch files and other scripts

A batch file can prepare an environment, start a companion tool, mount media, select a mod, or run cleanup after the game closes. A carefully written wrapper can use cd /d to choose a working folder and start /wait when later commands must wait for the game.

PowerShell .ps1 files should not be assumed to execute merely because their path is selected; Windows commonly associates them with editing rather than direct execution. If PowerShell is genuinely required, use an explicit, trusted launcher or batch wrapper and do not weaken system-wide security settings just for LaunchBox.

Storefront clients and duplicate entries

A manually added game can still depend on Steam, GOG Galaxy, the EA app, Ubisoft Connect, Epic Games Launcher, or another client. Using the official shortcut or supported protocol can preserve authentication, cloud saves, overlays, ownership checks, and update behavior.

If LaunchBox already imports the title through a supported storefront connection, adding it manually can produce a second entry. The entries may have different targets, metadata, play counts, installed states, and additional versions. Compare their paths and storefront identifiers before combining or deleting anything.

Portable Windows games

Storing a game beneath LaunchBox\Games\Windows\Example Game can make the application path portable with LaunchBox. It does not guarantee that the game itself is portable. Check for dependencies on:

• Registry entries or installed services.

• AppData, ProgramData, Documents, or Saved Games.

• DirectX components, Visual C++ redistributables, .NET, PhysX, OpenAL, Java, drivers, or anti-cheat.

• A storefront client, machine-specific activation, or external mod manager.

Copying an installed program folder does not automatically make the game portable.

Installers, configuration tools, and alternate launches

Install a game through its documented setup process, launch it once outside LaunchBox, and use the installed game's executable or shortcut as the primary application. Do not make setup.exe the main launch target.

In the game editor, use Additional Apps for utilities that should remain attached to the game, such as a configuration program, mod manager, dedicated server, level editor, alternate launcher, or clearly labeled offline installer. Use Additional Versions when the item is another playable build or edition.

An Additional App includes an application name, Application Path, Command-Line Parameters, and options including:

• Automatically Run Before Main Application

• Automatically Run After Main Application

• Wait for Exit, available for an app that runs before the main application

Wait for Exit waits for the launched process for a limited period; it is not a guarantee that every launcher, child process, or long-running setup task will finish before the game begins. Test automatic chains carefully. Never set an interactive installer or uninstaller to run automatically.

Compatibility and administrator privileges

Configure Windows compatibility properties on the actual executable, or retain a shortcut that is already known to work. Older games may require compatibility mode, high-DPI adjustments, or administrator privileges, but apply them only where necessary.

For missing DirectX, Visual C++, .NET, PhysX, OpenAL, or similar dependencies, use the game's installer, publisher, or runtime vendor. Do not download individual DLL files from unknown sites.

Installed status

The Installed field is a nullable library status for manually managed entries. Marking a native game Installed does not install it, and clearing the field does not uninstall it. Supported storefront integrations can update installed status using their identifiers and installation data, which is different from a manually maintained field.

Installed status does not validate that a manual Application Path is correct. Test Play and verify the file separately.

Removing a game is not uninstalling it

Deleting a native Windows game entry removes it from the LaunchBox library; it does not run the game's uninstaller. LaunchBox may also offer to delete associated media, depending on the delete prompt and your setting, so read the confirmation carefully.

The separate option that permits deletion of ROM files applies to emulated game paths. A correctly configured native Windows executable, with no emulator assigned, is not treated as a ROM-deletion target. Even so, keep backups and confirm that emulation is disabled before removing an entry whose path points at valuable files.

Uninstalling through Windows or a storefront can have the opposite result: the LaunchBox entry can remain while its executable no longer exists.

Moving or backing up a Windows game

A complete migration may require more than the installation folder:

• LaunchBox data and locally stored media.

• The game installation or portable folder.

• Save and configuration folders.

• Shortcuts, batch files, mods, launchers, and Additional Apps.

• Required runtimes, storefront clients, offline installers, and license information.

After moving computers, first make the game or shortcut work directly in Windows. Then correct any absolute Application Paths and retest through LaunchBox.

Common problems

• Play does nothing: verify that Application Path exists, or that the protocol's client is installed; also check Windows Security quarantine history.

• Application path was not found: reconnect the drive or edit the path. A moved shortcut file and its moved target are two different problems.

• The launcher opens but the game does not: sign in, verify ownership and installation, and test the same shortcut or protocol outside LaunchBox.

• The game immediately exits: check dependencies, logs, and arguments; direct executable launches use the executable's folder as their working directory.

• The game works only from its shortcut: make that .lnk file the Application Path.

• A batch file opens briefly and closes: run it from a Command Prompt to see the error, quote paths, and set its working folder explicitly.

• The wrong helper starts: choose the real game executable or required launcher.

• An administrator prompt appears every time: determine whether the target or its compatibility settings request elevation.

• A duplicate appears: compare the manual and storefront-imported entries before combining or deleting either.

• Metadata matches another platform or edition: correct Platform or Scrape As, then select the intended Windows database release.

Beginner recommendation

Start with the exact executable or Windows shortcut that already works, add it as a Windows game, leave emulation disabled, and keep Application Command-Line Parameters empty unless arguments are required. Use Additional Apps for clearly labeled utilities, and return to direct Windows testing whenever a launch stops working.