Connection to Cursor server failed: [wsl exec: installServerScript]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since today 4/4/2026 i update to last version, curson have being unusable they keep returning error and error this is the error that im getting

Connection to Cursor server failed: [wsl exec: installServerScript] Command failed with exit code 4294967295: stdout: Catastrophic failure Error code: Wsl/Service/E_UNEXPECTED

im currently using wsl i had this issue in the past and i just shutdown the wsl, but this time not matter what i do the error keep pumping, restarted, shutdown wsl, nothing work.

Steps to Reproduce

just doing nothing the error pop up

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.12 (user setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

Looks like this is just for go repos

Hey, thanks for the report. I can see the screenshot with the error. The Wsl/Service/E_UNEXPECTED error usually means the WSL service itself can’t start properly. That’s on the Windows side, not Cursor.

Try these in order:

  1. In PowerShell run wsl --shutdown, then reopen Cursor
  2. Update WSL: wsl --update
  3. Inside WSL delete Cursor server files rm -rf ~/.cursor-server, then reconnect
  4. If that doesn’t help, reinstall the WSL extension in Cursor. First close the remote connection with Ctrl+Shift+P then Remote: Close Remote Connection. Open a local project, find the WSL extension, uninstall it, restart Cursor, then reinstall it when prompted.

More context here: Cursor WSL error: Failed to patch code.sh launcher

Also, you said it’s “just for go repos”. Can you clarify? Do other projects work fine through WSL? If yes, it might be something specific to the Go workspace, not a general WSL issue.

A couple questions to help diagnose:

  • Which WSL distro are you using?
  • What does wsl --version show in PowerShell?

Let me know how it goes.