The March 2026 update to Turbo Client includes the following improvements:

• --proxy-server now supports multiple proxy servers in semi-colon delimited format. The optimal proxy is automatically selected based on latency measurements.
• Proxy latency results are now cached and refreshed in the background by the Sandbox Manager, enabling faster proxy selection on subsequent launches
• New --disable-proxy-resolve-via-proxy launch flag disables resolving hostnames via the proxy server
• turbo config proxy commands now support --all-users to apply proxy settings for all users
• Changed default image pull behavior to prefer local images first, reducing unnecessary update checks when a local image is already available
• Improved image download network outage resilience with better retry logic
• New turbo config --p2p-mode configuration option controls peer-to-peer download behavior
• turbo config path settings (e.g., --image-path, --sandbox-path) now require absolute paths
• Turbo Client installer now starts the user Sandbox Manager automatically after installation
• The Turbo Client installer now prevents downgrades by default. Silent installs exit with code 1638 if a newer version is already installed; use --allow-downgrade to override. Non-silent installs prompt for confirmation before proceeding.
• MSI uninstall now supports --delete-user-data to remove user data during uninstallation
• --network no longer scrambles port mappings as part of network isolation
• Remote sandbox launches now display an "Initializing Secure Sandbox" status dialog while the secure environment is being prepared
• Session sandboxes are now automatically created when mounting from a not-yet-created session sandbox
• Subscription-registered applications now pull images on demand when not already cached locally
• Run commands now report the system machine name instead of the fully qualified DNS name for usage analytics reported to Turbo Server
• Run commands now report detailed startup file metadata for usage analytics reported to Turbo Server
• Sensitive information in launch arguments is now filtered from TurboPlay logs
• Client log format has changed to a more standardized format
• Client logs now include timing traces for launch operations
• Removed deprecated streaming model commands: turbo pushm, turbo model, turbo build, and turbo harvest. The --stream flag for turbo run has also been removed. This update includes fixes for the following issues:
• The Turbo Sandbox Manager service could fail to start when the client was installed from a SYSTEM account or from session 0
• turbo rmi -a cleared write permissions when the client was configured with turbo config --image-path=allusers --permission=write
• turbo rmi -a from an administrative command prompt reported success even when the deletion failed due to a permission error
• turbo import vm falsely reported "image already exists" when the VM version did not exist locally
• turbo precache exited with code 0 when cache operations failed with an error
• turbo history -n returned an extra result when used with --format=json
• The latest image version from the all-users repository was not used when an older version of the same image existed in the current user's repository
• The all-users assembly cache was not used when images were pre-cached in the shared all-users repository
• TurboDrive could encounter DateTime parsing errors when using certain regional date and time formats
• TurboDrive did not gracefully handle errors when the domain topology was not fully resolved
• Proxy resolution could hang when a proxy server did not respond during the SOCKS5 handshake, causing long command startup delays
• Launches could fail if the proxies.json file was locked by another process
• Settings could be overwritten while Sandbox Manager resolved the domain topology, causing configuration changes to be lost
• Merged VM settings could serialize incorrectly, causing unexpected VM settings to be applied at launch
• The --no-pull flag did not correctly prevent image downloads
• Saving to a mounted Documents or Desktop folder wrote files to the application session sandbox instead of the shared storage session sandbox when those folders were synchronized via OneDrive
• Application launches failed when the startup file came from a mount source
• Mount validation errors occurred when Windows known folders (e.g., Downloads) were moved to non-default locations
• Subscription applications could remain installed after Active Directory access was revoked
• Remote sandbox failed on Azure AD-joined computers
• Applications could fail to register when the application name contained special characters
• Run commands reported an incorrect Windows version string in recent Windows versions
• Subscription uninstallation entries were not removed from Add/Remove Programs when uninstalling the Turbo client
• Device keys could collide when multiple machines were provisioned with the same host name
• Pulling the same image simultaneously from multiple processes, when direct download is disabled, could cause one process to crash with an unhandled exception