# WSL - connection to cursor server failed

**URL:** <https://forum.cursor.com/t/wsl-connection-to-cursor-server-failed/152258>\
**Category:** Bug Reports\
**Tags:** windows, wsl, ssh\
**Created:** [February 19, 2026, 8:35am UTC](https://forum.cursor.com/t/wsl-connection-to-cursor-server-failed/152258 "2026-02-19T08:35:40Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 19, 2026, 8:54am UTC](https://forum.cursor.com/t/wsl-connection-to-cursor-server-failed/152258/4 "2026-02-19T08:54:08Z")

</div>

Hey, thanks for the report. Error `0x8007274c` is a Windows socket timeout. The WSL process stops responding, and Cursor can’t reach its server. The Docker connection you mentioned is a good clue, since Docker Desktop and WSL together can quietly hit resource limits.

Try these steps in order:

1. In PowerShell, run `wsl --shutdown`, then reopen Cursor
2. Create or edit `C:\Users\<username>\.wslconfig` to increase resource limits:

```auto
[wsl2]
memory=8GB
processors=4

```

Then restart WSL with `wsl --shutdown`. This is especially important if you run Docker containers at the same time as Cursor.
3. Update WSL: `wsl --update`
4. Inside WSL, remove Cursor’s server files: `rm -rf ~/.cursor-server`, then reconnect from Cursor

A couple questions to narrow it down:

- Which WSL distro are you using?
- How many Docker containers are usually running when this happens?
- What does `wsl --version` show in PowerShell?

A similar issue is described here: [Cursor fails after some time when using WSL](https://forum.cursor.com/t/cursor-fails-after-some-time-when-using-wsl/151877)

Let me know if any of these steps helped.

---

_[View the full topic](https://forum.cursor.com/t/wsl-connection-to-cursor-server-failed/152258)._