# 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>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.defguard.net/support-1/troubleshooting-guides/desktop-client/windows-client-unable-to-connect.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.