Cursor not starting anymore after reinstalled

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor uninstalled itself after windows update did a auto reboot.
Reinstalled cursor, when launching i get an error.
The window terminated unexpectedly ( reason crashed, code -2147483645

Steps to Reproduce

No idea, Cursor does not work at all. Crash is persistent even after uninstalling/installing before
Deleted %AppData%\Cursor\Cache and %AppData%\Cursor\GPUCache before installing

Expected Behavior

Cursor needs to start

Screenshots / Screen Recordings

Screenshot 2026-06-01 043625.png
Screenshot 2026-06-01 043625.png960×564 10.4 KB

Operating System

Windows 10/11

Version Information

Latest version

Does this stop you from using Cursor

Yes - Cursor is unusable

6

The crash code you’re seeing (-2147483645 / STATUS_BREAKPOINT) is a Chromium sandbox issue that commonly shows up after a Windows Update changes GPU drivers or security settings. It’s not specific to Cursor - it affects the underlying Electron framework.

Here’s what to try, in order:

  1. Update your GPU drivers (NVIDIA, AMD, or Intel - whichever you have) to the latest version directly from the manufacturer’s site. Windows Update often installs a version that conflicts with the Chromium sandbox. This has resolved the issue for other users with the same crash code.

  2. Clear the full app data, not just the cache. Delete these folders entirely, then relaunch:

    • %APPDATA%\Cursor

    • %LOCALAPPDATA%\Cursor

    Important: this will remove your local chat history and settings. If you want to preserve them, back up the folders first.

  3. Check antivirus / security software. CrowdStrike, Bitdefender, Webroot, and similar tools sometimes start blocking the Chromium sandbox after system updates. Temporarily disable real-time protection and try launching. If that fixes it, add Cursor to your exclusions list.

  4. Workaround if nothing else works: Create a shortcut to Cursor and add --disable-chromium-sandbox to the Target field. This bypasses the sandbox entirely and is safe for normal use.

Regarding Cursor disappearing after the Windows Update reboot - that’s a known issue we’re actively working on. The auto-updater can partially run during shutdown, and if the system powers off before it finishes, Cursor gets removed. A fix is in progress but it’s a complex one.

Let me know which step resolves it for you!