Hey Todd. Sorry you had to go through that. Spending 5 hours talking to AI and still not getting a fix really sucks, especially when you need to work. I’m @deanrie from the Cursor team, let’s look at what actually happened.
What the AI told you, reach out to the team, wasn’t wrong. I’m that team. We just handle most support through the forum rather than private ticketing for individual Pro users. That’s not an excuse for a slow reply, just context.
On the actual issue. Nobody disabled WSL for you. This is a known regression after a Windows update. In your second thread 161472 Cursor is completely broken after update you can see the root cause:
Failed to patch code.sh launcher: ENOENT: no such file or directory,
open 'd:\Development\cursor\resources\app\bin\code'
This means the Windows updater didn’t finish writing the launcher file during the reinstall phase, so the WSL resolver has nothing to patch. We’re tracking the issue, but I can’t share an ETA for a fix yet.
What you can do right now. This workaround from @Tom_Coustols Lousy customer support - #4 by Tom_Coustols is confirmed by other threads:
- In WSL:
rm -rf ~/.cursor-server - In PowerShell:
wsl --shutdown - Make sure only
anysphere.remote-wslis enabled, not Microsoft Remote-WSL - If that didn’t help, do a full reinstall of Cursor to the default path
%LOCALAPPDATA%\Programs\cursor, notd:\Development\cursor\. A non-standard install path is very likely what breaks the updater for you. - Alternative. Roll back to the previous stable build. Links to older versions are in thread 153737 Can't connect to WSL anymore
Try these steps and reply here with where it fails and the new error text if it still shows up. Then we can debug it more directly. I’m going to close thread 161472 as a duplicate so the full history stays in one place, is that ok?