Windows Release Notes

Managed Windows deployments

If you are using MDM software to deploy the Twingate Windows Client, download the release version you require from the list below. If you have disabled optional updates or users do not have local admin rights, you will need to manage Twingate Windows client upgrades for users.

Additional information on Windows MSI command line options can be found here.


If you are not using a managed deployment method with an MDM solution like InTune or Microsoft Endpoint Manager, and you have local admin rights on your device, you can install Twingate by visiting Learn more

Release notes


Release Date

MSI download for managed deployment



June 2nd, 2021


Support for a new authentication flow that no longer prompts the user after successfully authenticating with the identity provider.

The client will now correctly display resources with underscores in their label.

Resolved a small visual bug with the Twingate icon in dark mode.

Resolved an issue that would prompt the user to upgrade the application even when deployed via MSI with updates disabled.


May 18th, 2021


Support for device metadata reporting.

Increased default connection timeout to improve compatibility with long data idle periods in persistent connections.


March 26th, 2021


Significant performance improvements for traffic that bypasses Twingate.


March 22nd, 2021


Added support for unqualified domain names defined as Resources.

Support for port restrictions on Resources, which requires upgrading your Connectors to v1.20 or later.


March 1st, 2021


Added "Start at Login" functionality, which can be toggled by the user, and is set to start the Twingate client at login by default.


February 10th, 2021


This release contains a number of incremental performance improvements and bug fixes. Notably, we have improved data throughput for protocols that send small packets. This performance improvement also requires upgrading your Connectors to v1.18 or later.


December 7th, 2020


The Twingate client now runs a number of checks before starting to ensure that it will be able to connect to your Twingate network. These include whether DNS is configured correctly and warn the user if another VPN is running.

After a user has successfully authenticated and connected to Twingate, the client now shows a list of what Resources that user has access to with a convenience link to open the Resource address in a browser. Admin users will additionally see convenience links directly into the Twingate Admin console.


November 5th, 2020


The Twingate Windows client now runs using a privileged Windows service and an unprivileged user interface. This means that users no longer need local admin rights to run Twingate.

The Twingate system service needs to be running in order for users to be able to connect to Twingate. A current restriction is that multiple local users on the same device may not run Twingate at the same time.

Updated 11 days ago

Windows Release Notes

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.