Cursor stopped working since upgrade to Ultra plan, no response from Cursor support

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor IDE completely broken, cannot open any projects since ‘upgrading’, 5 hours of detailed digging suggests its a bug in Cursor’s WSL integration. All projects use DevContainers and WSL (half of them originally MS-WSL/MS-DevContainers, half of them originally Anysphere-WSL/Anysphere-DevContainers) - manual wipe of all extensions and reinstall of latest Anysphere extensions: no effect)

After clean wipe + install, using latest version of Windows 10, I can get the IDE to open, but it refuses to open any projects, with a missing error message (the error is “”). Googling suggests this is a know bug that Cursor has a broken error handler for issues related to WSL.

No response from Cursor support ([email protected]) for 5 days and counting.

Steps to Reproduce

Update to latest Windows 10.
Lose all access to your work.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Tried with latest version, and downgraded a couple of versions (2.3.x, 2.2.x) and wiped + reinstalled - nothing works.

Tried rolling back 3-4 versions of Anysphere-WSL and Anysphere-DevContainers - no effect.

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

My guess: it’s the latest Windows10 updates.

But it happened immediately after upgrading the account to Ultra. So I don’t know if that’s a coincidence.

Does this stop you from using Cursor

Yes - Cursor is unusable

I have another windows10 machine - NOT updated to latest windows10 updates (I’ve firewalled WindowsUpdate on this machine! In case that’s what’s causing the problem) - which is still running Cursor fine (but is on v2.2.44. The projects appear to have no problems - everything is identical at project level according to git.

The issue you’re facing with Cursor IDE not opening any projects after the upgrade on Windows is not common.

Do you know what updates are upcoming on your other windows 10 machine? it may help us narrow down the causes.

If I unblock updates to see what’s in the pipeline then I don’t believe I can prevent them from applying. Since this is the only machine I have where Cursor still runs that’s a huge risk to take.

Intense digging suggests that there’s 1 (or more) bugs in how Cursor translates paths to/from WSL and windows filesystem – the error message is empty, but google/forum searches suggest it’s trying to load docker / container files using a linux path (inside the container) but converting it to a windows path (which is stupid and by definition could never work - windows filesystem refs dont exist inside a linux container).

… but the lack of log output from Cursor makes this difficult and guesswork. I have logs leading up to the moment it fails, but they just show it’s ‘something’ around Cursor accessing the docker files. I think it can’t find them - but as noted: they are there, they have not moved or changed in any way.

Update: virgin install of windows 11, on new hard disk, virgin install of ubuntu 24.04 … virgin install of latest Cursor = BROKEN.

Cursor is unusable since the changes. Old versions worked but Anysphere have (why? to save money?) remotely blocked all the old versions. I’ll be downgrading/cancelling plan end of this month.

NOTE: reply from support was entirely usesles, essentially: our engineers are now looking at it but will give you no information, no followup, no contact, no ETA, if you’re lucky maybe one day we might fix it, go away.

1 Like