> For the complete documentation index, see [llms.txt](https://docs.defguard.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.defguard.net/support-1/troubleshooting-guides/desktop-client/windows-client-unable-to-connect.md).

# Windows client unable to connect

If the Windows client shows command timeout errors or fails to establish a connection, check the background service logs first. Open **Settings** in the client and review the log output, or locate the [Desktop Client](/using-defguard-for-end-users/desktop-client.md#log-files) directly.

### Stale WireGuard tunnel

If the background service logs contain errors like `Unable to access interface: No such file or directory`, a previous tunnel was not shut down cleanly. This leaves a ghost tunnel entry that blocks new connections.

To fix it:

1. Open the Windows **Services** manager (`services.msc`).
2. Look for any services named **WireGuard Tunnel**.
3. Stop and delete any such services.
4. Retry the connection in Defguard.

<figure><img src="/files/ykX1inFcQsfS8qbex6Eg" alt=""><figcaption></figcaption></figure>