TurboServer Update 17.0.493

TurboServer is an on-premise version of the Turbo.net Hub designed for enterprise environments.

The Turbo Server 17.0.493 update is now available at: turbo.net/server/download.

New and Improved

This update includes the following new features and improvements:

  • New! Support for Mozilla Firefox 50+ using the new extensions system.
  • Upgraded the Apache component to version 2.2.32.
  • A sample application is available by default when TurboServer is installed in Portal mode.

Bug Fixes

This update includes fixes for the following issues:

  • TurboServer does not update the Turbo Client component during an upgrade.
  • TurboServer does not allow anonymous users to launch containers past the trial expiration date.
  • TurboServer does not prompt the user to install Turbo Client when clicking on links that require it.
  • TurboServer creates a folder on the host system drive at C:\.

Version Numbers

The component version numbers for this release are:

  • Turbo Server: 17.0.493

Turbo Studio Update 17.0.886.13

Turbo Studio is an easy-to-use graphical editing tool for creating and editing Turbo  environments.

The Turbo Studio 17.0.8886.13 update is now available at: turbo.net/studio/download.

New and Improved

This update includes the following new features and improvements:

  • New! Build Portable Application EXEs with an on-premise Turbo Hub Server back-end in addition to the cloud-based Turbo.net Hub.
  • New! All official repositories from Turbo.net Hub are available to any user via the Template and Import application configuration wizards.
  • Improved! New isolation rules are applied when using the Template wizard to build ISV Application EXEs and Layers for Turbo Portal Server.
  • Image dependencies are packaged into ISV Application EXE outputs as well as applications pushed to Turbo Portal Server.
  • Temporary .XAPPL configuration backups are created when saving as a recovery option for data corruption.

Bug Fixes

This update includes fixes for the following issues:

  • Turbo Studio fails to communicate with the Turbo.net Hub when the Turbo Client has been logged in a Turbo Hub Server.
  • The mailto: protocol does not get captured correctly in a snapshot configuration.
  • Outputs are built with an incorrect file icon if a startup file is not defined in the configuration.
  • Turbo Studio ma fail to profile an application properly.
  • Turbo Studio may fail to harvest using the Microsoft Office 2010 recipe.
  • Turbo XStudio fails to import MSI installer files.

Version Numbers

The component version numbers for this release are:

  • Turbo Studio: 17.0.886.13
  • Turbo VM: 11.8.1120.8

Turbo Client and VM Updates, March 15

Users will be automatically updated to the latest version of Turbo Client and VM.

New and Improved

This update includes the following new features and improvements:

  • New! Isolate container processes with the IsolateProcessNames container VM setting. Example: turbo run --enable=IsolateProcessNames
  • New! Disable access to non-system drives (for example, everything other than C:\) with the IsolateNonSystemDrives container VM setting
  • New! Disable access to network file shares with the IsolateNetworkShares VM setting
  • New! Build Portable Application EXEs that use a private self-hosted Turbo Hub Server instead of the Turbo.net Hub
  • Improved! Optimized synchronization performance and memory usage
  • Synchronization process works properly through proxies when a self-signed certificate in the Windows certificate store is used
  • User interface improvements

Bug Fixes

This update includes fixes for the following issues:

  • The Firefox browser extension does not work if the Turbo.net client is installed for all users.
  • Applications launched via the Turbo.net browser extension may fail to start when many users are logged on the operating system at the same time.
  • Network route blocking does not block specified hostnames when using a proxy server.
  • Portable applications built with the data synchronization option enabled fail to start with a login error.
  • The turbo netstat command fails to find the specified container.
  • TurboPlay fails to load application models from the local filesystem or network share.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1488.10
  • Turbo VM: 11.8.1120.8

New on Turbo.net in March

The following applications have been added or updated on Turbo.net for March:

Follow @turbobuild for up-to-the-minute updates, and send your requests to us at @turbohq.

Turbo Client and VM Updates, January 27

Users will be automatically updated to the latest version of Turbo Client and VM.

New and Improved

This update includes the following new features and improvements:

  • New! Support for Firefox 50 and up using the Mozilla extensions platform.
  • New! Export logs for a container using the turbo logs --export=[path] [container] command.
  • Improved! Improved responsiveness of progress indicator for long-running sync operations.
  • Improved! Portable EXEs prompt the user to accept the user agreement of the repository.
  • Control which paths of the container are synchronized using the sync command for TurboScript. See the documentation for more information.
  • Turbo Client installer prompts the user to accept the terms of service before proceeding with the installation.
  • Portable Application outputs may be configured with a trial expiration date.

Bug Fixes

This update includes fixes for the following issues:

  • Sophos HitmanPro may cause the Turbo Client and Turbo applications to crash.
  • Avast Antivirus may cause Turbo applications to stop working when a file dialog appears.
  • Portable EXEs fail to start if one of the packaged images already exist on the system and the file is in use.
  • Configured shims are executed multiple times on startup and shutdown of Turbo application.
  • Turbo Installer may fail to push an image with an “index out of range” error.
  • Container may fail to start with an error that the local sandbox cannot be cleaned.
  • Images pushed to Turbo Hub that do not have an explicitly set startup file may show an incorrect icon on their repository page.
  • Compressed Turbo applications may crash due to memory exhaustion.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1465.0
  • Turbo VM: 11.8.1100.4

Turbo Client and VM Updates, January 3

Users will be automatically updated to the latest version of Turbo Client and VM.

New and Improved

This update includes the following new features and improvements:

  • New! Generate a Portable EXE using the turbo export [image] --type-exe command.
  • Improved! Significant speed improvements for image pushes and pulls and container synchronization.
  • Improved! Improved user experience for Portable EXEs, including support for setting the default launch options.
  • The turbo commit command automatically selects the startup file for the output image when the target container has a single startup file.
  • The turbo push command automatically sets the icon for the image on its Turbo Hub repository page.
  • The turbo continue command passes arguments following the -- flag to the container.
  • New client uninstall options: /delete-user-data/uninstall-launcher/uninstall-redirector (see the client documentation for more information).

Bug Fixes

This update includes fixes for the following issues:

  • Internet Explorer 6-10 fail to access whitelisted addresses when --route-block=ip is specified.
  • Portable EXEs fail to run if turbo config --image-path is used to set a custom storage path.
  • Synchronization may sometimes fail with a “key not found” error.
  • The buffering dialog may remain visible when the application or container has already started.
  • The turbo continue command fails to resume a container if the tagged image has been overwritten on the Turbo Hub.
  • The turbo continue command fails to resume a container with an “insufficient permissions” error if the state was created with a Portable EXE.
  • The turbo commit --startup-file=[path] and turbo inspect commands do not use path tokens for the startup files.
  • The turbo inspect command does not show which startup file is set as the default.
  • TurboInstaller.exe is missing its digital certificate.
  • TurboLauncher does not show results when searching the Turbo Hub.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1436.0
  • Turbo VM: 11.8.1062.2

New on Turbo.net in January

The following applications have been added or updated to Turbo.net for January:

Follow @turbobuild for up-to-the-minute updates, and send your requests to us at @turbohq.

Turbo Client and VM Updates, December 13

Users will be automatically updated to the latest version of Turbo Client and VM.

New and Improved

This update includes the following new features and improvements:

  • Shortcuts for installed applications are now placed in the Start Menu root folder for faster access.
  • Running a Portable EXE does not automatically start the TurboLauncher.
  • Text for various dialogs and error messages has been updated for improved clarity.

Bug Fixes

This update includes fixes for the following issues:

  • Google Chrome 55 browser tabs fail on startup.
  • Java applications launched via JNLP fail when using JRE version 8.
  • Running or installing an application may fail with an access denied error due to incorrectly set file permissions.
  • The command prompt cursor may move erratically during turbo push and pull commands.
  • The turbo run command does not correctly update the container images when the --enable-sync and --upgrade-from flags are specified.
  • The turbo config command does not prompt for UAC elevation when the --all-users flag is specified.
  • The turbo rm command may fail to remove a container with an unhandled exception error.
  • Synchronization fails to include all images in the total size calculation resulting in progress that exceeds 100%.
  • Installed applications fail to synchronize container data when using Turbo Hub Server.
  • Start Menu shortcuts for installed applications fail to start when the turbo config is used to change the hub URL.
  • Launching an application via the Start Menu shortcut does not show progress for container data synchronization when the option is enabled.
  • The Turbo Client install dialog does not scale correctly when Windows uses a high DPI setting.
  • Clicking on My Files in TurboLauncher generates an error when Windows Explorer fails to restart after the client is installed.
  • Portable Application outputs may use settings from another application because the setting storage path is not sufficiently unique.
  • TurboLauncher may fail to properly load application tiles.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1409.0
  • Turbo VM: 11.8.1062.0