LaunchBox turns a messy folder of emulators and game files into one searchable library with box art, videos, and a single play button. This tutorial walks through a full LaunchBox setup on Windows 11 in 13 steps, from picking a folder to a tested backup. Plan on about 60 minutes if your files are already on the PC.
The app is a frontend, not an emulator. It launches the emulators you install, hands them your game files, and stores the metadata around them. The vendor’s help article on what LaunchBox is and how it works frames it the same way. If you are still deciding between frontends, our LaunchBox vs Playnite vs ES-DE comparison covers the price gap and feature trade-offs. This guide assumes you picked LaunchBox and want it working tonight.
Everything below uses legally sourced material. You supply your own game dumps and your own console firmware. We never link to download sites, and the steps work the same whether your library holds ten games or ten thousand.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Why LaunchBox Is Worth Setting Up in 2026
Most emulator users start with one emulator per console and a desktop full of shortcuts. That works until the third console. Then you forget which emulator runs which system, which command-line switch starts fullscreen, and where the save files went. A frontend fixes all three problems by storing the answers once.
LaunchBox has also changed a lot this year. Version 14.0 landed on August 14, 2026, and the developers said the scope grew well past an ordinary update. The changelog lists a new Media Engine, a built-in Reader for manuals and magazines, faster List View and Image Grid performance, a redesigned Big Box filtering and sorting system, searchable options, and an improved ROM-import flow that installs emulators for you. A 14.1.0 beta circulates in the forums, and as of October 29 it remains a beta, so treat it as a test build.
LaunchBox’s homepage puts the pitch plainly: “LaunchBox includes support for countless emulators.” That claim holds up in practice. The app can download and configure many popular emulators, and it accepts any other emulator you point it at by hand. If you prefer a bundle that installs a whole emulator suite at once, EmuDeck on Windows takes a different route. If you want a themeable launcher that stays out of your way, Pegasus Frontend sits at the minimal end of the spectrum. LaunchBox lands in the middle with a full database-driven library and a gentle learning curve.
LaunchBox, Big Box, and LaunchBox for Android
The naming trips people up, so here is the split. LaunchBox is the desktop library manager. Big Box is the fullscreen, controller-first interface that ships inside the Windows app and counts as a premium feature. LaunchBox for Android is a separate product with its own release track. It changes nothing on Windows.
| Product | Platform | Role | Status on Oct. 29, 2026 |
|---|---|---|---|
| LaunchBox | Windows | Library manager, importer, scraper, launcher | Stable 14.0.1, 14.1.0 in beta |
| Big Box | Windows | Fullscreen controller interface for TVs and cabinets | Included with LaunchBox, premium feature |
| LaunchBox for Android | Android | Separate mobile frontend | Version 1.23 released Oct. 9, 2026 |
| Reader | Windows | In-app viewer for manuals and magazines | Added in 14.0 |
| Media Engine | Windows | New media handling layer | Added in 14.0 |
| Game Pulse | Windows | Faster successor to hi2txt for high scores | 14.1 beta only |
On pricing, the official pricing page (last updated October 25, 2026) reportedly lists a free starter tier, a $30 license with one year of updates, and a $75 lifetime license. Check the page yourself before buying, because the vendor has adjusted tiers before. The free tier is enough to follow every step except step 12, which covers Big Box and needs the premium license.
Prerequisites and Versions
Gather these before you start. The table lists what the guide was written against. Newer emulator builds behave the same way in almost every case, since the steps lean on stable menus and command-line switches rather than on version-specific features.
| Requirement | Version or spec used | Notes |
|---|---|---|
| Operating system | Windows 11 version 26H2 | Available to all eligible devices by Oct. 28, 2026 |
| LaunchBox for Windows | 14.0.1 (stable) | Released Aug. 25, 2026. Skip the 14.1 beta for a first setup |
| Shell for scripts | Windows PowerShell 5.1 (built in) | PowerShell 7 works too |
| Storage | A dedicated drive or large partition | An external SSD works if the drive letter stays fixed |
| Emulators | Latest stable build of each | LaunchBox can download many of them |
| Game files | Dumps from discs and cartridges you own | Uncompressed, or CHD for disc systems where supported |
| Firmware or BIOS | Dumped from your own consoles | Required by some systems, not all |
| Controller | Any XInput or DirectInput pad | Test it in Windows first |
On the OS side, Microsoft’s release-health pages show Windows 11 version 26H2 reached full availability for eligible devices by October 28, 2026. Windows 11 24H2 Home and Pro stopped receiving updates on October 13, 2026. If your machine still runs 24H2 Home or Pro, update before you build a library on it. Microsoft’s October 28 setup update for 26H1 targets new devices that ship with that release, so most existing PCs will never see it. We found no Windows 11 change that blocks emulators or frontends. For the wider picture of what runs well on current hardware, see our rundown of emulators for Windows PCs.
Hardware Expectations
LaunchBox itself is light. The load comes from the emulators and from artwork caching. A modern quad-core CPU, a recent GPU, and an SSD for the LaunchBox folder keep browsing snappy. Disc systems from the PS2 era onward push hardest, and that cost belongs to the emulator, not the frontend. Put the LaunchBox install and its Images folder on an SSD even if your game archive lives on a larger hard drive.
Plan the Library Layout First (Steps 1 and 2)
Most LaunchBox headaches trace back to a folder layout nobody planned. LaunchBox stores paths to your files, so moving them later breaks entries unless you fix the paths. Spend ten minutes on layout now and you save an evening later.
Step 1: Check Your Windows 11 Build
Open PowerShell and read the release from the registry. This takes five seconds and tells you whether you sit on a supported build.
# Show the Windows 11 release, build, and edition
$v = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
[pscustomobject]@{
Edition = $v.ProductName
DisplayVersion = $v.DisplayVersion
Build = $v.CurrentBuild
Revision = $v.UBR
} | Format-ListOn a current machine the output matches the sample in the output section below. If DisplayVersion says 24H2 and the edition is Home or Pro, open Settings, then Windows Update, and install the newer release first. Reboot before you move on.
Step 2: Create a Fixed Folder Structure
Pick a root folder on a drive that keeps its letter. Avoid OneDrive-synced locations such as Documents or Desktop, because sync clients can lock files while LaunchBox writes to them. Avoid Program Files too, since Windows restricts writes there. The script below builds a layout that separates the app, the emulators, the game files, firmware, saves, and backups.
$root = 'D:\Emulation'
$folders = @(
"$root\LaunchBox",
"$root\Emulators",
"$root\ROMs\Sony PlayStation",
"$root\ROMs\Nintendo 64",
"$root\ROMs\Sega Genesis",
"$root\BIOS",
"$root\Saves",
"$root\Backups"
)
foreach ($f in $folders) {
New-Item -ItemType Directory -Path $f -Force | Out-Null
}
Get-ChildItem $root -Directory | Select-Object NameKeep one folder per platform under ROMs. LaunchBox does not require this, but its importer works platform by platform, and a clean split lets you point each import at a single folder. Short paths help too, because some older emulators still choke on very long ones. Name each platform folder after the console in plain English so you can read your own library six months from now.
Install LaunchBox and Run the First-Time Wizard (Steps 3 and 4)
Step 3: Download and Install LaunchBox
Download the installer from the official LaunchBox site only. Search results for frontends attract lookalike download pages, and an emulator frontend runs with enough file access that you want the genuine build. Run the installer as a normal user. When it asks for an install location, choose the LaunchBox folder you created in step 2 instead of the default.
Windows SmartScreen may show a prompt on first launch. For an installer from the vendor, that prompt is routine. Compare the publisher name before you continue. The copyright line on the vendor’s site reads Unbroken Software, LLC.
One tutorial creator gave the portability reason for choosing a custom drive: “This way if I bring this drive somewhere I have everything all encompassed on this drive.” The remark comes from an uncredited presenter in a LaunchBox and MAME walkthrough on YouTube. The logic holds even if you never move the drive. A self-contained folder is easier to back up, and it survives a Windows reinstall.
Step 4: Walk Through the First-Run Setup
On first launch the app opens a setup flow. In practice you will see prompts to import games, choose a starting emulator, and decide which media to download. You can skip any prompt and return later through the Tools menu, which is how this guide handles it. Menu labels shift slightly between builds, so match the wording on your screen rather than expecting an exact copy.
Skip the game import for now. We want emulators working before games enter the library, so every later failure points to one cause. If the app offers an account sign-in, you can decline for this guide. The 14.1 beta reworks sign-in around an “Unbroken Account” that uses OAuth, but the stable 14.0.1 build does not depend on it for a local library.
Open Tools, then Options, and confirm two settings before you continue. First, check where LaunchBox plans to keep images and videos, and keep that path on your SSD. Second, leave automatic update checks on. LaunchBox ships point releases quickly, and 14.0.1 arrived 11 days after 14.0.
Add Emulators the Safe Way (Steps 5 and 6)
The order matters. Install and test each emulator on its own, then connect it to LaunchBox. If a game fails later, you will already know the emulator itself works.
Step 5: Install or Register Your First Emulator
You have two routes. The first is automatic. The 14.0 changelog says the ROM-import flow now handles emulator installation better, so LaunchBox can fetch a supported emulator while you import a platform. The second is manual. Download an emulator yourself, unpack it into the Emulators folder, and register it under Tools, then Manage, then Emulators. The manual route takes longer and gives you control over the exact build and folder.
This guide uses two emulators across three platforms. RetroArch covers Nintendo 64 and Sega Genesis through two cores. DuckStation covers Sony PlayStation as a standalone program. Install each into its own subfolder under Emulators, such as D:\Emulation\Emulators\RetroArch. Core and firmware rules differ per system in RetroArch, so this guide touches only what it needs. For a look at a command-line multi-system emulator that LaunchBox can wrap in a menu, Mednafen on Windows shows the raw version of the same idea.
When you add an emulator manually, LaunchBox asks for the executable path, a title, and the platforms the emulator handles. Choose the exact platforms. An emulator mapped to every platform makes the later question of which emulator launches a given game much harder to debug.
Step 6: Launch Each Emulator Once on Its Own
Start every emulator directly from its folder and let it create its configuration files. Many emulators run a first-time wizard that asks for a firmware folder, a game list folder, or a graphics backend. Finish those wizards now. Then load one test game from the emulator’s own menu. If the game boots, the emulator works. If it does not, fix it here, since LaunchBox only passes along a path and a few switches.
Run one test from PowerShell as well. This is the same call LaunchBox makes later, so a successful run proves the command line is right.
# RetroArch: run a Genesis game with an explicit core, fullscreen
& "D:\Emulation\Emulators\RetroArch\retroarch.exe" `
-L "D:\Emulation\Emulators\RetroArch\cores\genesis_plus_gx_libretro.dll" `
"D:\Emulation\ROMs\Sega Genesis\Example Game.md" `
-f
# DuckStation: run a PlayStation disc image in batch mode, fullscreen
& "D:\Emulation\Emulators\DuckStation\duckstation-qt-x64-ReleaseLTCG.exe" `
-batch -fullscreen -- "D:\Emulation\ROMs\Sony PlayStation\Example Game.cue"Your executable names may differ by build, so adjust the paths to match your folders. The point is the pattern: program, switches, then the game path last. Write down the switches that work. You paste them into LaunchBox in step 11.
Import and Scrape Your Library (Steps 7 and 8)
Step 7: Import Game Files Platform by Platform
Open Tools, then Import, then ROM Files. Select the folder for one platform, such as Sega Genesis. LaunchBox scans the files and tries to match each filename against its Games Database. The wizard then asks which platform the files belong to, which emulator should launch them, and whether to download metadata and media. Run the import for one platform at a time. A small batch lets you spot a wrong platform setting before it spreads across thousands of entries.
Before the import, tidy the filenames. The matcher works best with clean titles in the style of “Example Game (USA)”. Names stuffed with tags, release-group text, or stray punctuation match poorly. A short rename pass costs a few minutes and saves a long manual cleanup later.
Generate a checksum manifest before you import. It records exactly what you owned on the day you built the library, and it gives you a way to confirm that a restored backup came back intact. The script below hashes every file under the ROMs folder.
$romRoot = 'D:\Emulation\ROMs'
$manifest = 'D:\Emulation\Backups\rom-manifest.csv'
Get-ChildItem $romRoot -Recurse -File |
Get-FileHash -Algorithm SHA1 |
Select-Object Hash, Path |
Export-Csv $manifest -NoTypeInformation
(Import-Csv $manifest).CountThe last line prints the number of hashed files. Compare it against what you expect. A count that looks too low usually means files sit in a folder you did not expect, or an archive hides several games inside it.
Step 8: Download Metadata and Media
Metadata is the point of a frontend. LaunchBox pulls titles, descriptions, release dates, genres, box art, screenshots, and clear logos from its database. It can fetch this during import or later through the Tools menu. Running it after import gives you a cleaner view of what matched and what did not.
Start with the essentials: front box art, a screenshot, and a clear logo. Videos are large, and you can add them once the library works. The Media Engine in 14.0 handles media loading, and the changelog credits it with smoother Big Box browsing. The 14.1 beta adds automatic EmuMovies imports, though that feature stays in beta until a stable release ships.
When the download finishes, scan the library for gaps. Sort by missing box art and handle the leftovers by hand. Games with unusual regional titles or fan translations often fail to match. Right-click the entry, edit it, and search the database for the right record. A few manual fixes are normal even on a clean library.
Firmware, Controllers, and Command Lines (Steps 9 to 11)
Step 9: Place Firmware Files Correctly
Some systems need console firmware to boot, and some do not. Cartridge systems such as the Genesis and the Nintendo 64 typically run without it. Disc systems often need a BIOS dump from your own console. Where each file goes depends on the emulator, so read that emulator’s documentation. LaunchBox does not manage firmware. It launches the emulator, and the emulator looks in its own folders.
Keep one master copy of each dump in D:\Emulation\BIOS, then copy files into the folder each emulator expects. Create a small CSV that lists every file you need, the emulator that wants it, and the target folder. Then run this check whenever something fails to boot.
$required = Import-Csv 'D:\Emulation\BIOS\required-bios.csv'
foreach ($r in $required) {
$path = Join-Path $r.Folder $r.File
if (Test-Path $path) {
Write-Host ("OK {0,-12} {1}" -f $r.Emulator, $r.File) -ForegroundColor Green
} else {
Write-Host ("MISSING {0,-12} {1}" -f $r.Emulator, $r.File) -ForegroundColor Red
}
}The CSV needs three columns named Emulator, File, and Folder. Fill it from each emulator’s documentation and never from a download site. The Libretro docs make a similar point for RetroArch cores. Their October 2026 pages say firmware requirements are core-specific, that some cores need none, and that firmware and game media do not ship with the core.
Step 10: Set Up Controllers Before Touching Big Box
Controllers work on three layers. Windows sees the device first. Then LaunchBox or Big Box uses it for menu navigation. Finally each emulator maps buttons for gameplay. Test the layers in that order. Press the Windows key, type “Set up USB game controllers”, and open the test pane to confirm every button registers. If Windows does not see the pad, no frontend will.
Next, open the controller options inside LaunchBox and map the navigation buttons you want. Then open each emulator and set its in-game mapping. Do not expect one mapping to cover everything. LaunchBox maps menu navigation, and each emulator keeps its own gameplay layout. Steam Input can sit above all three layers if you add LaunchBox as a non-Steam game, which gives you one place to manage layouts for every pad.
Step 11: Assign Emulators and Command-Line Switches per Platform
Open Tools, then Manage, then Emulators. Select an emulator, open its platform tab, and tick the platforms it handles. Mark one emulator as the default for each platform. Then fill in the command-line parameters you tested in step 6. LaunchBox appends the game path at the end, so keep your switches in front of it.
| Platform | Emulator | Example command-line parameters | What they do |
|---|---|---|---|
| Sega Genesis | RetroArch | -L "cores\genesis_plus_gx_libretro.dll" -f | Load the core, start fullscreen |
| Nintendo 64 | RetroArch | -L "cores\mupen64plus_next_libretro.dll" -f | Load the core, start fullscreen |
| Sony PlayStation | DuckStation | -batch -fullscreen -- | Quit with the game, fullscreen, game path follows |
| Nintendo GameCube | Dolphin | -b -e | Batch mode, execute the given file |
| Sony PlayStation 2 | PCSX2 | -batch -fullscreen -- | Skip the main window, fullscreen |
Treat the table as a starting point. Emulators change switches between releases, so check your build’s help output if a parameter stops working. Test one game per platform from the LaunchBox list after you save. If a game launches, quits cleanly, and returns you to LaunchBox, the platform is done.
Switch on Big Box (Step 12)
Step 12: Configure Big Box for a Controller-First Experience
Big Box is the fullscreen interface for couches, TVs, and arcade cabinets. It reads the same library as LaunchBox, so every import and every fix you made carries over. You rebuild nothing. Big Box requires the premium license, and the vendor presents it as the premium, controller-oriented interface. If you would rather skip a paid tier, the ES-DE frontend on Windows offers a free TV-first alternative.
Launch Big Box from the LaunchBox menu or its own shortcut. Browse with the controller only for the first test, since that is the whole point of the mode. Check three things. Can you open a platform, pick a game, and start it without touching the keyboard? Does the game exit cleanly back into Big Box? Do videos and art load without stutter? Version 14.0 reworked Big Box filtering, sorting, media loading, and startup-video reliability, so problems here are rarer than in older builds.
Pick a theme next. Themes change layout, animation, and how much screen space the art uses. Start with the default and change one thing at a time. Heavy themes with video backgrounds look great and cost more GPU time, so pair them with a library on an SSD. If you run a cabinet, the 14.1 beta adds Big Box support for trackballs and spinners, including dual spinners and mouse-wheel spinners with adjustable sensitivity. It is beta only today, so wait for a stable release before you build a cabinet around it.
Make Big Box the Default Front End
For a living-room PC, add a shortcut to Big Box in your Startup folder. Press the Windows key plus R, type shell:startup, and drop the shortcut there. Reboot and confirm the PC lands in Big Box without a click. Keep a keyboard nearby for the first week so you can leave Big Box if a menu misbehaves.
Back Up and Verify (Step 13)
Step 13: Back Up the LaunchBox Data Folder on a Schedule
Your library lives as XML files in the Data folder inside the LaunchBox install. Hours of metadata edits, playlists, and per-game settings sit there. Artwork lives in the Images folder and can be downloaded again, so Data matters more. Back it up weekly. The script below copies the folder into a dated subfolder, which keeps older copies available if a bad edit corrupts the current one.
$src = 'D:\Emulation\LaunchBox\Data'
$stamp = Get-Date -Format 'yyyy-MM-dd'
$dest = "D:\Emulation\Backups\LaunchBox-Data\$stamp"
New-Item -ItemType Directory -Path $dest -Force | Out-Null
robocopy $src $dest /E /R:2 /W:2 /NFL /NDL /NP
# Keep the newest 8 backups, delete the rest
Get-ChildItem 'D:\Emulation\Backups\LaunchBox-Data' -Directory |
Sort-Object Name -Descending |
Select-Object -Skip 8 |
Remove-Item -Recurse -ForceSave the script as Backup-LaunchBox.ps1 and schedule it with Task Scheduler. Run it while LaunchBox is closed, so no file is mid-write. If you want a quick weekly job from the command line, this registers one for Sunday evening.
schtasks /Create /SC WEEKLY /D SUN /ST 20:00 /TN "LaunchBox Data Backup" ^
/TR "powershell.exe -NoProfile -ExecutionPolicy Bypass -File D:\Emulation\Backups\Backup-LaunchBox.ps1"Finish with a restore test. Copy the newest backup to a scratch folder, compare it to the live folder, and confirm the files match. A backup you never restored is a guess. Also keep your save files in mind. Emulators store saves in their own folders, so include the Saves folder in the same routine, or use a dedicated tool such as Ludusavi that knows where each emulator hides its saves.
Complete Working Project: A Portable Three-Platform Library
Here is the whole setup as one repeatable project. The goal is a portable library on one drive with Genesis, Nintendo 64, and PlayStation games, a firmware check, a hash manifest, and a dated backup. The script automates the parts that are plain file work. You still do the LaunchBox clicks, because the app owns its own configuration.
#requires -Version 5.1
# Setup-EmuLibrary.ps1
# Builds the folder layout, checks firmware, hashes games, and backs up LaunchBox data.
param(
[string]$Root = 'D:\Emulation'
)
$layout = @(
'LaunchBox', 'Emulators', 'BIOS', 'Saves', 'Backups',
'ROMs\Sony PlayStation', 'ROMs\Nintendo 64', 'ROMs\Sega Genesis'
)
Write-Host "== 1. Folder layout under $Root" -ForegroundColor Cyan
foreach ($d in $layout) {
$p = Join-Path $Root $d
if (-not (Test-Path $p)) { New-Item -ItemType Directory -Path $p -Force | Out-Null }
Write-Host (" ready {0}" -f $p)
}
Write-Host "== 2. Firmware check" -ForegroundColor Cyan
$csv = Join-Path $Root 'BIOS\required-bios.csv'
if (Test-Path $csv) {
foreach ($r in Import-Csv $csv) {
$f = Join-Path $r.Folder $r.File
if (Test-Path $f) { Write-Host (" OK {0} {1}" -f $r.Emulator, $r.File) -ForegroundColor Green }
else { Write-Host (" MISSING {0} {1}" -f $r.Emulator, $r.File) -ForegroundColor Red }
}
} else {
Write-Host " No required-bios.csv yet. Create one with columns Emulator, File, Folder."
}
Write-Host "== 3. Game file manifest" -ForegroundColor Cyan
$manifest = Join-Path $Root 'Backups\rom-manifest.csv'
$files = Get-ChildItem (Join-Path $Root 'ROMs') -Recurse -File -ErrorAction SilentlyContinue
if ($files) {
$files | Get-FileHash -Algorithm SHA1 | Select-Object Hash, Path |
Export-Csv $manifest -NoTypeInformation
Write-Host (" hashed {0} files" -f $files.Count)
} else {
Write-Host " No game files found yet."
}
Write-Host "== 4. LaunchBox data backup" -ForegroundColor Cyan
$src = Join-Path $Root 'LaunchBox\Data'
if (Test-Path $src) {
$dest = Join-Path $Root ("Backups\LaunchBox-Data\" + (Get-Date -Format 'yyyy-MM-dd'))
New-Item -ItemType Directory -Path $dest -Force | Out-Null
robocopy $src $dest /E /R:2 /W:2 /NFL /NDL /NP | Out-Null
Write-Host " copied to $dest"
} else {
Write-Host " LaunchBox Data folder not found yet. Install LaunchBox first."
}
Write-Host "Done." -ForegroundColor CyanRun it once before you install LaunchBox to create the folders. Run it again after your first import to hash the games and take the first backup. Because it only creates missing folders and copies files, running it repeatedly is safe. Save the file to D:\Emulation\Backups and call it with powershell -ExecutionPolicy Bypass -File if your policy blocks local scripts. For more guides in this vein, browse our gaming coverage.
Project Checklist
- Run the script to create the folder layout on a drive with a fixed letter.
- Install LaunchBox 14.0.1 into the LaunchBox folder.
- Install RetroArch and DuckStation, launch each once, and test one game.
- Register both emulators in LaunchBox and assign platforms.
- Import one platform, check the matches, then import the other two.
- Download box art, screenshots, and logos.
- Fill in the firmware CSV, run the check, and fix anything marked MISSING.
- Launch one game per platform from LaunchBox, then from Big Box if you own the license.
- Run the script again for the manifest and the first backup.
Expected Output at Each Stage
Use these samples to confirm your results. Exact values differ on your machine, but the shape should match. First, the build check from step 1 on a current Windows 11 PC:
Edition : Windows 11 Pro
DisplayVersion : 26H2
Build : 26300
Revision : (varies with your latest cumulative update)Next, a firmware check where one file is missing. The red line tells you exactly what to fix:
== 2. Firmware check
OK DuckStation (your PlayStation BIOS file)
MISSING PCSX2 (your PlayStation 2 BIOS file)Finally, the manifest and backup stages. A healthy run ends with a destination path and no errors:
== 3. Game file manifest
hashed 412 files
== 4. LaunchBox data backup
copied to D:\Emulation\Backups\LaunchBox-Data\2026-10-29
Done.The file count in that sample is illustrative only. In the LaunchBox window, a successful import shows your platforms in the left pane, a game count next to each, and box art filling in as downloads complete. If a platform shows zero games after an import, jump to the troubleshooting list below.
Common Pitfalls to Avoid
These six mistakes cause most support threads. Each is cheap to avoid and expensive to repair later.
- Installing under Program Files. Windows restricts writes there, so updates, caches, and media downloads can fail in odd ways. Use your own folder.
- Relying on a drive letter that changes. An external drive that mounts as E: today and F: tomorrow breaks every stored path. Assign a fixed letter in Disk Management and keep it.
- Importing everything in one pass. A wrong platform or emulator setting then spreads across the whole library. Import one platform at a time and inspect the result.
- Running the beta as your main build. The 14.1.0 beta adds useful features, and it is still a beta. Keep your main library on 14.0.1 and test betas on a copy.
- Keeping the library in a cloud-synced folder. Sync clients lock files and create conflict copies of XML data. Back up with a script and keep the live folder local.
- Skipping the standalone emulator test. If you never confirm the emulator works by itself, you cannot tell whether LaunchBox or the emulator is at fault.
A seventh habit deserves mention. Do not move or rename game folders after import unless you plan to fix paths. If you must reorganize, LaunchBox can update many entries in bulk through its edit tools, but you still want a backup first.
Troubleshooting: 10 Problems and Fixes
1. A Game Does Nothing When You Double-Click It
Check that the entry has an emulator assigned. Right-click the game, choose edit, and look at the emulation tab. If the emulator field is empty and no default exists for the platform, LaunchBox has nothing to launch. Set a default emulator for the platform under Tools, then Manage, then Emulators.
2. The Emulator Opens and Closes Immediately
This usually means a bad command line or missing firmware. Run the exact command from PowerShell, as in step 6, and read the emulator’s error. Missing firmware is the most common cause on disc systems. Run the firmware check script and fix anything marked MISSING.
3. The Wrong Emulator Launches
Per-game settings override the platform default. Open the game’s edit window and look for a game-level emulator. Clear it if you want the platform default to apply. Also check whether two emulators claim the same platform, and set only one as default.
4. Games Import With No Metadata
The matcher failed on the filename. Clean the names, then run Download Metadata and Media again. For stubborn titles, edit the entry and search the database by hand. A game missing from the database needs manual details, and LaunchBox lets you add art yourself.
5. Box Art Is Missing or Wrong
Wrong art means a wrong match. Fix the match first, then redownload media for that entry. Missing art can also mean the download was interrupted. Rerun the media download later and it picks up the gaps. Confirm the media folder sits on a drive with free space, since a full disk fails quietly.
6. The Controller Works in Windows but Not in Big Box
Close other programs that grab the pad, such as a controller-mapping utility or a Steam client running a conflicting layout. Reconnect the controller, restart Big Box, and test again. If you use Steam Input, make sure only one layer owns the device. Two layers fighting over the same pad produce double inputs or none.
7. Big Box Shows a Black Screen or a Stuck Startup Video
Update your graphics driver, then try disabling the startup video in the Big Box options. Version 14.0 improved startup-video reliability, so if you run an older build, update LaunchBox first. If the problem persists, switch to a lighter theme and see whether the GPU is the bottleneck.
8. Everything Breaks After a Drive Letter Change
Return the drive to its old letter in Disk Management. That restores every path at once, which beats editing thousands of entries. If you cannot go back, use LaunchBox’s bulk path tools or restore the Data folder from backup and adjust once.
9. Antivirus Quarantines an Emulator
Emulators sometimes trigger false positives because they compile or patch code at runtime. First confirm you downloaded the emulator from its official project page. Then restore the file from quarantine and add a narrow exclusion for the emulator’s own folder. Do not exclude your whole drive.
10. LaunchBox Starts Slowly With a Big Library
Move the LaunchBox folder, especially Images, to an SSD. Trim videos you never watch. The 14.0 release made List View and Image Grid faster, and the 14.1 beta targets faster startup and shutdown, so updating helps. Also check for a bloated Data folder from duplicate imports. Remove the duplicates and restart.
Bonus: A Steam Entry Shows as Missing
The 14.1 beta marks unavailable Steam games with a clearer “Missing” status. If you see it, the Steam client no longer reports that game as installed. Reinstall it in Steam or remove the stale entry from LaunchBox.
Advanced Tips for Power Users
Once the basics run, a few habits make a library feel professional. Use playlists to group games by theme, such as two-player games or short sessions, then pin the playlists you open most. Add a second emulator for the same platform and choose it per game when one runs a title better than another. LaunchBox lets a single platform use several emulators, so you keep the default simple and override only where needed.
Manuals deserve attention. Since 14.0, LaunchBox and Big Box can read manuals, guides, and magazines inside the app. If you own digital copies of manuals, attach them to games and browse them without leaving the frontend. For a library that includes PC classics, 86Box can emulate old PC hardware, and you can register it in LaunchBox like any other emulator. Arcade fans on Windows cabinets can also try TeknoParrot, which LaunchBox can launch as an external program.
Consider converting disc images to a compressed format where the emulator supports it. Smaller files cut storage cost and speed up backups. Test each converted game before you delete the originals, and keep the hash manifest from step 7 so you can compare before and after. Finally, test updates on a copy. Clone the LaunchBox folder, update the clone, and confirm your key games launch before you touch the main library. That habit turns every update from a gamble into a routine.
Keep a plain text file next to the library with every command-line switch you rely on, the emulator build each platform uses, and the date you last tested it. When a game breaks six months from now, that file tells you what changed. It also makes a move to a new PC a ten-minute job instead of a weekend of guessing.
FAQ
Is LaunchBox free?
The core app has a free tier, which covers importing games, adding emulators, and scraping metadata. Big Box and some extras need the premium license. Prices and tier names change, so confirm them on the official LaunchBox pricing page before you buy.
Does LaunchBox include emulators or games?
It includes no games. It can help you download and configure many emulators, but you supply your own game files and firmware from media you own. Treat any site that offers ready-made game libraries as a legal risk and a malware risk.
Does LaunchBox work on Windows 11 version 26H2?
We found no sign of a Windows 11 26H2 incompatibility with LaunchBox, Big Box, emulator imports, or metadata scraping in Microsoft’s release-health pages or in the vendor’s changelog. Microsoft lists 26H2 as available to all eligible devices as of October 28, 2026. Install it and follow the steps above.
Should I install the 14.1 beta?
Not for your main library. The beta adds faster startup, a new sign-in system, Game Pulse, and automatic EmuMovies imports, but beta builds can have bugs. If you want to test it, clone your LaunchBox folder first and run the beta on the copy.
Can I keep LaunchBox on an external drive?
Yes, and it suits anyone who moves between PCs. Keep the drive letter fixed on each machine, or you will break stored paths. Use an SSD rather than a spinning disk for the LaunchBox folder, and keep a backup on a second drive.
How do I move my library to a new PC?
Copy the whole Emulation folder to the new machine, using the same drive letter and path if you can. Launch each emulator once to confirm it runs. If the path differs, use the bulk path tools to update entries, and restore the Data backup if anything looks off.
Is LaunchBox for Android the same as the Windows version?
No. It is a separate product with its own releases. Version 1.23 is the current Android release and added dual-screen support and RetroAchievements profile access. It does not change your Windows library.
