Cursor
Overview
Version & Lifecycle
Community Notes
Cursor update and duplicate ARP entry note
For managed Cursor updates, close the desktop application before starting the installer. If the app is left running, Cursor EXE/User-x64 updates can fail with Exit Code 1 or leave the install in an untrustworthy state. Add a pre-close/check step for Cursor.exe in deployment tooling before retrying the update.
When remediating older Cursor User-x64 installs, check for duplicate Add/Remove Programs entries from versions before 0.46.0. Older auto-updates could remove Uninstall Cursor.exe from the install directory, leaving the previous ARP entry with an invalid uninstall string; clean up that stale entry before relying on current Cursor uninstall/update detection.
Use Cursor’s official download/current release source for Windows installers and verify the installed version after cleanup. Source: Cursor downloads.
Release Notes & Updates
Help us match vulnerabilities
No vulnerability match yet. Pick the right product: