Appearance

Launcher Troubleshooting ​

Common issues and solutions for the Turbo Launcher.

Quick Reference

  • Check policy configuration for missing shortcuts
  • Validate JSON syntax for policy loading issues
  • Review launcher logs for detailed error information

Common Issues ​

Applications Tab ​

No Applications Appearing ​

Problem: The Applications tab shows no applications or fewer applications than expected.

Solutions:

  • Verify that at least one "allow" policy matches your shortcuts
  • Check that scan locations contain valid shortcut files
  • Ensure policy file has correct JSON syntax
  • Review launcher logs for policy evaluation errors

Applications Not Launching ​

Problem: Applications appear in the launcher but fail to launch.

Solutions:

  • Ensure Turbo Client is installed and accessible
  • Verify target executables exist and are accessible
  • Check that policy modifications aren't causing launch failures
  • Review launcher logs for launch attempt details

Files Tab ​

Cannot See Files Tab ​

Problem: The Files tab is not available or shows an error.

Solutions:

  • Ensure the Sandbox Manager service is running
  • Verify Sandbox Manager version is compatible with the Launcher
  • Click the Retry button if shown
  • Check launcher logs for connection errors

Files Not Importing ​

Problem: Drag-drop file import fails or shows errors.

Solutions:

  • Check available disk space on the target drive
  • Verify you have write permissions to the sandbox storage location
  • Review error dialog details for specific failure reasons
  • Try importing a single small file first to isolate the issue

Cannot Open Files ​

Problem: Clicking files doesn't open them or shows an error.

Solutions:

  • Check that an application rule in your policy includes a file association for that file type
  • Verify the handler application is installed and appears in the Start Menu
  • Ensure the application's matcher pattern can find the executable
  • Check that file operation policies allow opening (no explicit deny for the extension)

Policy Configuration ​

Policy Not Loading ​

Problem: Policy changes are not taking effect.

Solutions:

  • Verify JSON syntax using an online validator
  • Check file permissions and accessibility
  • Ensure policy file is in the correct location:
    • System-wide: %PROGRAMDATA%\Turbo\Launcher\policy.json
    • User-specific: %LOCALAPPDATA%\Turbo\Launcher\policy.json
  • Review launcher logs for policy loading errors

Policy Modifications Not Applied ​

Problem: Policy modifications are not being applied to launches.

Solutions:

  • Ensure the policy action is "allow" (not just "modify")
  • Verify modification syntax in the policy file
  • Check policy priority for modification merging
  • Review launcher logs for modification application errors

Proxy Settings ​

Proxy Test Failures ​

Problem: Proxy tests fail or show timeout errors.

Solutions:

  • Verify the proxy server address and port are correct
  • Check that your network allows connections to the proxy
  • Ensure firewall rules permit SOCKS traffic
  • Verify proxy credentials if authentication is required
  • Check that the proxy server is running and responsive

Variable Substitution and Credentials ​

Variables Not Resolving ​

Problem: Policy contains variables like {{CRED:PolicyProxy001:username}} but they appear as empty strings or are not resolved.

Solutions:

  • Verify the Sandbox Manager service is running: sc query "Turbo Sandbox Manager"
  • Check that credentials are stored in Windows Credential Manager under the service account context
  • Verify credential naming follows the turbo: prefix convention
  • Review launcher logs for variable resolution errors or warnings
  • Ensure the Sandbox Manager service account has access to the credentials

Verifying Credential Storage ​

Problem: Need to confirm credentials are properly stored for policy variable resolution.

Steps to Verify:

  1. Check if credentials exist:
    cmd
    cmdkey /list | findstr "turbo"
  2. Verify the target name matches your policy variable (e.g., turbo:PolicyProxy001)
  3. If running as the service account, ensure you're checking credentials in that context

Log Analysis ​

Log Locations ​

Launcher logs provide detailed information about policy loading, shortcut evaluation, and launch attempts.

Turbo client logs are written to the %LOCALAPPDATA%\Turbo\Logs folder and contain both launcher-specific logs and client logs for application launches:

  • Launcher logs: TurboLauncher_YYYYMMDD_HHMMSS_XXXXX.log
  • Client logs: turbo_YYYYMMDD_HHMMSS_XXXXX.log

Known Issues ​

  • "Run in diagnostic mode" does not set up diagnostics if the container is already running
  • Proxy selection changes are not applied if the container is already running
  • Launcher does not immediately recover from policy errors. Click "Retry" to manually recover.
  • Launcher is not fully keyboard accessible
  • Launcher taskbar pin stops working after client upgrade
  • Turbo Server session reports list Launcher-launched applications as "windows/base"
  • Sessions created in older versions of the Turbo Launcher will not show up in the Sessions tab until they are launched via the new Turbo Launcher

Turbo.net © 2025