• Established in 2018
  • Developed in the UK
  • Over 9000 Users Worldwide
  • 194 Million Patches Delivered

LaunchBoost.io

Login
Plans
Priority SupportVIP
Skip the queue on Discord
/Documentation/Patch Runtime/Debug Log – Troubleshooting

Debug Log – Troubleshooting

This page is designed to be the ultimate troubleshooting companion. It dissects the debug logs generated by LaunchBoost, explaining exactly what each message means and how to fix the underlying issue.

🐞 Debug Logs & Troubleshooting Guide

LaunchBoost generates detailed logs to help you diagnose configuration errors, network issues, and permission blockers. This guide breaks down the specific messages you might see in debuglog-*.txt or the user-friendly lastpatchlog.html.

📂 Log File Locations

  • HTML Log (Best for viewing):%AppData%\LaunchBoost\<project-slug>\lastpatchlog.html

  • Raw Text Log:%AppData%\LaunchBoost\<project-slug>\debuglog-[TIMESTAMP].txt

🚀 1. Startup & Security Errors

These errors occur immediately when the patcher launches.

CRITICAL: Missing required launch arguments

  • Event: Application startup aborts.

  • Meaning: The patcher was launched without the necessary authentication flags.

  • Remedy: Ensure your launcher or command line includes:

    • -apiKey "YOUR_KEY"

    • -project "YOUR_SLUG"

Security Check Failed / License Valid: False

  • Event: Authentication handshake fails.

  • Specific Messages:

    • TimeCheck Failed: The client could not synchronize time with the validation server.

    • AccessReq Failed: The API Key or Project Slug is incorrect, or the server rejected the signature.

    • Subscription inactive: The developer account associated with this project has an expired subscription.

  • Remedy:

    • Check Keys: Verify the API Key and Project Slug in your launch arguments match your LaunchBoost dashboard exactly.

    • Check Plan: Log in to LaunchBoost and ensure your subscription is active.

    • Firewall: Ensure the user isn’t blocking connections to launchboost.io.

CRITICAL: INTEGRITY VIOLIATION DETECTED

  • Event: The application immediately exits with code 0xC0000005.

  • Meaning: The patcher.exe binary on the user’s disk has been modified, infected, or cracked. It does not match the official runtime version.

  • Remedy:

    • Redownload: The user must redownload the official patcher executable.

    • Virus Scan: Recommend a system scan as this can indicate malware tampering.

📂 2. Directory Detection & Permissions

CRITICAL: Could not determine game directory

  • Event: Patcher cannot find where to install/update the game.

  • Meaning: All configured detection methods (Registry, Appended, Self) failed to return a valid path.

  • Remedy:

    • Registry Mode: Verify the keys defined in your Patch Settings exist on the user’s machine.

    • Appended Mode: Ensure the relative path rule is correct relative to the patcher executable.

Write access denied to: [Path]

  • Event: The patcher detects it cannot save files to the game folder.

  • Meaning: The game is likely installed in a protected system folder (e.g., C:\Program Files) and the user is not running as Administrator.

  • Remedy:

    • Auto-Elevation: The patcher should automatically request Admin rights (UAC prompt). If the user clicked “No”, tell them to restart and click “Yes”.

    • Manual Run: Right-click the patcher and select “Run as Administrator”.

🛠️ 3. Patching Engine Errors (Stage 5)

CRITICAL: No servers defined in configuration

  • Event: Patcher aborts Stage 5.

  • Meaning: Your project configuration returned an empty list for Servers.

  • Remedy: Go to the LaunchBoost dashboard and add at least one valid download server/mirror.

Failed to fetch patchlist

  • Event: Cannot download patchlist.json.

  • Meaning: The patcher could not reach patchlist.json on any of the defined servers.

  • Remedy:

    • Check URL: Open your server patchlist URL in a browser and append /patchlist.json to verify it exists.

    • CORS/Firewall: Ensure your web host allows direct file access. Make sure the patchlist.json file is readable publicly.

Integrity Mistmatch: [Filename]

  • Event: The patcher decides to re-download a file.

  • Meaning: The local file exists but its contents are different from what the server expects.

    • Expected: Hash/Size from patchlist.json.

    • Actual: Hash/Size of the file on disk.

  • Remedy: This is normal behavior for an update. However, if it happens repeatedly for the same file without an update, check if your local antivirus is modifying the file or if the patch_salt in your config has changed.

CRITICAL: integrity fail: checksum mismatch (Post-Patch)

  • Event: Patching fails after downloading.

  • Meaning: The file was downloaded, but the resulting file on disk still doesn’t match the expected hash even after patching.

  • Causes & Remedies:

    • CDN Caching: Your CDN might be serving an old version of the file. Purge your CDN or web host / nginx cache.

    • Corruption: The download was corrupted in transit.

    • Antivirus: Security software deleted/quarantined the file immediately after write.

    • Permissions: The patcher failed to obtain permissions to patch that specific file on the computer.

HTTP 404 or HTTP 403

  • Event: A specific file fails to download.

  • Meaning: The file listed in patchlist.json does not exist on the server.

  • Remedy:

    • Re-generate Patchlist: Run your patch generation tool again to ensure the manifest matches the files on the server.

    • Case Sensitivity: Linux servers are case-sensitive. Ensure MyFile.Texture matches exactly on the server (not myfile.texture).

HTTP 401 (Unauthorized)

  • Event: Download fails immediately.

  • Meaning: The requested file is behind a password-protected directory (e.g., Basic Auth, .htpasswd).

  • Remedy:

    • Public Access: Your patch servers must be publicly accessible. Disable password protection for the patch directory.

    • Permissions: Check your web host’s file permissions (chmod) to ensure the web user can read the files.

HTTP 416 (Range not Satisfiable)

  • Event: Patcher attempts to resume a partial download but the server rejects it.

  • Meaning: The patcher has a partial file (e.g., 50MB of 100MB), but the server says the file size on disk is invalid or the file has changed since the download started.

  • Remedy:

    • Delete Staging: Delete the %AppData%\LaunchBoost\<project-slug>\staging folder to force a fresh download.

    • Server Config: Ensure your web server supports Range headers (Resumable downloads).

HTTP 500 (Internal Server Error)

  • Event: Server responds with a generic error.

  • Meaning: Your web server crashed or is misconfigured while trying to serve the file.

  • Remedy:

    • MIME Types: Ensure your server has MIME types configured for your game files (e.g., .pak, .data, .bundle). Some servers crash if they don’t know how to serve a specific extension.

    • Logs: Check your web server’s error logs (Apache/Nginx/IIS logs), not the LaunchBoost logs.

HTTP 502 / HTTP 503 / HTTP 504 (Gateway/Timeout))

  • Event: Connection drops or times out.

  • Meaning: The server is overloaded, down for maintenance, or a proxy (like Cloudflare) is timing out the connection.

  • Remedy:

    • Cloudflare: If using Cloudflare, you may be hitting their timeout limits for large files.

    • Status: Check if your web host is experiencing an outage.

⚠️ Third-Party Hosting Disclaimer

Please Read Carefully:

LaunchBoost is a client-side patching engine. It is designed to download files from any standard HTTP/HTTPS web server. It does not control, manage, or configure your web hosting environment.

We do not provide support for third-party web hosting configurations, VPS setup, or Dedicated Server management.

If you encounter HTTP 403, 404, 500, or connection timeout errors, these indicate issues with your web host, not the LaunchBoost software.

You must contact your web hosting provider or server administrator for assistance with:

  • File Permissions: Ensuring files are readable by the public.

  • MIME Types: Configuring the server to allow downloading of .pak, .dll, or custom file extensions.

  • Firewall Rules: Unblocking incoming connections or specific regions.

  • Bandwidth Limits: resolving throttling or “Quota Exceeded” errors.

  • CORS/Cross-Domain Policies: If using web-based launchers.

If the LaunchBoost logs show that the URL is correct but the download fails, the issue lies with the server hosting that URL.

We can and may, at our own discretion, provide some further support via the Discord VIP rooms.

✅ 4. Prerequisite & Post-requisite Errors

Condition Check Error

  • Event: A rule failed to evaluate.

  • Meaning: The data for the condition is malformed or invalid.

  • Remedy: Check your Project Configuration data for syntax errors in your Requisites.

Action Execution Failed

  • Event: The condition was met, but the action (e.g., writing a file) failed.

  • Specifics:

    • Download failed: The URL in DownloadAndRun is unreachable.

    • Write Registry: Permission denied (requires Admin).

  • Remedy:

    • Ensure all URLs in your actions are direct download links.

    • If writing to HKLM registry, ensure the patcher requests Admin privileges.

Action Execution Failed

  • Event: The entire patching process stops.

  • Meaning: A Prerequisite or Post-requisite marked as abort_on_fail: true failed to execute.

  • Remedy: Investigate the specific Action failure above. If this step is optional (e.g., installing DirectX), set abort_on_fail to false in your config.

🔄 5. Auto-Updater Errors

Update Check Failed

  • Event: Patcher cannot check for self-updates.

  • Meaning: Could not reach the ByteBox Media server to read the version file.

  • Remedy: Usually a temporary network issue. If persistent, check if the user’s firewall blocks any runtime URLs.

Self Update Failed

  • Event: The patcher tried to update but failed to replace itself.

  • Meaning: The file system locked patcher.exe, preventing the rename/overwrite operation.

  • Remedy: Reboot the computer to release file locks and try again.

PreviousTroubleshootingNext Runtime Tips