Can no longer connect to WSL 2.0

Discussion
1

I have been using Cursor and VS Code within WSL 2.0 for a while, ubuntu. On last restart, suddenly Cursor cannot connect to the distro. Don’t think there was a windows update at the same time.

WSL Daemon exited with code 0 Check WSL terminal for more details.
logs
[2024-08-02 12:41:12.804] Extension version: 0.81.8
[2024-08-02 12:41:12.804] L10N bundle: undefined
[2024-08-02 12:41:12.824] authorityHierarchy: wsl+Ubuntu-22.04
[2024-08-02 12:41:12.824] WSL extension activating for a local WSL instance
[2024-08-02 12:41:12.843] Resolving wsl+Ubuntu-22.04, resolveAttempt: 1
[2024-08-02 12:41:12.844] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --status
[2024-08-02 12:41:12.923] WSL feature installed: true (wsl --status)
[2024-08-02 12:41:12.924] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --list --verbose
[2024-08-02 12:41:12.991] 3 distros found
[2024-08-02 12:41:12.992] Starting VS Code Server inside WSL (wsl2)
[2024-08-02 12:41:12.992] Windows build: 22631. Multi distro support: available. WSL path support: enabled
[2024-08-02 12:41:12.992] Scriptless setup: false
[2024-08-02 12:41:12.993] No shell environment set or found for current distro.
[2024-08-02 12:41:13.137] For help with startup problems, go to Visual Studio Code Remote Development Troubleshooting Tips and Tricks

I tried forcing Fix WSL.
I checked that WSL is latest.
I ran the script that is on these boards and just got alot of errors.
I tried reinstalling Cursor
I tried removing .vscode server and .cursor server to reinstall

so far nothing has worked
VS Code still opens enviorments fine. Any suggestions?

2 Likes
3

I’m uncertain if they’ll respond. Six weeks ago, I opened an issue on GitHub that’s been ignored. No one from the team has addressed this month-old problem, which arose with update 0.35.1.

You can view the issue here: Cursor is not starting in WSL · Issue #1508 · getcursor/cursor · GitHub

Hopefully, reposting the issue here will prompt some action.

4

I ended up doing full OS wipe - been a while anyways. Latest version of cursor works. Something with cache or update chain broke. Fresh os worked. Not a great solution but worked.

5

Uninstalling Cursor completely solved this problem for me.
I completely erased everything, including the Cursor folder in AppData and the .cursor in the user folder.

2 Likes
6

Same here today. I removed the .cursor folder from my windows user directory and reinstalled the WSL extension and it worked again.

4 Likes
7

this works for me, In extensions, search for Wsl and uninstall it

2 Likes
8

This worked for me. I tried new WSL distribution but it didn’t help. Uninstalling cursor and wiping every folder helped me. Thank you!