Appearance

Turbo Client Release Notes ​

This page contains information about the new features, improvements, known issues, and bug fixes in Turbo Client 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.5.4.1712

The May 2025 update to Turbo Client includes the following improvements:

  • New! P2P bandwidth throttling feature allows limiting upload and download speeds for P2P downloads. To enable P2P bandwidth throttling use the following turbo config flags:

    --p2p-max-download-speed=VALUE   Maximum P2P download speed in KB/s (0 for unlimited)
--p2p-max-upload-speed=VALUE     Maximum P2P upload speed in KB/s (0 for unlimited)

  • New! P2P seeding feature allows seeding images after downloading.

    To enable P2P seeding, use the following command:

    turbo config --enable=P2PSeeding

  • The search command now includes releases and supports the -n parameter to return more results.

This update includes fixes for the following issues:

  • XVM updated even when the turbo subscribe --no-pull flag was specified.
  • P2P download fails when a corrupted version of the target .svm existed in the repository.
  • Turbo Drive Filr integration did not work against the latest Filr server.
  • Turbo GCI did not delete P2P files correctly.

Additional improvements:

  • Improved P2P hash verification time.

25.1.19.1661

The January 2025 update to Turbo Client includes the following improvements:

  • New! Peer-to-Peer Transfer feature enhances image distribution by supporting peer-to-peer distribution. This improves download speeds and reduces server load when numerous clients are downloading simultaneously. Note this feature also requires a corresponding Turbo Server update.
  • Improved handling of read-only image repositories, ensuring Turbo Client can launch successfully in shared image cache scenarios.
  • Enhanced subscription management with better offline support and improved error handling.
  • Disabled automatic font and DLL caching by default to improve initial performance.
  • Improved API security through the addition of API keys to additional API calls.

This update includes fixes for the following issues:

  • Turbo Sandbox Manager silent uninstall did not provide feedback on success or failure.
  • The --no-file-associations flag was not functioning as expected.
  • Locked subscription.json metadata file unnecesarily prevented users from registering a subscription.
  • Missing error handling and user feedback for various commands, including turbo export and turbo gc-shortcuts.
  • The turbo session command incorrectly reported the status of running sessions.
  • The turbo subscribe command with the --pull flag ignored disabled auto-precache settings.
  • An unhandled exception occurred in specific situations when using Run on My PC (Local).
  • Fixed various user interface elements to improve user experience.

Additional improvements:

  • Removed the deprecated Portable EXE export type.
  • Improved installation process to ensure all necessary files are included on Windows Server 2019.
  • Various performance optimizations and stability improvements.

24.9.2.1590

The September 2024 update to Turbo Client includes the following improvements:

  • New! Remote Sandbox feature in Turbo Sandbox Manager enhances security for sensitive data by allowing custom, encrypted sandbox locations accessible only to Turbo applications.
  • Introduces the turbo config --support-contact command to support customizing end-user support contact information in error prompts.
  • The turbo kill command help text has been enhanced for clarity.
  • Image version resolution has been improved for various Turbo commands.
  • The date created/modified in the assembly cache now matches the file from the image to improve application compatibility.

This update includes fixes for the following issues:

  • Applications could fail to launch if a previous instance of Turbo failed to release the repository lock due to a crash.
  • The Starting Session dialog persisted when launching certain system tray applications.
  • Installing the Acrobat Pro image could disable certain native Windows shell extensions.
  • The turbo gci command incorrectly removed images that are components of turbo installi registered applications.
  • An error occurred during turbo push operations when the image is absent but its metadata still exists in the local database.
  • The turbo installi command failed if the metadata Product Title contained a colon character.
  • Downloading images with request forwarding was not supported.
  • The turbo pull command failed if the assembly cache file was corrupt.
  • Installed applications failed to launch if the device key login cache file was corrupt.
  • Reduced excessive logging in Turbo Sandbox Manager logs.

24.5.5.1403

The May 2024 update to Turbo Client includes the following improvements:

  • The turbo import command now supports the xvm type for importing a Turbo VM directly from a file path.
  • The turbo import command now automatically detects and applies the appropriate application version to the release tag.
  • Turbo application dependencies are no longer restricted to exact image matches. Dependencies such as java:8 will now match with newer versions of application images named java:8.
  • The turbo containers command has been renamed to turbo sessions, accompanied by corresponding updates in all supporting text. JSON-based APIs remain unaffected by this change, and the original command will still function as an alias.
  • Java has been entirely removed from the Turbo Client.
  • The turbo push command will fail early if the user does not have permissions to push images.
  • The turbo gci command now accurately considers subscribed application images.
  • The turbo start --vm flag now supports using an empty string to unset the VM version for a specific session.
  • The turbo cache /xvm command has been introduced to address potential false positives triggered by security software.
  • Installed browsers will now appear in the Windows Default Apps settings.
  • Greatly improved Default Programs integration. Images with multiple programs will now install under separate entries in Default Programs.
  • The SSO login process has been streamlined when launching applications via the Launch Configuration service.

This update includes fixes for the following issues:

  • The turbo installi --offline --all-users command returned a misleading error message if the user did not have permissions to write to the image cache path.
  • Installed or subscribed applications sent unnecessary web events to Turbo Server.
  • An error dialog related to the T: Drive appeared without user interaction and has been removed.
  • T: Drive failed to ignore hidden files in specific scenarios.
  • T: Drive failed to synchronize Unicode characters in file names correctly.
  • Files directly unzipped into the T: Drive were not synchronized properly.
  • Install on My PC from Turbo Server failed if the application was not cached and required fonts.
  • The Turbo Client Path environment variable was not removed when uninstalled.
  • Certain fonts were installed with incorrect font names.
  • The turbo config --all-users --as-override command failed to correctly display the image path setting.
  • The Turbo Sandbox Manager service used an unquoted path.
  • Install on My PC from Turbo Server did not apply the correct application icon in some cases.
  • The turbo config --format=json command was missing the domainUrl field.
  • The turbo run --enable flag did not handle unknown values properly.
  • Turbo Sandbox Manager made outbound network connections in some situations even if installed in offline mode.
  • Even when auto-updates were turned off, Turbo Sandbox Manager continued to perform update checks.
  • Turbo Client generated temporary file names with random extensions triggering security audits.
  • The turbo subscription register command resulted in the creation of duplicate desktop shortcuts in certain scenarios.
  • Background subscription updates triggered auto-launching applications.
  • The turbo unsubscribe threw an unhandled error when the image path is read-only.
  • Desktop shortcuts duplicated when upgrading from subscriptions created in Turbo Client 23.6.9.576.
  • The turbo run command failed to verify whether the specified startup file architecture matched the host machine.

24.2.1.0

The February 2024 update to Turbo Client includes the following improvements:

  • The turbo installi command now generates a shortcut targets that are backwards compatible for Citrix environments.
  • The turbo installer now accepts an --offline flag indicating the Turbo Client components should run in offline mode.
  • The turbo config command now accepts an --enable=offline flag that forces turbo commands to run offline if possible. Any command that requires access online resources will fail in offline mode.
  • New turbo gcc command removes unused image cache resources.

This update includes fixes for the following issues:

  • The turbo release command could create an empty release visible in the turbo images command.
  • An unhandled exception dialog appeared when the user does not have permissions to write to the image cache when an image download is required.
  • The turbo push command did not correctly set the release version if specified for rename.
  • The turbo import command did not correctly set the release version if the destination image release already existed.
  • The turbo installi and turbo uninstalli command failed when running in specific timezones against applications installed from an older version of Turbo Client.
  • The turbo login --api-key=<key> --all-users command could result in expired user credentials being cached that were not renewed without logging out again.
  • The turbo rmi -a did not properly clear the image cache database under certain circumstances. This caused subsequent pulls to no longer cache the image executables and fonts.
  • The turbo subscription command was missing the unregister verb in the help text.
  • The turbo installi --offline command failed for certain images.
  • Turbo Sandbox Manager failed to properly garbage collect All Users images under certain circumstances.
  • The turbo gci command removed All Users images incorrectly if the current user configures the image path to the same All Users path.
  • Image downloads may silently fail under slow or unstable network conditions. An error message or dialog is now displayed to the user.
  • The turbo installi command did not properly register PDFs for Google Chrome and Microsoft Edge images.
  • The turbo cache command did not accurately detect font names for installation.
  • The turbo config command did not accurate print immediate changes when using the --all-users --as-override flags.

Update 24.2.1.1311

  • Installing applications that require non-standard fonts failed if the image was not present in the local cache.

23.11.26.1168

The November 2023 update to Turbo Client includes the following improvements:

  • Turbo Sandbox Manager can now automatically register and unregister subscribed workspaces in local user accounts against All Users subscriptions
  • Application fonts are now installed during image caching. This improves the speed of application registration and launches.
  • Web Applications are now installed when registering a subscription
  • Local users' Turbo Client install will now remove itself if the All Users install is present
  • The turbo run command now uses Write Copy isolation by default
  • Turbo Sandbox Manager can now automatically garbage collect session sandboxes
  • The turbo config command now supports setting storage path using environment variables such as %LOCALAPPDATA%
  • Improved download progress UI
  • Improved various error messages
  • Registered applications through turbo installi and turbo subscribe now appear in the Windows Default apps settings UI. This enables administrators to select registered applications as default file extension or URL protocol handler.
  • Registered applications that support the same file extension can be selected using Windows Explorer right click Open with... context menu.

This update includes fixes for the following issues:

  • Some passthrough turbo config flags for Turbo Client installer were ignored
  • Uninstalling Turbo Client installed by the MSI installer left entries in the registry
  • Image downloads did not resume correctly, potentially resulting in corrupted images
  • Image download reported an incorrect error when there was not enough disk space
  • Logging into Turbo Server configured with OpenID SSO authentication failed
  • Users were erroneously shown an error dialog "Turbo Drive must be installed" if the drive letter T: was in use.
  • Users were erroneously shown an error dialog "Turbo Drive Error" when Turbo Server went offline
  • Taskbar icons appeared incorrectly when launching applications from Turbo Portal. This was caused by installed desktop shortcut due to a bug in Windows Explorer.
  • Installed shortcuts used incorrect icons in certain scenarios
  • Unsubscribed All Users subscriptions were not removed from local user registrations
  • Duplicated shortcuts were created if the metadata folder was removed and the same apps were installed again
  • Turbo Client installer failed on Windows 11 Enterprise Azure VM
  • Turbo Client installer GUI did not scale correctly in high DPI resolutions
  • T: Drive did not save project folders correctly from Ansys applications

23.9.22.1012

The September 2023 update to Turbo Client includes the following improvements:

  • New Turbo Sandbox Manager service now handles workspace subscription updates, replacing the Windows Task Scheduler. This allows nearly realtime updates to endpoints as configuration changes. Please use turbo uninstalli or otherwise remove the old Windows Task Scheduler entries.
  • New turbo subscribe --all command flag automatically adds and removes all subscriptions available to the user
  • Improved syncing speed for the following commands: turbo pull, turbo push, turbo save and turbo continue
  • Improved turbo installi command speed
  • Added the --all flag to turbo unsubscribe and turbo subscription commands to apply actions to all subscribed workspaces
  • Added the --all flag to the turbo config command to print all settings
  • The turbo pull command now checks if there is enough disk space before attempting to pull the image
  • The --enable and --disable flags now support comma delimited values
  • The turbo installi command now uses a unique application identifier to prevent unintended configuration changes

This update includes fixes for the following issues:

  • The turbo subscribe --register command could create incorrect shortcuts when the images were not available locally
  • The turbo subscribe --pull command failed when the assembly folder was read-only
  • The turbo config --image-path=<path> failed when <path> was a drive root
  • The turbo new command failed when using an image more than once
  • The turbo images command failed to show images for all users correctly
  • The turbo pull --force command could fail if the image already existed
  • Shortcuts created by the turbo installi command and subscribed workspaces overwrote each other
  • Applications with the same name but in different workspaces overwrote each other when subscribed
  • Installed fonts did not load after system restart
  • Disabling T: Drive caused excessive CPU usage
  • Uninstalling Turbo Client failed to remove some installed files and settings
  • Launching a file from T: Drive occasionally failed on the application server

23.6.9.576

The June 2023 update to Turbo Client includes the following improvements:

  • The turbo installi command now installs URL handlers by default (use --no-url-handlers to disable)
  • The turbo config --image-path=<path> command now supports adding write permissions using the --permission=write flag
  • The turbo installi command now retries creating desktop shortcuts for better compatibility with OneDrive-synced desktops
  • Application sessions now display a warning dialog to users that are not part of an upcoming license reservation period
  • Support for launching applications as administrator from Turbo Server
  • Support for additional Turbo VM settings from Turbo Server

This update includes fixes for the following issues:

  • The turbo installi command did not correctly install context menu shell extensions
  • The turbo commit command failed for Internet Explorer
  • The turbo run command failed to check if the user was logged in under certain conditions resulting in a delayed error
  • The turbo subscribe command failed to inherit workspace settings
  • The turbo gci command incorrectly removed installed or registered images
  • Sessions from installed applications did not terminate if the user lost permissions to access the application
  • T: Drive could become unresponsive due to certain file system storage provider errors

23.4.6.549

The April 2023 update to Turbo Client includes the following improvements:

  • The turbo installi command now installs virtual fonts to improve launch performance
  • The turbo precache more accurately detects executable files to pre-cache to improve launch performance
  • The turbo precache honors files which are marked for precache in an image

This update includes fixes for the following issues:

  • The turbo gci failed under certain conditions
  • The turbo subscribe command failed to inherit workspace isolation settings
  • The turbo diff command failed if certain registry keys paths were modified
  • The turbo subscribe --pull command failed if a workspace application was set to inherit isolation
  • T: Drive failed to mount if the same user in a different Windows session had an existing T: Drive mount
  • The default permissions for c:\ProgramData\turbo allowed write access to Users group

23.2.3.457

The February 2023 update to Turbo Client includes the following improvements:

  • Updated to use .NET Framework 4.8
  • Improved launch startup times by automatically enabling the executable cache
  • New turbo subscribe --overwrite-shortcuts flag overwrites any existing shortcuts on the desktop when subscribing applications
  • Deprecated turbo installi --pin-client-version flag and replaced with the TURBOCLIENTBIN environment variable for discovering Turbo binaries when launching from shortcuts
  • Error messages from Turbo Drive are now available to the end user
  • Removed implied /k flag in turbo run if the startup file defaulted to cmd.exe
  • Cleaned up orphaned Turbo Drive mounted drives on Turbo Service startup
  • Removed unnecessary binary configuration log entries when launching applications
  • Improved diagnostic logging for user permissions during turbo subscribe
  • Renamed Turbo-Launcher.exe to TurboLauncher.exe

This update includes fixes for the following issues:

  • Turbo Client installation failed when installing on end user devices without .NET
  • The turbo commit command failed on containers with startup scripts
  • Applications could uninstall unexpectedly while registering a new subscription
  • A starting session dialog appeared for installed applications during application launch
  • Relaunching an application immediately after closing could fail in some instances
  • The turbo installi did not properly handle collisions with existing shortcuts
  • The turbo subscribe failed to remove application shortcuts when user access is revoked
  • The turbo run command failed to pass in triggers when launching in an existing session

22.12.7.379

The December 2022 update to Turbo Client includes the following improvements:

  • New turbo kill command kills sessions running on the local system
  • Improved reliability of image downloads on slow or unstable network connections with automatic retries on network failures and resuming partial downloads for all download modes
  • New turbo pull --force and --TURBODIRECTDOWNLOAD flags allow more control over image download behavior
  • Improved turbo config performance when setting an all-users image cache path
  • New turbo config --no-domain-verify flag disables domain verification, allowing configuration of domains that are offline or not yet setup. Unverified domains will be verified at runtime when running online.
  • Updated the turbo precache --all-users command to use the all-users image pre-cache location if running an All Users image in a local user context
  • Updated the executable cache to include .ocx files
  • Executable caching is now enabled by default for improved launch performance. New executable cache configuration options include a turbo import --precache flag and turbo config --enable=ExecutableCache and AutomaticPrecache settings.
  • Updated turbo rmi -a and turbo gci commands to remove all unreferenced executable cache files
  • Improved launch performance when mounting the T: Drive
  • Removed an unsigned wrapper executable in the image install directory that could cause issues with certain antivirus programs
  • Improved various text and error messages

This update includes fixes for the following issues:

  • The turbo rmi command incorrectly returned a 0 exit code on error
  • The turbo rmi command incorrectly deleted the underlying SVM when other releases reference the image
  • The turbo try -d command did not remove the container on exit
  • The turbodesktop register and unregister commands resulted in an error when running with the --all-users flag
  • The turbo install command could fail for applications with very long names
  • The turbo export command could fail on filenames with certain special characters
  • The turbo subscription unregister command could incorrectly result in a UAC elevation prompt in certain scenarios
  • Image downloads that took over an hour resulted in a timeout error when direct download was disabled
  • Failed image downloads could result in a corrupted image and cause subsequent download failures under certain circumstances
  • Image uploads could fail if all blocks already existed in the block storage
  • Launching an application with Ask for Credentials authentication using Run in Cloud (Windowed) a second time could result in an incorrect domain prefix if the workspace was configured with a default domain.
  • Mount points could fail to mount if they targeted a redirected special folder
  • T: Drive could fail to mount if the user manually installed certain drivers after installing Turbo for PC
  • T: Drive OneDrive file operations could fail for certain special characters
  • Existing login credentials could still used after changing domains, resulting in confusing login errors
  • Invalid device keys could result in command failures even if other valid device keys existed

22.9.60.304

The October 2022 update to Turbo Client includes the following improvements:

  • Added new turbo export --overwrite flag to overwrite existing images
  • Updated turbo subscription register command to support shortcuts and file extensions. This behavior is now consistent with the installi command.
  • Added new turbo subscription register --offline flag to register subscriptions without a hub connection
  • Added new turbo subscription register --allow-offline flag to register subscriptions offline if the connection to the hub fails
  • Added new turbo installi --TURBOREPO flag to support image path overrides
  • Updated turbo installi command to use the standard metadata title instead of the installation name for the file extension product name.
  • Installed applications no longer show the stopping session dialog on close
  • Updated turbo config --image-path command to only configure permissions on the images and assemblies subdirectories
  • Improved error handling for the turbo push command
  • Updated turbo installed command JSON output to include metadata about the installed objects
  • Updated turbo gc command to remove all sessions that have not been used in 30 days by default. A new --forks flag has been added to support removing only forked containers.
  • Relaxed login credential host matching logic to match any server host within the domain
  • Improved login credential renewal process for expired logins
  • Added support for Windows 11 Build 22621.521
  • Improved various text and error messages

This update includes fixes for the following issues:

  • The turbo installi command could incorrectly fail with a login error under certain circumstances
  • The turbo installi --offline command could fail to assign file associations
  • The turbo install command failed to install containers with only clean or base images
  • Installed applications could fail to launch due to malformed arguments or unresolved environmental variables under certain circumstances
  • The turbo suspend command incorrectly reported a failure upon successful suspension
  • The turbo login --auth=integrated command failed to login if the Hub was offline
  • The turbo images command could show incorrect all-users values if local repository and all-users repository were set to the same path
  • Running a registered shortcut from an all-users subscription could fail to launch
  • The turbo rmi --all-users <image> command incorrectly removed every all-users image
  • Turbo commands that require valid login credentials could fail if the credentials were within one hour of expiration
  • The T: Drive move operation could interrupt active uploads and result in data loss under certain circumstances
  • T: Drive startup failures could delay the application startup time under certain circumstances

22.6.1.183

The June 2022 update to Turbo Client includes the following improvements:

  • Improved T: Drive connection management to detect connection changes
  • Improved T: Drive to gracefully shutdown and upload files while user is logged off
  • Improved T: Drive performance when uploading very large files
  • Removed automatic shell extension registration from the turbo subscribe command. New turbo subscription register and turbo subscribe --register commands have been added to register shell extensions.
  • Updated workspace subscriptions to download the application's components when updating the application
  • Added a new subscribe --update-interval flag to control how often a subscription is updated
  • Added a new turbo gcl command that removes log files that exceed a configurable number of days
  • Added a new stopping session dialog when closing a Turbo application
  • Warn users when mounting a file that also exists in the sandbox that changes will be lost
  • Granted global read-only access to images installed in the all-users image cache and added an All Users column to the turbo images command
  • Improved error message when launching a Turbo application with a startup file located in the T: Drive on a system that does not have T: Drive installed
  • Updated the Turbo client installer to add a native image for the Turbo Service
  • Revised naming for Turbo desktop, service, and service host processes
  • Improved various text and error messages

This update includes fixes for the following issues:

  • Fixed an issue where commit failed when using certain dependency layers
  • Fixed an issue causing application launches to fail when using the Launch Configuration Service against the latest Turbo Server with anonymous authentication
  • Fixed an issue where launching a subscribed application would not use a new application version if there was an existing sandbox
  • Fixed an issue preventing subscription of a workspace by different users on the same desktop
  • Fixed an issue where running two two subscription tasks simultaneously could result in one of the tasks hanging
  • Fixed an issue in T: Drive where renaming and editing a file could result in duplicate files
  • Fixed an error message when pushing a malformed image
  • Fixed an exception when running Turbo commands if the Turbo installation folder contained a client version with a malformed version string
  • Fixed a turbo gc error when attempting to remove malformed containers

21.10.2402

The October 2021 update to Turbo Client includes fixes for the following issues:

  • Added Single Sign-On (SSO) authentication from the command line interface using turbo login --auth=sso .
  • Added Integrated windows authentication from the command line interface using turbo login --auth=integrated.
  • Added ability to cancel a download when using Run on My PC.
  • When adding shortcuts from a workspace application using Install On My PC, SVM defined shortcuts are now used by default, except when installing a Web Application.
  • Fixed an issue causing "Sandbox is in use" error message on initial run after installation.
  • Fixed .NET platform installation issues on Windows 7.
  • Fixed an issue when using multiple mount flags such as turbo --mount=c:\invalid --mount=c:\valid, the invalid mount caused all other mountings to fail.
  • Fixed an issue when parsing mount arguments when running from Turbo Server Portal.
  • Fixed an issue where the Turbo CLI did not set the correct exit code from the underlying virtual application.
  • Added ability to connect to a remote session without using Network Level Authentication to avoid using NTLM protocol.

21.7.2350.8

The August 2021 update to Turbo Client includes the following reliability and experience improvements:

  • Improved session state management and reporting to enable new Server 21.7 features. See the Server 21.7 release notes for more details.
  • Added User Agent analytics reporting.
  • Fixed permissions to metadata files when installed and configured for All Users.
  • Fixed permissions when subscribing to a workspace as All Users.
  • Improved turbo config --add-trusted-sources command by defaulting to https protocol if the user omits the protocol.
  • Improved antivirus false positive on dependency adshim.dll.
  • Fixed an error preventing turbo push for very large images.
  • Fixed an error when importing images from Studio 21.5.
  • Allow cloud drive providers to map to other drive letters.
  • Deprecated --mount-if flag from turbo run.
  • Fixed an issue when passing turboplay turbo CLI commands if quoted arguments contained whitespaces.

21.3.2270.0

The March 2021 update to Turbo Client includes the following reliability and experience improvements:

  • Improved error message when applications are run without valid credentials
  • Removed duplicated tracing for output logged to the log file
  • Improved support for installi on web and native applications
  • Added support for custom icons when using installi for Workspace applications
  • Sanitize the installi name for applications with invalid characters in the display name
  • Improved SSL certificate type support
  • Fixed missing feedback for licensed applications that exceed licensing restrictions

20.10.2184.0

The October 2020 update to Turbo Client includes fixes for the following issues:

  • Windows Defender Compatibility issue that could result in an intermittent Could not load assembly error message.
  • Cloud Windowed execution mode is now multimonitor DPI aware. This resolves an issue where streamed windows could be restricted to a small area of a monitor.
  • Command line gci command --trial flag more accurately reports the number of images to be removed.

20.7.2169

The July 2020 update to Turbo Client includes the following new features:

  • Multiple monitor support for Windows Native remote applications.
  • Allow reconnecting to existing sessions when running remote applications.
  • Allow remote applications to display Windows Logon screen messages.
  • Allow access to the user's profile folder when running cloud appications with Merge User Isolation to provide direct HTML5 file upload and download access to user folders.

This update includes fixes for the following issues:

  • Corrected behavior of --offline flag when using installi and run commands.
  • Allow data synchronization when exiting command prompt applications that return non-zero (failure) exit codes.
  • DLL and EXE cache settings not properly applied when running applications from Turbo Portal.
  • File and registry settings for transient components should take precedence over the primary image.
  • Improve application license restriction user experience when the license restriction is triggered from HTML5.
  • Switching domains may not work properly after installing images.
  • Improve security defaults for local machine device keys.

Note ​

The component layering as specified by the Turbo Server Portal was incorrectly ordered in previous version.

Administrators should reverse the ordering of any application components that depend on a specific component ordering.

19.12.2108

New and Improved

  • Support for Turbo Server 20, a powerful new platform that delivers your organization’s applications to all of your devices and the cloud.
  • New Turbo Gateway allows streaming sessions to work over SSL, with no need to open any additional ports.
  • Turbo and all Turbo-supported applications are ready and compatibility tested with the latest Windows 10 Insider Preview, build 18941 (20H1).
  • The new turbo:// protocol no longer requires a separate sign-in for local and natively streamed application launches.
  • The turbo as command can be used to set the Turbo client profile context to the All Users profile, simplifying management of system-wide applications and settings.
  • The installer allows configuration options to be passed on the command line to set default turbo config settings.
  • The Launcher interface has been removed from the client. Launches are now initiated from the Turbo Portal, Start Menu, or third-party integration.
  • Multiple images may be downloaded from a Turbo Hub with a single pull command, eg turbo pull sqlserver,ssms,dotnet
  • Whitelisting and blacklisting of application sources now support wildcard (*) expressions.
  • Added support for SSL digital certificates with a public key size greater than 2048 bits.
  • The turbo uninstalli command can use the --name flag to specify a named installed application.
  • The turbo installi command no longer installs container services to the host system by default. To install a containerized service, use the --register-services flag.
  • Significantly reduced processing time for turbo installi commands when installing large images.
  • The turbo installi command does not pull the image by default. To force download of the image, use the --pull flag.
  • The path for the All Users image repository can be now be configured via the turbo config --image-path=&path& --all-users command.
  • The expiration period for unused application images during cache cleanup can now be configured using the turbo config --gci-expiration command. The default has been changed from 30 to 90 days.

Bug Fixes

  • The MSI installer does not scale with DPI settings.
  • May show a “Sandbox already in use” error when launching multiple shortcuts for the same application very quickly.
  • Does not show an appropriate error message when a shortcut launch fails due to a network error.
  • Does not refresh the login session or cloud regions if the initial network connectivity check fails due to a network error.
  • The installer now disables automatic Turbo updates when installing for All Users on the system. Administrators should push Turbo client updates using their desktop management infrastructure.
  • Does not show the image buffering dialog while dependency images are being downloaded.
  • Integrity Software SofTrack may interfere with startup of containerized applications.
  • The turbo push command fails to push icons to the image repository on systems that have FIPS Compliance enabled.
  • The turbo config command does not display correct Turbo Drive settings.
  • The turbo commit command appends a suffix to ProgIDs resulting in broken associations for certain applications.
  • The turbo commit command captures changes to classes in the HKCR registry hive instead of the HKCU hive as in Turbo Studio.
  • The turbo installi command automatically downloads the latest Turbo VM even if a different version is requested by the user.
  • The turbo uninstalli command shows an error message for containerized services that were never installed.
  • The turbo uninstalli command fails if the image name contains an underscore character.

19.4.1964.21

New and Improved

  • Containers startup performance is significantly faster.
  • Local images can be viewed and removed using the Manage Cache dialog.
  • Garbage collection is used to remove files that are no longer used, such as sandboxes from old client versions.
  • Automatic garbage collection for old images can be turned on by setting the turbo config --gci-interval. Garbage collection will periodically check for images that have not been used in 30 days.
  • Users may set the maximum size of the local image repository via turbo config --image-cache-size.
  • Application sources may be marked as trusted or blocked via turbo config --add-trusted-source|--block-trusted-source|--remove-trusted-source=[source].
  • Access to local network from cloud applications may be managed via turbo config --enable|--disable=localnetworkaccess.
  • Added option for turbo commit --working-dir=current-dir to set the working directory of the committed image to use the active directory when the container is launched.
  • Installation flags may be passed to the MSI Installer.

Bug Fixes

  • The turbo installi and install commands overwrite existing shortcuts.
  • The turbo run command overwrites local image with hub image if using the same name.
  • The turbo commit command sets incorrect file permissions when image path is set to all users.
  • Launch configs are not re-downloaded if the local cache becomes corrupted.
  • The Run in Cloud option fails when logging in on-premise portal after being logged in Turbo.net Hub.
  • Old Programs and Features entry is not removed when client is upgraded.
  • Turbo for PC does not clear the Username field on the Sign In dialog when using ADFS SSO.
  • Turbo for PC crashes when the Server field on the Sign In dialog is cleared.
  • Turbo for PC is unable to sign in using anonymous authentication.
  • Turbo for PC window height is too big when undocked.
  • Turbo for PC does not work with favorites when connected to a legacy Portal Server.
  • Portable applications are not compatible with Hub Server 18.

19.3.1946

New and Improved

  • Added --no-auto-update to installer to disable auto-updates to the latest version
  • Added --offline flag for installi command so it can be executed offline
  • Added ability for install commands to add ProgIDs if defined in container image but not bound to a file association (ex: for protcol handlers)
  • Added new flags for install/installi command to control how shortcuts and file associations are registered
  • Added ability for Turbo Launcher to write trace logs to file
  • Added support for latest Turbo Hub Server
  • Removed java dependency for internal tools

Bug Fixes

  • Sandbox manager process may restart when redirector failed to get new rules
  • Login errors to SSO providers not shown
  • Users logging in for the first time to an SSO provider were not automatically assigned to the correct workspace
  • Installi command used the wrong image when computing the default name
  • Uninstall command failed if multiple containers existed with the same name
  • Install command failed to use the correct startup file in shortcuts
  • Login to Turbo Hub Server configured for anonymous access failed
  • Visual artifact on login form of Turbo Launcher after install

19.2.1926

New and Improved

  • Adds support for ADFS authentication for local execution on PCs
  • Adds support for ADFS2 to the SSO authentication methods

Bug Fixes

  • Turbo for PC does not check if a server is using SSO authentication if a previous query failed
  • Turbo for PC may not honor the Remember me option when installed for All Users

19.2.1915

New and Improved

  • Added new application configuration turbo:// protocol type
  • Added new security validation dialogs for launches via turbo:// protocol links
  • Launches via turbo:// protocol links display a security dialog for applications outside of Turbo.net
  • Administrators can define trusted workspaces for all users in %PROGRAMDATA%\Turbo\Containers\trusted-sources.json.
  • Added support for on-premises workspaces
  • Combined client toggle settings under turbo config --enable|--disable=[option] command.
  • Administrators can set default or override settings for the client configuration using turbo config --as-inherit|--as-override command.
  • Added ability to disable merge isolation using turbo config --disable=mergeisolation command.
  • Added --working-dir|-w=[path] flag to turbo commit for setting the working directory of an image.
  • Added the Java component to the Turbo for PC installer to support systems that are not connected to the Internet.

Bug Fixes

  • Turbo for PC fails to launch application on the local PC when a cloud container session is not synchronized to the local system.
  • Turbo for PC now respects network rules specified in application settings.
  • The login dialog may fail to detect when an on-premises workspace is using an SSO authentication method.
  • Certain applications may crash on application exit due to a race condition.
  • Applications may fail to start with an “Object reference not set to an instance of an object” error.
  • A new application version is downloaded even when upgrade check is disabled on application startup.
  • Running the clean and base images with incompatible isolation should display a warning message.
  • The turbo config --image-path=allusers command may fail with invalid container storage path error.
  • The turbo-plugin.exe --app-server command to provision application servers should detect incompatible OS versions.

18.12.1831

New and Improved

  • Image upgrades with layered session state preservation are now performed by default during turbo run.
  • Isolation mode override flag --isolate=[full|write-copy|merge] is now available for portable application outputs.
  • Support for additional Security Support Providers (SSPs), enabling authentication via Kerberos, NLA, and more.
  • The Turbo for PC installer now uses HTTPS to download components.
  • The Turbo for Mac client has been updated with improved support for copy-and-paste between native and virtualized environments, support for the Windows hidden files flag, and improved diagnostic logging.
  • The Turbo for Android and Turbo for Chromebook clients now support Single Sign-On.
  • The working directory may now be specified in the image configuration. The clean image has been updated to maintain backwards compatibility with the new behavior.

Bug Fixes

  • Images are not extracted in the local repository folder when using portable applications.
  • Subsequent executions of a portable executions may crash under some circumstances.
  • The installer UI may not disappear until the associated portable application is closed.
  • The turbo rm command fails when an improperly named container folder exists.
  • The turbo installi command may check the local user repository for images even when the --all-users flag is specified.
  • The turbo installi command may not create a valid application shortcut when startup file arguments are specified.
  • Turbo for PC ignores the Allow access to local user folders setting when using on-premise Hub Server.
  • Improved support for Azure AD and ADFS authentication in Turbo for Mac.

18.11.1806

New and Improved

  • Support for containerizing Cygwin (Linux environment on Windows)
  • Support for additional Security Support Providers (SSPs), enabling new authentication methods
  • Containers now respect the working directory setting from the image configuration. (Previously the working directory was based on the current directory of the turbo.exe process.)
  • Turbo VM honors the SYSTEM attribute for virtualized files.
  • Ability to set the minimum thread stack size in the image configuration

Bug Fixes

  • Turbo Client installation can fail if the installer is not executed from the correct folder.
  • The turbo pull command is not listed in turbo help.
  • Fixed behavior of container thread local storage (TLS) initialization
  • Fixed behavior of asynchronous I/O into sandbox

18.7.1755

New and Improved

  • New! Access your local network by visiting localhost.turbo.net
  • New! Use the T: drive to access your local OneDrive folder

Bug Fixes

  • Fix UI responsiveness when clicking the refresh button

18.3.1699

New and Improved

  • New! Support for SQL Server Management Studio 2017
  • New! Upgraded to Microsoft .NET Framework 4.6.2 component to support TLS 1.2
  • New! Improved performance for large executables/DLLs, including Microsoft Power BI
  • Improved handling of side-by-side assemblies, manifests, and policy files in containers

Bug Fixes

  • Logs from Turbo VM are written to OutputDebugString if an error occurs during initialization
  • Jobs sent to the print spooler from containerized applications may fail to print.
  • The Turbo Launcher is unresponve while loading a large list of application versions.
  • The turbo commit command fails when using old images with an incorrect error message.
  • The metadata for the Turbo Client MSI installer is incorrect.

18.2.1692

New and Improved

  • New! Launch applications in the Turbo.net cloud.
  • Applications launched in Turbo.net cloud can open and save files to the local disk.
  • Improved handling of directories mounted to containers with the --mount flag.
  • Turbo Client stores images to the temp folder when image storage path is read-only.
  • The turbo installi --honor-setup-info command registers all shortcuts defined in the application configuration to the Start Menu.

Bug Fixes

  • Some storage paths are not inherited correctly when configured for All Users.
  • The turbo uninstalli command fails when specifying an invalid image.

Notes

  • Removed --startup-file-default flag from turbo new, try, run, and start commands.
  • Removed --install flag from turbo new and run commands.

Turbo.net © 2025