WSL extension not recognized after Cursor 3.0.12 update

Support Bug Reports
7

@justinjtownsend, fair point. If rm -rf ~/.cursor-server only helps sometimes, it’s probably not just server cache. It’s more likely a conflict between WSL client extensions.

Try this option too. It worked for a few users in a nearby thread: Cursor 3: Extension 'WSL' is required to open the remote window - #31 by kyle-514

  1. Fully close Cursor and check Task Manager to make sure no Cursor processes are running.
  2. Run cursor --classic from a Windows terminal.
  3. If you get a prompt to remove ms-vscode-remote.remote-wsl Microsoft’s WSL extension, accept it and click Uninstall & Restart Cursor. In Cursor 3 you should only have anysphere.remote-wsl.
  4. After restart, open your WSL project. It should connect reliably.

If it still hangs on Opening Remote, please send:

  • Output of wsl -l -v and wsl --version
  • Logs in Cursor: F1 → WSL: Show Log or Output → Remote - WSL. Screenshot or text is fine
  • What you see exactly: an empty editor with Opening Remote, an extension popup, or an error

With that, I can file a separate bug for your specific case Editor Window, 3.1.15, intermittent hangs. It’s different from the Agents Window issue that was fixed in 3.1.10.