Version 0.45.11, Cannot connect to WSL

[yanlinlin82]

I am using Cursor on Win11/WSL2. After I upgrade Cursor to latest version (0.45.11) today, the WSL extension (ms-vscode-remote.remote-wsl,
0.81.8) cannot work anymore.

Click ‘Ctrl’+‘Shift’+‘P’, run ‘WSL: Connect to WSL’, it prompted the error of “command ‘remote-wsl.connect’ not found” as picture attached.

Version: 0.45.11
VSCode Version: 1.96.2
Commit: f5f18731406b73244e0558ee7716d77c8096d150
Date: 2025-02-07T09:43:58.555Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

[SoMaCoSF (SoMaCo)]

@yanlinlin82

command ‘remote-wsl.connect’ not found

I wonder how the extension is invoking

WSL vscode command returning error "not found"

– the extension is checking path and its not getting it…

[deanrie]

Hey try this:

Command 'remote-wsl.connect' not found

I got it to work by running cursor from WSL by running the command /mnt/c/Users/<windows username here>/AppData/Local/Programs/cursor/resources/app/bin/cursor /path/to/workspace/directory. This triggered the WSL server install, but on first load it complained that the WSL filesystem backend wasn’t present. I then hit ctrl-shift-p and ran the Extensions: Install Extensions command and saw that some extensions were requiring a window reload. Once I did that it seemed to be working. Note that you …

[yanlinlin82]

I have tried this but it does not fix the problem.

Before running command (in WSL) ‘/mnt/c/Users/■■■/AppData/Local/Programs/cursor/resources/app/bin/cursor /path/to/work-dir’, the command ‘which cursor’ returns ‘/mnt/c/Users/■■■/AppData/Local/Programs/cursor/resources/app/bin/cursor’.

After running above command, it downloads and installing VS Code Server for x64 in ‘~/.cursor-server/bin/f5f18731406b73244e0558ee7716d77c8096d150/’, which caused another error:

$ cursor .
node:internal/modules/cjs/loader:1228
  throw err;
  ^

Error: Cannot find module '/home/■■■/.cursor-server/bin/f5f18731406b73244e0558ee7716d77c8096d150/out/server-cli.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Module._load (node:internal/modules/cjs/loader:1051:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:173:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v20.18.1

[yanlinlin82]

I have solved this problem by following steps:

1. Uninstall cursor and reinstall it (as latest version).
2. Uninstall WSL extension.
3. Start cursor in WSL bash terminal (by running ‘cursor’ command).
4. Follow the prompt to install WSL extension in this cursor instance.

Now the ‘WSL: Connect to WSL’ command works.

[markuseicher]

Hi there. Thanks for your post and trying to help. I did what you proposed, but I still get the following error in the console:

[2025-02-12 11:27:12.565] Extension version: 0.88.5
[2025-02-12 11:27:12.566] L10N bundle: none
[2025-02-12 11:27:12.567] WSL extension is supported only in Microsoft versions of VS Code

Any tips? I am going crazy because I can’t use WSL in Cursor yet. Appreciate any help.

[yanlinlin82]

It seems that you are running VS code of Linux version. Have you installed vscode in WSL2? If yes, maybe you need to uninstall it first. After install VS code/cursor in Windows, it should find the windows version app in WSL2. Please try ‘which code’ or ‘which cursor’, this should be located at path like ‘/mnt/c/User/■■■/app/bin/cursor’.

[markuseicher]

Many thanks. After uninstalling Cursor and deleting .cursor and cursor folders from %appdata% and %userprofile% and then reinstalling it seems to work now. I have the following output when using which cursor

/mnt/c/Users/marku/AppData/Local/Programs/cursor/resources/app/bin/cursor

Thanks.

[SoMaCoSF (SoMaCo)]

This is an off the cuff reply and I have no idea what Im talking about:

File path following by whatever backend processs is hitting internal limits…

Shorten ALL filePaths?

(I say this because Cursor has bitched abt file path lengths a LOT)