I’m using Cursor with Windows and WSL. It was working just fine a few days ago… But now it just doesn’t work, whenever I try to connect to the Remote server or try opening cursor directly from the Powershell terminal while using WSL, it doesn’t work.
I get Connection to Cursor server failed: spawn EPERM.
I tried “Reinstall server” and it also does not work, the error just keep repeating.
I’ve tried uninstalling and installing Cursor again, no success. WSL + VS Code is working just fine with Remote, but not Cursor.
Steps to Reproduce
Run WSL, try to open any directory inside of the ubuntu instance through Cursor.
Hi @p-arth, could you share the full logs from the “Remote - WSL” output window? From the error message it sounds like this is a permissions issue where we are unable to call “wsl.exe” to spawn a subprocess.
I just found out the issue. Since the last update, for some reason now Windows Defender is flagging the WSL Remote connection through cursor specifically (it works with VS Code) as something unsafe, I guess? If I deactivate the live-protection from Windows Defender, it works.
This just happens with Cursor, I can remote connect to WSL by any other means, but not with Cursor.
You guys should really look into that to fix it, pretty weird that I need to make my system “unsafe” to be able to use such a simple feature that was working before.
Could you share more about what windows defender found / why live scan blocked it? Definitely, we’ll see if there’s anything we can do to prevent this from happening.
