Avoiding Cloud Sync Issues with LaunchBox

LaunchBox is portable, which means many users naturally want to place their LaunchBox folder inside a cloud storage folder such as OneDrive, Dropbox, Google Drive, or iCloud Drive.

While this can seem convenient, it can also cause problems if the cloud sync service tries to upload, download, lock, or replace files while LaunchBox or Big Box is running.

Why cloud sync can cause problems

LaunchBox regularly reads and writes files while you use it. This can include library data, settings, metadata, images, videos, cache files, plugins, logs, and backups.

Cloud sync services also need to read and write those same files so they can upload changes to the cloud or download changes from another device.

Problems can happen when both LaunchBox and the cloud sync service try to work with the same file at the same time.

This may lead to:

• Files being locked while LaunchBox needs to update them

• Partial or delayed syncs

• Conflicted copies

• Older files replacing newer ones

• Missing or unavailable files

• Permission errors

• Corrupted database or data files

Cloud sync services are useful for documents and backups, but an active LaunchBox folder behaves more like an application folder. It contains files that can change frequently and need to remain available while the program is running.

Errors or symptoms you may see

Cloud sync issues can show up in different ways. You may see:

• Access denied errors

• Plugin errors after launching or updating LaunchBox

• Troubleshooting: "Another Instance is Already Running" Error

• SQLite database errors, including database disk image is malformed

• Settings reverting unexpectedly

• Cloud sync apps showing files stuck syncing

• Duplicate or conflicted copies of LaunchBox data files

• Games or media not opening because files are not available locally

Note: These symptoms do not always mean cloud sync is the cause, but if your LaunchBox folder is stored inside OneDrive, Dropbox, Google Drive, iCloud Drive, or another syncing service, it is one of the first things to check.

Why some LaunchBox files are more sensitive

Some files are more likely to have problems than others because LaunchBox actively uses them while running.

Data files

The LaunchBoxData folder contains much of your library and configuration data, including platforms, games, playlists, emulator settings, and other important information.

These files may be updated when you:

• Import games

• Edit game metadata

• Change emulator settings

• Update playlists

• Change options

• Close LaunchBox or Big Box

If a cloud sync service interrupts or replaces one of these files while LaunchBox is writing to it, data may not save correctly.

Database files

LaunchBox uses local database files for some metadata and lookup functions. If a database file is locked, partially synced, or interrupted while being written, you may see database errors.

A common example is:

SQLite Error 11: database disk image is malformed

Plugin files

Plugins can be especially sensitive because they often include .dll files.

When LaunchBox loads a plugin, Windows may keep those plugin files in use. At the same time, a cloud sync service may try to scan, upload, download, replace, or lock those same files.

This can cause errors such as:

Access to the path '...LaunchBox\Plugins\[Plugin Name]' is denied.

This is more likely during LaunchBox startup, updates, plugin installs, or plugin repairs.

Media and backup files

Images, videos, manuals, music, and backup archives are usually less risky than active data files, but they can still cause problems if they are not fully available locally.

For example, cloud services may mark files as online-only. If LaunchBox or an emulator tries to use a file that has not been downloaded to the PC yet, it may appear missing or fail to open.

What to do if LaunchBox is in cloud storage

The safest option is to move your active LaunchBox installation out of the cloud-sync folder and onto a local drive, such as:

C:\LaunchBox

or another local folder outside OneDrive, Dropbox, Google Drive, or iCloud Drive.

You can still back up LaunchBox separately using LaunchBox's built-in backup tools or by copying the full LaunchBox folder while LaunchBox is closed.

Related guide: See Backing Up and Restoring Your LaunchBox Setup for safer backup options.

If you must use cloud storage

If you choose to keep LaunchBox in a cloud-synced folder, use these precautions:

1. Close LaunchBox and Big Box before syncing

   Make sure LaunchBox and Big Box are fully closed before your cloud service syncs the folder.

2. Pause syncing while LaunchBox is running

   If your cloud service supports it, pause sync before opening LaunchBox or Big Box. Resume syncing only after LaunchBox has fully closed.

3. Wait for sync to finish before opening LaunchBox

   Do not open LaunchBox while the cloud service is still uploading, downloading, or resolving sync conflicts.

4. Keep files available offline

   Avoid online-only placeholders for your LaunchBox folder. Make sure the files are stored locally on your PC.

5. Do not run the same LaunchBox folder on multiple PCs at the same time

   Running the same synced LaunchBox installation on two computers at once can create conflicting changes and may damage or overwrite data.

6. Keep regular backups

   Cloud sync is not the same as a clean backup. If a corrupted or incomplete file syncs to the cloud, that bad version may replace the good one on other devices.