Windows Client Migration to .NET 10

.NET 10 migration overview

On November 10, 2026, Microsoft is ending support of .NET 8. As a result, the Twingate Windows Client is moving to .NET 10, starting with a release in late October 2026. Devices running that version of the Windows Client or later need the .NET 10 Desktop Runtime installed.

How this impacts Windows devices

The Twingate Windows Client EXE installer automatically installs .NET 10 as a prerequisite. Updates installed from within the Client also install the runtime automatically. You can download the Twingate Windows Client from our Client download page. Administrators who deploy the EXE installer to remote devices can continue to do so without any changes.

If you deploy the Twingate Windows Client with our MSI package, you need to install the .NET 10 Desktop Runtime on each device. Download the .NET 10 Desktop Runtime x64 from the Microsoft website. Push the package out through your MDM solution or install it manually on each device.

To deploy the .NET 10 Desktop Runtime package remotely, use the following flags to install it silently:

c:\path\to\windowsdesktop-runtime-10.0.x-win-x64.exe /install /quiet /norestart

Replace 10.0.x with the version in the file name you downloaded.

The .NET 10 Desktop Runtime installs side by side with .NET 8. You don’t need to uninstall .NET 8 first, and other applications that depend on it continue to work.

Once the .NET 10 Desktop Runtime is installed on each device, future versions of the Twingate Windows Client will run as expected. You can continue to deploy updated versions as they’re available.

→ Windows managed devices

→ Deploy the Windows Client with Microsoft Intune

FAQ

Q: When will the Twingate Windows Client move to .NET 10?

A: The Twingate Windows Client will move to .NET 10 as part of the release in late October 2026, ahead of .NET 8 reaching end of support on November 10, 2026.

Q: What happens if I don’t install the .NET 10 Desktop Runtime on my Windows devices?

A: If the .NET 10 Desktop Runtime is not installed on a Windows device, the .NET 10 version of the Twingate Windows Client and later versions will not run. Install the .NET 10 Desktop Runtime on each device to continue using the Twingate Windows Client. Having only .NET 8 installed is not sufficient.

Q: Will Windows Client versions built on .NET 8 continue to work?

A: Existing .NET 8 versions of the Client continue to run while the .NET 8 Desktop Runtime is installed. However, they no longer receive updates, and Clients older than 12 months are not supported. Plan to move all devices to a .NET 10 version of the Client.

Q: How do I know if the .NET 10 Desktop Runtime is installed on my Windows devices?

A: Go to Settings > Apps > Installed apps (or Control Panel > Programs > Programs and Features). If Microsoft Windows Desktop Runtime - 10.0.x (x64) is listed, it is installed on the device.

You can also run the following command in PowerShell:

dotnet --list-runtimes | Select-String "Microsoft.WindowsDesktop.App 10\."

If the .NET 10 Desktop Runtime is installed, the command returns output similar to the following (your patch version may differ):

Microsoft.WindowsDesktop.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

If the command returns nothing, or PowerShell reports that dotnet is not recognized, the .NET 10 Desktop Runtime is not installed.