In this article:
- Twingate Component: Twingate Client (Windows)
In the context menu of the Twingate Client, there are two options to end the program but they function in a very different way.
The difference in behaviour is due to the Start Before Logon support within Twingate. If the application were to disconnect on quit/system restart, we would be unable to facilitate authenticating against a Twingate resource (such as an AD server) because there would be no active Twingate network. As such, the Twingate Windows Service remains online unless it is logged.
In the screenshot below:
1. Log out & Disconnect will close the Twingate application but in addition, it will also disconnect the Twingate Client. This options should be used at all times if you plan to connect to a different network.
2. Quit will close the application without disconnecting the Twingate Client connection in the process. This option should only be used if are disconnected from Twingate and looking to exit the Twingate Client UI.
Note: Choosing Quit instead of Log out & Disconnect may cause issues with connectivity if you change networks, the remedy in this case would be starting the client and then selecting Log out & Disconnect before reconnecting.