URGENT - WSL keeps disconnecting

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

During extended operations, WSL needs to reconnect and then fails, requiring a window reload.

Window reload usually fails, requiring a full restart.

Steps to Reproduce

Run Cursor for an extended period of time (Win 11 + WSL)

Operating System

Windows 10/11

Version Information

Version: 2.6.20 (user setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Early Access
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.26200Version: 2.6.20 (user setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Early Access
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

4

Hey, this is a known issue with WSL resource limits during long sessions. By default, WSL caps memory at 50% of your host RAM, often around 4 GB. During heavy use, Cursor’s server process inside WSL can run out of resources, which causes the disconnect.

Here’s what should help:

  1. Create or edit %USERPROFILE%\.wslconfig with these settings:
[wsl2]
memory=8GB
processors=4
  1. Then run in PowerShell:
wsl --shutdown
wsl --update
  1. Reopen your project in Cursor.

A user with the same issue confirmed Cursor fails after some time when using WSL that increasing WSL memory to 8 GB significantly reduced the disconnects.

It’s also worth checking htop inside WSL to see if CPU or memory is maxing out right before the disconnect. That can confirm if resource limits are the root cause.

Let me know if this helps, or if the disconnects continue after the config change.