After updating to the latest version, the IDE keeps losing connection with WSL

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

“After updating to the latest version, the IDE keeps losing connection with WSL, and the model cannot connect to read files.”

WSL ubuntu 24.04 ,last version with wsl --update , kernel 6

Steps to Reproduce

After a moment when start cursor IDE

Expected Behavior

WSL must persistance connection, and terminal must be reponse with command

Screenshots / Screen Recordings

Screenshot 2026-06-12 192545.png
Screenshot 2026-06-12 192545.png1896×884 24.6 KB

Operating System

Windows 10/11

Version Information

Version: 3.7.27 (user setup)
VS Code Extension API: 1.105.1
Commit: e48ee6102a199492b0c9964699bf011886708ba0
Date: 2026-06-10T01:46:16.942Z
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
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

All model

Does this stop you from using Cursor

Yes - Cursor is unusable

5

cursor
cursor772×444 10 KB

7

Hi! This is a known issue on Windows + WSL — after recent updates, the agent can lose its connection to the WSL side, and when that happens file reads, search, and the terminal all stop responding at once (which matches your screenshots). It’s not something on your end, and it only affects WSL/remote setups, not native Windows.

A few things that have helped others, in order:

  1. Reload the window — Ctrl+Shift+P → Developer: Reload Window.
  2. If that doesn’t stick, run wsl --shutdown in PowerShell, then reopen your project with cursor ..
  3. Still failing? Delete the ~/.cursor-server folder inside WSL and reconnect - Cursor reinstalls the server automatically (this just re-downloads it; your code and settings aren’t affected).

We’re actively working on a fix but don’t have an ETA to share yet. The best place to follow updates (and add your setup as a data point) is the main thread here: Execution backend unavailable.