Silent install command for Turbo.net Desktop 26.3.11.2687

The exact silent switches the Turbo.net Desktop installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.

One-line silent install (x64, user scope)

turbo-client-26.3.11.2687.exe --silent

Run from the directory containing turbo-client-26.3.11.2687.exe. Download the installer from the Direct link below first.

Architecture	Scope	Type	Silent switches	Source
x64	user	EXE		Declared by publisher
x64	machine	EXE	Custom: --all-users	Declared by publisher
x64	machine	MSI		Default for MSI
x86	user	EXE		Declared by publisher
x86	machine	EXE	Custom: --all-users	Declared by publisher
x86	machine	MSI		Default for MSI

Declared by publisher means the switches come straight from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs.
Default for {type} means the manifest doesn't specify silent switches, so the framework's standard switches are shown (e.g. /S for NSIS, /quiet /norestart for MSI).

Frequently asked questions

What is the silent install command for Turbo.net Desktop?

Turbo.net Desktop uses EXE. After downloading the installer, run: turbo-client-26.3.11.2687.exe --silent. The silent install switches are --silent.

How do I deploy Turbo.net Desktop via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id CodeSystems.Turbo --exact 26.3.11.2687 --silent --accept-package-agreements --accept-source-agreements. If winget isn't viable in your environment, package the publisher's installer directly using the silent switches above.

Where do these silent switches come from?

The switches marked "Declared by publisher" come from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs. Switches marked "Default for EXE" come from the installer framework's documented defaults.

Prefer the winget route? See the full Turbo.net Desktop install page.