In this article:

    Applicable to

    • Twingate Component: Client (version 2026.7)
    • Platform OS: Windows

    Overview

    This article addresses a known issue with the Twingate Windows Client in version 2026.7 where there may be an issue with the Client being unresponsive or unexpectedly disconnecting.

    Our engineering team is aware of the issue and is actively working on a permanent solution.

    Symptoms

    Impacted users may observe one or more of the following after a network change event including device power on, reboot, or sleep/wake.

    • User unable to login to the Client with the error Could not join network.

    • The connection toggle (slider) spins/pinwheels and then returns to OFF.

    • The Client disconnects shortly after connecting, or cannot connect at all.

    • Stopping the Twingate service via services.msc may hang in Stopping.

    • Rebooting does not always recover the client or service.

    Cause

    While the review of the issue is still underway, our current hypothesis is that the Twingate Windows Service starts before Windows has established a usable internet connection. This can happen if:

    • The device is not connected to a network immediately after sign-in (for example, the network is not set to connect automatically).

    • DHCP has not yet assigned network configuration to the interface.

    • A default route is not yet present, preventing the client from identifying a bypass interface

    With these scenarios the Client can fail to detect DNS servers from available interfaces and network initialization fails. In some cases, even after connectivity returns, the Client can still fail and become stuck, leaving no clean recovery path without forcefully terminating the Twingate Windows Service (Twingate.Service.exe).

    Workarounds

    Option 1: Downgrade the Windows Client

    Downgrading to the Twingate Windows Client 2025.338 is the most reliable way to get users unstuck quickly.

    Option 2: Ensure a Network Connects Automatically 

    Verify that impacted devices have at least one known-good network configured to connect automatically, so an internet connection is available shortly after sign-in. This reduces the likelihood that the Twingate Windows Service starts before a usable interface, DNS, and default route exist.

    • Open Settings on the Windows device.
    • Navigate to Network & Internet.
    • Choose Wi-Fi from the navigation menu.
    • Open Manage known networks to view saved wireless networks.
    • Select the network that should be used by default.
    • Confirm that Connect automatically when in range is enabled.

    Option 3: Terminate + Restart Twingate Service (Results May Vary)

    If the user is blocked and a downgrade is not immediately possible, the following may temporarily restore functionality.

    1. Quit the Twingate Client

      • System tray > Twingate > Quit

    2. Close any remaining Twingate processes

      • Task Manager > end any Twingate-related processes (Twingate.exe, Twingate.Service.exe)

    3. Attempt to restart the service

      • Open services.msc

      • Stop Twingate Service (if running)

      • Start Twingate Service

      • Relaunch the Twingate Client (GUI)

    4. Validate internet connectivity first

      • Confirm the device has an active internet connection before starting the service/client

    Important note: In some cases Windows cannot stop the Twingate service and it may remain stuck in “Stopping.” If this occurs, a reboot may be required. Some environments may require forcefully terminating the service process as an admin action.

    Further Details

    To confirm the issue beyond the stated symptoms occurring on version 2026.7, you can check the Twingate logs.

    1. Click on the Twingate Client in the system tray.
    2. Navigate to Client > More > Troubleshoot > View Logs.
    3. This will open two File Explorer windows
      1. %PROGRAMDATA%\Twingate\logs\ (C:\ProgramData\Twingate\logs)
      2. %LOCALAPPDATA%\Twingate\logs\ (C:\Users\<username>\AppData\Local\Twingate\logs)

    4. Search %PROGRAMDATA%\Twingate\logs\Twingate.Service.log for failed to initialize libhydra: code -1 following the packet manager initialization. In a bad state, we would expect this to continuously looping.

      [<date_time>] [INFO] [client] Start packet manager initialization. [<no type>.platform_module_new] 
[<date_time>] [ERROR] [libsdwan] failed to initialize libhydra: code -1 [<no type>.log]
    5. Search %LOCALAPPDATA%\Twingate\logs\system-events.log (created after clicking View Logs in the Twingate Client) for both of the below criteria, seeing if there are matching results returned.

    • Search criteria: Application: Twingate.Service.exe

      [<date_time>] [Error] .NET Runtime
Application: Twingate.Service.exe
CoreCLR Version: 8.0.2325.60607
.NET Version: 8.0.23
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
   at <Module>.PktDevice_WFPBlockTrafficOutsideTun(_PktDevice*, Boolean)
   ...

    • Search criteria: P1: Twingate.Service.exe

      [date_time>] [Information] Windows Error Reporting
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Twingate.Service.exe
P2: 2026.7.2078.0