Connection to Cursor server failed: [wsl exec: installServerScript] Command failed with exit code 4294967295: stdout: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error code: Wsl/Service/0x8007274c
Steps to Reproduce
open Cursor IDE, wait.
Operating System
Windows 10/11
Version Information
2.5.17 (user setup)
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
This seems to be related to running docker containers.
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:
In PowerShell, run wsl --shutdown, then reopen Cursor
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.
Update WSL: wsl --update
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?