Appearance

Application Troubleshooting ​

Use this page to isolate and resolve application launch issues from Turbo Server workspaces.

Test Known Application ​

Problem

  • You need to confirm whether the issue is with Turbo Server or the application configuration.

Solutions

Related

Launch Modes ​

Problem

  • The application works in some launch modes but not others.

Solutions

  • Test Run in Cloud (HTML5), Run in Cloud (Windowed), and Run on My PC from the workspace context menu.
  • If HTML5 succeeds but Windowed fails (or vice versa), report the issue to Turbo Support.
  • If Run in Cloud works but Run on My PC fails, follow Application Troubleshooting for app-specific issues.
  • If Run on My PC works but Run in Cloud fails, test a known-good app to see if the issue is server-side.

Related

Command-Line Launch ​

Problem

  • Workspace launches fail and you need to test the image directly.

Solutions

  • On the affected system, run turbo try application-image to launch in a temporary container.
  • If the command fails, review configuration using Application Troubleshooting.
  • If it succeeds, investigate sandbox corruption or workspace settings (isolation, components).

Related

Sandbox Problem ​

Problem

  • A persisted sandbox prevents the application from starting.

Solutions

  • Create a temporary internal user (Admin > Users > Add User) and launch the app to test with a clean sandbox.
  • If the temporary user succeeds, clear the affected user's session in Admin > Users > Username > Sessions.
  • Remove local session sandboxes with turbo containers and turbo rm <containername> or delete C:\\Users\\*username*\\AppData\\Local\\Turbo\\Containers\\Sandboxes.

Related

Component Conflict ​

Problem

  • A component bundled with the app causes the launch to fail.

Solutions

  • Remove nonessential components under Workspace Application settings > Components and retest.
  • If the app launches after removal, troubleshoot the component using Application Troubleshooting.

Related

Container Isolation ​

Problem

  • The isolation level conflicts with native applications or filesystem access.

Solutions

  • Default isolation is Write-Copy. Switch to Full to hide native apps if conflicts occur.
  • Switch to Merge if the app must write to the native filesystem for downstream processes.

Related

Generate VM Diagnostic Logs ​

Problem

  • You need detailed VM logs to diagnose launch failures.

Solutions

  • Append &diagnostic= to the launch URL:
    • Original: https://turboserver/run/3c3120d5-0151-41fa-9f35-bb2a8082c291?loc=2&title=Notepad%2B%2B
    • Diagnostic: https://turboserver/run/3c3120d5-0151-41fa-9f35-bb2a8082c291?loc=2&title=Notepad%2B%2B&diagnostic=
  • Collect logs from %LOCALAPPDATA%\\Turbo\\Containers\\sandboxes\\*sandbox-guid*\\logs (Run on My PC) or the application server (Run in Cloud).

Related

Application Updates ​

Problem

  • The workspace may be launching an outdated image.

Solutions

  • Run turbo images on the execution host to confirm the image ID matches the update.
  • To force an update, run turbo pull application-image instead of waiting for the 24-hour auto-check.

Related

Licensing ​

Problem

  • The application requires an Active Directory user context to satisfy licensing.

Solutions

  • Set Workspace Application settings > General > Profile Mode to Ask for Credentials, then launch and sign in with the required AD user.

Related

Security Software ​

Problem

  • Security software blocks the application on certain systems.

Solutions

Related

Internet Explorer Does Not Launch Inside Virtual Application ​

Problem

  • Apps that rely on Internet Explorer fail to start inside the virtual environment.

Solutions

  • Set isolation to Write-Copy or Merge; Full isolation may block required Windows components.

Related

Turbo.net © 2025