The Twingate Windows client is distributed in an MSI package in order to allow automated managed device deployment.
We also maintain a historical public changelog of prior releases.
Since version 2023.206, the Windows client requires the .NET Desktop Runtime 6.0.0 (x64) or higher. The MSI installer does not include the .NET Desktop Runtime. When installing the client via the MSI, you must manually install .NET Desktop Runtime alongside the client if not already installed.
The MSI package supports a number of command line options that are useful for automated deployments:
- Silent installation. The
/qnoption will suppress the installation dialog and automatically accept the user terms of service.
- Pre-configure the Twingate Network. The
network=option allows pre-configuring the Twingate Network name so that users do not have to enter this information.
- Disable automatic updates. Setting
no_optional_updates=truewill disable optional updates. See the next section for more information on why you might want to do this.
- Configure NCSI global DNS. Setting
NCSI_GlobalDns. Enable this option if users are experiencing a false “No internet” NCSI while Twingate is running.
In this example, this will install the Twingate Windows client, setting the Twingate Network to
beam reach.twingate.com and disable optional updates.
TwingateWindowsInstaller.msi /qn network=beamreach.twingate.com no_optional_updates=true
Usually, yes, but this depends on whether you allow users to have local admin rights on their Windows PC. Automatic updates cannot be installed without the local user providing administrator authorization, so if you do not allow local admin rights, you should disable automatic updates. The MSI command-line setting allows flexibility for different user groups depending on their local admin permissions.
- If you allow local admin rights: We recommend you leave automatic updates enabled (this is the default). Users will be prompted when an update is available and asked to update the Twingate client.
- If you do not allow local admin rights: You should disable automatic updates. This is because, if optional updates are enabled, users will receive update availability prompts but will not be able to update the client. New versions of the Twingate Windows client must instead be pushed to users via your MDM solution.
Chocolatey packages are not currently updated as part of our automated release pipeline so package updates may be subject to delayed release.
With Chocolatey installed, Twingate can be installed with a single command:
choco install twingate
Last updated 2 months ago