Appearance
Turbo Client (Preview) Release Notes
This page contains information about the new features, improvements, known issues, and bug fixes in Turbo Client (Preview) releases.
For complete Turbo Client documentation, including installation guides, command reference, and tutorials, visit the Client Documentation. To download the latest version, visit the Turbo Client download page. For support, visit our contact page.
25.10.13.2526
This update to Turbo Client includes fixes for the following issues:
- The Turbo Sandbox Manager service could intermittently fail to start after installation when the client is installed as SYSTEM.
25.10.13.2520
This update to Turbo Client includes the following improvements:
- Run commands now report the
TURBOSITEIDenvironment variable as the site for usage analytics - Run commands now report detailed startup file metadata for usage analytics
- Run commands now report the system machine name instead of the fully qualified DNS name for usage analytics
This update includes fixes for the following issues:
- Run commands reported an incorrect Windows verison string in recent Windows versions
- Device keys may collide if two devices shared the same machine name
- TurboDrive may encounter DateTime parsing errors when using certain system date and time formats
25.10.13.2475
This update to Turbo Client includes the following improvements:
- New RequireTrustedLaunchOrigin security feature restricts commands to only originate from Turbo Launcher, preventing unauthorized command-line usage and protecting sensitive information. Configured via
turbo config --enable=RequireTrustedLaunchOrigin --all-users. --networkno longer scrambles port mappings as part of network isolation- MSI uninstall now supports
--delete-user-datato remove user data during uninstall - Various logging improvements
This update includes fixes for the following issues:
- Proxy resolution could hang when a proxy server did not respond during SOCKS5 handshake, causing long command startup delays
- Settings could be overwritten while Sandbox Manager resolves the domain topology, causing configuration changes to be lost
- TurboDrive did not gracefully handle errors when the domain is not fully resolved
- Subscription applications could remain installed after Active Directory access was revoked
- Merged VM settings could serialize incorrectly, leading to unexpected VM settings being applied
25.10.13.2288
This preview update to Turbo Client includes fixes for the following issues:
- Fixed mount validation error when Windows known folders (e.g., Downloads) are moved to non-default locations
- Settings file changes are now preserved when Sandbox Manager resolves domain topology in the background
- Sensitive information in TurboPlay logs are now filtered from launch arguments
25.10.13.2211
This preview update to Turbo Client includes fixes for the following issues:
- Application launches fail if the startup file comes from a mount source
25.10.13.2078
This preview update to Turbo Client includes fixes for the following issues:
- Saving to a mounted Documents/Desktop folder writes the files to the application container when the folders are synchronized via OneDrive. Now the files are correctly written to the mounted shared storage Desktop container.
25.10.13
This preview update to Turbo Client includes the following improvements:
- New
--disable-proxy-resolve-via-proxylaunch flag disables resolving hostnames via proxy turbo configproxy commands now support-all-users- Uninstall now removes all-user subscriptions and Add/Remove Program entries
- Install now starts the user Sandbox Manager automatically
- Adjusted various strings
This update includes fixes for the following issues:
- The latest image version from all-users repository was not used if that image existed in the current user repository
turbo rmi -acleared permissions set byturbo config --image-path=allusers --permission=write- Launches could fail if the
proxies.jsonfile was locked - The all-users assembly cache was not being used
25.9.64
This preview update to Turbo Client includes the following improvements:
- Improved proxy latency detection for launches that use a proxy
