Turbo Client 26.2.14.0

This 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.
• Improved proxy latency detection for launches that use a proxy
• New --disable-proxy-resolve-via-proxy launch flag disables resolving hostnames via proxy
• turbo config proxy commands now support --all-users
• Install now starts the user Sandbox Manager automatically
• Uninstall now removes all-user subscriptions and Add/Remove Programs entries
• MSI uninstall now supports --delete-user-data to remove user data during uninstall
• --network no longer scrambles port mappings as part of network isolation
• Improved image download network outage resilience with better retry logic
• Changed default image pull behavior to prefer local images first, reducing dependency on hub availability
• New turbo config --p2p-mode configuration allows control of peer-to-peer download behavior
• Containers are now automatically created when mounting from a not-yet-created container
• 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
• Client log format changed to a more standardized format
• Multiple logging improvements

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
• The all-users assembly cache was not being used
• turbo rmi -a cleared permissions set by turbo config --image-path=allusers --permission=write
• turbo rmi -a from admin command prompt reported success even if the delete failed due to permission errors
• turbo precache reported exit code 0 when cache operations failed
• turbo import vm falsely reported "image already exists" error when the VM version did not exist
• --no-pull flag did not correctly prevent image downloads
• Mounts did not work correctly when Desktop/Documents folders were redirected to OneDrive locations
• Application launches failed if the startup file came from a mount source
• Mount validation error occurred when Windows known folders (e.g., Downloads) were moved to non-default locations
• Proxy resolution could hang when a proxy server did not respond during SOCKS5 handshake, causing long command startup delays
• Launches could fail if the proxies.json file was locked
• 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
• TurboDrive could encounter DateTime parsing errors when using certain system date and time formats
• Subscription applications could remain installed after Active Directory access was revoked
• Merged VM settings could serialize incorrectly, leading to unexpected VM settings being applied
• Remote sandbox failed on Azure AD joined computers
• Application could fail to register due to special characters
• Run commands reported an incorrect Windows version string in recent Windows versions
• Device keys could collide if two devices shared the same machine name