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

Turbo partners with Perinova in Germany and Switzerland

Turbo.net is pleased to announce a partnership with Perinova IT-Management GmbH of Germany.

Perinova will provide Turbo.net enterprise consulting and implementation services in Germany and Switzerland.

“Perinova has offered its clients consulting and support in the field of application virtualization for over 10 years. Perinova has years of experience working with Turbo technologies in third-party products. This new direct partnership strengthens our existing cooperation and offers our mutual customers in Germany and Switzerland access to Perinova’s unique experience and depth in Turbo containerization and application virtualization technologies.”

For more information on Perinova IT-Management, visit their web site at http://perinova.com.

If you are interested in joining the Turbo Partner Program, please contact partners@turbo.net.

Browser Sandbox now available on Mac!

We are pleased to announce the availability of Mac and cloud execution support in the Turbo.net Browser Sandbox.

The new Browser Sandbox can run containerized browsers in the cloud via an HTML5 interface that runs on any device with an HTML5-enabled web browser.

Try the new Browser Sandbox now at http://turbo.net/browsers.

You can also run browsers on your local desktop when using a compatible Windows device. Turbo.net automatically synchronizes containers between desktops and the cloud so your applications are available anywhere.

Local or Cloud

Turbo.net will automatically select the best execution option (Local or Cloud) based on your device type. To manually select an execution mode, click on the arrow on the Run button to expand run options and select the preferred execution mode.


More Browsers

The Turbo.net Browser Sandbox now provides all versions of major browsers including Internet Explorer, Chrome, Firefox.

Chrome and Firefox images are automatically updated as new updates are released. Every legacy version is available for execution on demand.

Browsers can be configured with any combination of plugins and runtimes, including Java, .NET, Flash, and Silverlight.

Browser Sandbox also includes nightly Chrome Canary and Firefox Nightly builds and Firefox Mobile. Containerized browsers are a easy and safe way to test and develop against non-production builds of Chrome and Firefox.


A set of popular browsers are available free to use for evaluation purposes.

Turbo.net Pro subscribers can use the new cloud functionality at no additional charge for session lengths up to 10 minutes. (Additional cloud session time available separately.)

The Turbo.net Pro subscription is just $9.95 per month and includes the ability to create customized browsers and applications, run containerized servers, use Turbo Studio, and much more.

Upgrade to Turbo.net Pro Now

We hope you enjoy this major upgrade to the Browser Sandbox!
-- The Turbo Team

Turbo Studio 17 Now Available

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

The latest version of Turbo Studio includes direct integration with the Turbo.net Hub, an installer based wizard alternative to snapshots, the ability to create portable container (single EXE) outputs, new subscription-based licensing, as well as support for the latest Windows operating systems.

Turbo Studio 17 is available now at: turbo.net/studio/download.

New and Improved

This update includes the following new features and improvements:

  • New! Studio 17 directly integrates with the Turbo.net Hub. Templates and import wizards are automatically updated with continuously updated Hub content.
  • New! New Portable Applications (.exe) output mode generates portable containers with Turbo Client embedded, all in a single EXE.
  • New! Create applications by installing the application (MSI or EXE) into a container console. This alternative to the snapshot process does not require a clean operating system and does not dirty up the host filesystem or registry.
  • New! Support added for Windows 10 “Redstone 2” pre-release versions.
  • Studio available in MSI format and scriptable legacy XStudio command-line tool.
  • Ability to configure the Minimum OS Requirement for images.
  • Internal Turbo VM version has been updated to 11.8.1060.

Bug Fixes

This update includes fixes for the following issues:

  • Projects containing dependencies on the Turbo.hub Hub fail to build.
  • Containerized ProgIds are not fully isolated.
  • Renaming a folder incorrectly fails with a message that the resource is used by another process.
  • Failure to deinitialize and flush streams may cause missing file writes in specific scenarios.
  • Virtualized applications can crash if started from multiple paths.
  • Product version is not set correctly when the metadata field is set to inherit from the startup file.
  • Trailing spaces are trimmed incorrectly for file paths with arguments.
  • The command-line XStudio.exe tool does not recognize some encodings for the license file.
  • An error may occur pushing a XAPPL configuration with a service to the local repository or the Turbo.net Hub.
  • Many user interface fixes and improvements.

Version Numbers

The component version numbers for this release are:

  • Turbo Studio: 17.0.794.0
  • Turbo VM: 11.8.1060

Getting Turbo Studio 17

Turbo Studio 17 is available for download at turbo.net/studio/download.

Any Turbo.net user with a Pro subscription can use Turbo Studio 17 by signing in with their account. Studio may be used in a limited fashion by Free users for evaluation purposes.

The ISV upgrade to Turbo Studio 17 is available for free to all licensed users of previous versions of Studio on active maintenance. For commercial users of previous versions, a new license key is available from the account management page of your Turbo.net account.

We hope you enjoy Turbo Studio 17!

Turbo extension for Microsoft Edge

Microsoft Edge is the latest browser for the Windows 10 platform. In the Windows 10 Anniversary Update (build 1607), a browser extension feature was added to allow custom functionality to be built by third parties.

Edge support for third party extensions is very new and limited. Therefore, multiple manual steps are required to enable the Turbo Edge extension. This process should be simplified as Edge extension support matures.

Follow the steps below to enable the Turbo.net extension.

Enabling the Turbo Edge Browser Extension

Step 1: Ensure that you have the latest Turbo.net Client installed.

Step 2: Enable Edge communications to localhost via the command below:

# Run this command in an elevated, administrator command prompt
> CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe

All applications which are built with Windows 10 “Modern UI” architecture have disabled access to the local machine network. The Edge browser is built on this architecture so access to localhost is disabled. The Turbo.net browser extension requires communication with local services provided by the Turbo client runtime in order to allow coordination with the Turbo Sandbox Manager.

Step 3: Enable Edge browser extensions by typing about:flags into the browser’s location bar and checking the Enable extension developer features checkbox.
Once enabled, you’ll need to restart the browser.

Edge Enable Extension

Step 4: Load the Turbo.net extension by clicking on the Edge options menu dropdown and selecting Extensions.

Edge Extension Menu

This will show the Extensions menu.

Step 5: Click on Load Extensions and select the path to the Turbo.net Edge extension in the client install directory, which may be at one of the following locations depending on your environment:
a) c:\users\[user]\appdata\local\spoon\[version]\edge
b) c:\program files\spoon\[version]\edge
c) c:\program files (x86)\spoon\[version]\edge

Edge Load Extension

Step 6: Once loaded, the Turbo.net Extension will show up in the list of extensions that you have enabled for Edge. You will again need to restart your browser in order for the extension to be enabled.

Edge Turbo Extension

Step 7: Edge automatically disables extensions for the first 10-seconds when it is started. After that time a banner prompt will be shown on the bottom asking to turn them on. Click the Turn on anyway button to enable them.
Currently this step is required every time you start the Edge browser.

Edge Turn On Extension

At this point you’ll be able to use Turbo.net functionality!

Edge Running Turbo Container