WSL - connection to cursor server failed

Support Bug Reports
, ,
4

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:
    [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

Let me know if any of these steps helped.

2 Likes