Cursor ide update

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Bug: In-app auto-updater crashes when Node.js processes are running – no warning dialog shown

Description
The in-app auto-updater does not check for running Node.js processes before installing. It silently attempts to overwrite Node.js while it is still in use, causing a crash. Cursor then fails to reopen.

The standalone web installer handles this correctly – it detects running Node.js processes and shows a dialog asking the user to close them before proceeding. The in-app updater lacks this check entirely.

Actual Behavior
No dialog is shown. The updater silently crashes, leaving Cursor in a broken state.

Workaround
Manually download the installer from cursor.com and run it – this correctly prompts to close Node.js processes.

Reproducibility
Reproduced on last 2 consecutive updates.

Impact
High – forces manual reinstall during active work sessions, significant productivity disruption.

Steps to Reproduce

Steps to Reproduce

  1. Have any Node.js-based application running in the background (reproduced with Wispr)
  2. A Cursor update notification appears → click “Install Now”
  3. Cursor shuts down and begins the background update
  4. Installer crashes due to Node.js conflict – no warning or dialog is shown
  5. Cursor does not reopen

Expected Behavior

Expected Behavior
The in-app updater should detect running Node.js processes and show a dialog (same as the web installer does), asking the user to close them before continuing.

Operating System

Windows 10/11

Version Information

one before > CursorUserSetup-x64-3.2.11.exe

For AI issues: which model did you use?

auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. Your note about the Node.js processes (Wispr) is helpful and makes the root cause clearer.

This is a known class of bugs with the in-app updater on Windows. The background updater is launched with a flag that skips the check for running apps, so if a third-party process is holding a file lock on shared resources in the Cursor directory, the update fails halfway through. The standalone installer doesn’t do this, which is why the behavior is different.

We’re tracking this issue on our side, but we don’t have a specific ETA for a fix yet. I also shared your thread internally as an additional signal.

Your workaround is correct. Until this is fixed, for problematic updates please download the installer directly from cursor.com, or close Node apps before clicking Install Now.