Cursor uninstalled itself and didn’t install afterwards continued

Support Bug Reports
,
44

@Frunza_Cristian, @Carlos_skHard, @ilyes, @Schenk0, thanks for the reports. This is a known bug we’re tracking. No ETA yet, but this thread helped narrow down at least one root cause, see post #29: Cursor uninstalled itself and didn’t install afterwards continued - #29 by deanrie

The issue is that inno_updater can’t delete the resources/ folder because something is holding a file handle on it. It retries 11 times, then gives up halfway. In @mk18’s case, it was Cursor’s bundled node.exe kept alive by an agent-spawned wrangler dev. We’ve also seen it triggered by reboots while Cursor is still partially running.

Workaround until this is fixed: go to File > Preferences > Settings, search for update.mode, set it to none. You’ll need to update manually, but it should stop Cursor from disappearing.

If you want to help pin down your specific case, please share:

  • Install path: %LOCALAPPDATA%\Programs\cursor\ user or C:\Program Files\cursor\ system? If both at the same time, that’s a separate bug: Windows updater fails with dual install (system-wide + per-user) and leaks ~2GB of temp folders
  • Do you run any long-lived background processes through the Cursor agent, like pnpm dev, wrangler dev, next dev, etc.?
  • Antivirus or EDR, like Defender, Bitdefender, Sentinel, CrowdStrike, corporate?
  • Does it happen only after an update prompt, or also after plain restarts with no update involved?
  • Do you launch Cursor from WSL via cursor . or directly from Windows?

The more specific the repro steps, the better the chances of a targeted fix. I’ll post back here when there’s progress.