New on, week of July 18

Improved Error Handling in TurboScript provides thousands of images ready to go in the Hub. But if one of those doesn’t do the trick, TurboScript is a great way to create your own images.

In the past, TurboScript error messages were often confusing, leaving you clueless about the cause. A script may look correct but gives a parse error when executed, with no further information.

For example, could you have spotted what’s wrong in this example?

Useless Error Message
Here is another example. What equal sign is wrong and why?


The latest Turbo Client now provides much more explanatory help text for any failed command, including inline information and suggestions. Let’s retry the above examples with the newest clients.

First example: Aha, the import command needs a type specified!


Second example: Looks like the hosts command doesn’t need a equal sign:



The newest Turbo Client including error handling updates is now available on If you already have Turbo installed you will be automatically upgraded within 72 hours. Enjoy!

Running Containers as Different Domain Users

By default Turbo containers will run in the security context of the user executing the turbo command. But what if we need to run as a different user?

In this example, let’s run SQL Server Management Studio as a different domain user than the currently logged in user.  In our scenario we have the Turbo Sandbox Manager installed in the local profile, which is the default behavior.

Our first attempt is to just use the runas command to execute the command turbo run ssms2012:

> runas /user:user@domain "turbo run ssms2012"
Enter the password for user@domain:
Attempting to start turbo run ssms2012 as user "user@doamin" ...
RUNAS ERROR: Unable to run - turbo run ssms2012
5: Access is denied.

Unfortunately with the Turbo Sandbox Manager installed in my local profile I cannot use runas to run SSMS in the user context I want since it does not have access to that user’s profile!

One workaround then is to install Turbo for all users via MSI and then use runas:

> runas /user:user@domain "turbo run ssms2012"

This works well — except we may not want to reinstall the plugin, or may not want to install it for all users.

We can solve this by using runas with the /netonly flag:

> runas /netonly /user:user@domain "turbo run ssms2012"

The /netonly flag forces the application to use the runas account for remote resources and the logged in account for local resources.

New on, Week of July 11

Turbo Client and VM Updates, July 5

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

New and Improved

This update includes the following new features and improvements:

  • New! Support for window object isolation in TurboScript provides fine grained control over interprocess communications (IPC). See the isolate command for TurboScript for more information.
  • Significant container engine updates to reduce false positives with anti-virus software.

Bug Fixes

This update includes fixes for the following issues:

  • 64-bit applications crash when Avast anti-virus is installed
  • Container fails to start when adding a period to the startup file results in an invalid path
  • Applications are not scaled correctly when Windows DPI settings are changed from the default
  • Sophos Home anti-virus blocks DNS requests for applications
  • IP whitelisting for subdomains does not work in Internet Explorer containers
  • Taskbar jump list actions for new versions of Skype fail with missing DLL errors
  • Elasticsearch throws an exception when configuration files are not written to the sandbox
  • Microsoft Office InfoPath crashes immediately after starting
  • Internet Information Services (IIS) container fails to start without configuration updates
  • Loading cheous.dll module prevents other DLLs from being loaded due to conflicting paths

Version Numbers

The component version numbers for this release are:

  • Turbo VM: 11.8.979

New on, Week of July 4

“An Introduction to Turbo Containers” talk by Turbo founder Kenji Obata

This talk by Turbo founder Kenji Obata was given at the E2EVC conference in Las Vegas and walks through the highlights of Turbo containers.

Turbo Client Updates, June 20

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

New and Improved

This update includes the following new features and improvements:

  • New! Rules for automatic URL Redirection to Turbo browsers can optionally be defined in the Windows Registry. Registry rules can also redirect Turbo browsers back to the host browser.
  • Container right-click context menu DLLs can be defined in TurboScript using the shellextension instruction.
  • Streaming application images from the Hub has been disabled by default. Streaming can be manually enabled using the --stream flag.
  • The Turbo Client MSI installer no longer includes the TurboLauncher.
  • Rules for URL redirection are refreshed periodically.
  • Branding for the Turbo Client has been updated.

Bug Fixes

This update includes fixes for the following issues:

  • Launching containers that are created with the turbo installi command may encounter a login error because the device key is not specified.
  • turbo push fails with a specified TurboServer with a “Could not load file or assembly” error.
  • URL redirection rules may not be applied when clicking on a link in Internet Explorer.
  • Additional components of the Turbo Client are signed with a digital certificate.
  • Container fails to start when double-clicking a registered file extension with an “Item has already been added” error.
  • Synchronization bug causes container startup to be excessively slow.
  • turbo help output poorly formatted when help text is too long.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1109
  • Turbo Extension for Chrome: 3.33.1109