Cursor stops working properly only after it is launched from WSL command line with "cursor ."

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Network diagnostics fail only after running cursor . from WSL command line.

Steps to Reproduce

Quite simply:

I install CursorUserSetup-x64-3.7.21 on my Windows device (OS Name: Microsoft Windows 11 Enterprise, OS Version: 10.0.26200 N/A Build 26200) in the normal way.

If I launch Cursor from Windows, everything appears to work and I can pass all network diagnostics when I run it inside the settings of the Cursor interface.

Now, I want to work on a project by entering “cursor .” to the command line inside the relevant project in WSL.

The following message is returned and an update installed:

Installing Cursor Server for commit 517f696d8ab6c53eb04fbfdaae705cd146bf3460
Cleaning up old installations…
Downloading Cursor Server for x64 (517f696d8ab6c53eb04fbfdaae705cd146bf3460)
–2026-06-10 14:30:26-- [REMOVED HTTPS]downloads(DOT)cursor(DOT)com/production/517f696d8ab6c53eb04fbfdaae705cd146bf346e/linux/x64/cursor-reh-linux-x64.tar.gz
Resolving downloads(DOT)cursor(DOT)com (downloads(DOT)cursor(DOT)com)… 104.18.16.128, 104.18.17.128, 2606:4700::6812:1180, …
Connecting to downloads(DOT)cursor(DOT)com (downloads(DOT)cursor(DOT)com)|104.18.16.128|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 108584338 (104M) [application/gzip]
Saving to: ‘/home/(MY USER)/.cursor-server/bin/517f696d8ab6c53eb04fbfdaae705cd146bf3460-1781094626242492322.tar.gz’

Now if I let this run, Cursor is broken. Network diagnostics fails. Some diagnostics show a red cross with “Timeout waiting for EverythingProvider”. Others just hang forever. (screenshot attached)

I cannot communicate with agents as this just times out with an error.

Expected Behavior

Cursor should pass network diagnostics even when launched from wsl command line.

Screenshots / Screen Recordings

cursorbug.png
cursorbug.png673×713 49 KB

Operating System

Windows 10/11

Version Information

Version: 3.7.21 (user setup)
VS Code Extension API: 1.105.1
Commit: 517f696d8ab6c53eb04fbfdaae705cd146bf3460
Date: 2026-06-07T21:46:09.237Z
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

Additional Information

I can work around this by never using “cursor .” in WSL and just opening from Windows every time. If I let the update run that occurs when I use “cursor .”, Cursor becomes broken even if I launch it from Windows.

Furthermore, after Cursor breaks from using “cursor .”, a recurring request to install the WSL extension appears which always returns no matter how many times I click it and restart.

Finally, it’s worth noting that I have to rm -rf the /.cursor-server and anything else Cursor related before doing a clean install to make the work around work. If you just uninstall cursor and reinstall in the regular way, the bug persists even after the reinstall.

Sorry for messing with the URLs but it’s preventing me from posting this for too many urls. This is just a bit silly.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey @alecstibo

Thanks for the report! I thought I reproduced it, but I’m not so sure.

On my end: I ran cursor . on the root WSL directory and it was super slow with the same symptoms you’re describing (network diagnostics hanging, “Timeout waiting for EverythingProvider,” agents timing out).

Then I ran cursor . in a small folder and it was basically instant and everything passed.

What folder are you running it in? Is it the root, or a subfolder?

7

Hi Colin,

I was just running it in the subfolders where my various projects live. Hope this helps.