Cursor is completely broken after the update

[Tom_Coustols]

Hey @toddnagel , this looks like a known post-update WSL regression, not removed support. Can you share the exact error and Remote-WSL output? In the meantime,
try:
remove ~/.cursor-server
in WSL, and also
wsl --shutdown

Ensure only anysphere.remote-wsl is enabled (not Microsoft’s), and if needed roll the WSL extension to v0.08 then back. If still broken, downgrading Cursor to 3.3 temporarily is a workaround others used.

You can check those 2 other thread with the same underlying issue :

New update results in WSL breaking

Hey, this is a known issue with WSL in the latest versions. The logs show two things: a missing code.sh launcher file and unknown quality: when installing cursor-server. Both can block the connection. Try this workaround that helped other users: Open Cursor locally, not in WSL Go to Extensions and find the WSL extension Switch it to version v0.08 via Install Another Version… Restart Cursor Then update the WSL extension back to the latest version Restart Cursor and try connecting to WSL again …

Can't connect to WSL anymore

Hi @thibauld, Thanks for the incredibly detailed writeup and for sharing the fix. Your debugging session with the logs is spot on. This confirms what @pluma also found above – the root cause is having two WSL remote extensions installed simultaneously. Cursor ships its own (anysphere.remote-wsl), and if the older Microsoft one (ms-vscode-remote.remote-wsl) is also present, they conflict during initialization, which is what causes the “Opening remote…” hang. For anyone else hitting this, the f…