# Inconsistent update process for Cursor IDE Windows

**URL:** <https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624>\
**Category:** Bug Reports\
**Tags:** installation, windows\
**Created:** [October 2, 2026, 7:30pm UTC](https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624 "2026-10-02T19:30:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![master3395](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/master3395/32/46687_2.png) [@master3395](https://forum.cursor.com/u/master3395)\
**Post date:** [October 2, 2026, 7:30pm UTC](https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624/1 "2026-10-02T19:30:57Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

When i try to update the cursor using the “Restart to update” from “Help”, it simply refuses to update, because it’s running several node.js Javascript Runtime, that i have to manually rightclick and close, before cursor wants to restart and update.

“C:\Users\USER\AppData\Local\Programs\cursor\resources\app\resources\helpers”

### Steps to Reproduce

1. Click Help.
2. Click “Restart to update”
3. Open task manager.
4. Close all node.js Javascript Runtime
5. Cursor restarts and installs.

### Expected Behavior

Clicking restart to update should force-close all related services, so the user doesn’t have to close anything.

### Screenshots / Screen Recordings

 ![Skjermbilde 2026-10-02 212130.png](https://us1.discourse-cdn.com/cursor1/original/3X/1/b/1bb29c4a74571c0e51a0615e48c3bedee3032648.png)

### Operating System

Windows 10/11

### Version Information

Version: 3.23.5 (user setup)  
VS Code Extension API: 1.128.0  
Commit: a34aa15953a79dfe2ada63f5460efa79005dfbb0  
Date: 2026-09-29T21:43:27.519Z  
Layout: IDE  
Build Type: Stable  
Release Track: Nightly  
Electron: 42.10.0  
Chromium: 148.0.7778.280  
Node.js: 24.18.1  
V8: 14.8.178.38-electron.0  
xterm.js: 6.1.0-beta.291  
OS: Windows\_NT x64 10.0.26200

### For AI issues: which model did you use?

Auto

### For AI issues: add Request ID with privacy disabled

9315206d-961b-44d1-b2c5-ea7385156a54

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 5, 2026, 9:37am UTC](https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624/12 "2026-10-05T09:37:40Z")

</div>

Hey @master3395, thanks for the report!

This is a known issue on Windows that we’re tracking. Some MCP servers run on the Node runtime that ships with Cursor, and they can keep running after Cursor closes. Because they run from Cursor’s install folder, the updater can’t replace those files until they’re gone.

Until it’s fixed, if Restart to Update gets stuck, you can run this in PowerShell instead of closing them one by one in Task Manager:

```auto
Get-Process node -ErrorAction SilentlyContinue | Where-Object { $_.Path -like "*\Programs\cursor\resources\app\resources\helpers\*" } | Stop-Process -Force

```

It only stops Cursor’s bundled Node, not any Node.js you installed yourself.

To help us confirm which server is staying behind, next time it happens could you run this first (before the cleanup) and paste the output here?

```auto
Get-CimInstance Win32_Process -Filter "Name='node.exe'" | Select-Object ProcessId, ParentProcessId, CommandLine | Format-List

```

If any of the command lines contain an API key or token, please blank it out before posting.

---

<div class="post-metadata">

**Author:** ![master3395](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/master3395/32/46687_2.png) [@master3395](https://forum.cursor.com/u/master3395)\
**Post date:** [October 5, 2026, 9:51am UTC](https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624/13 "2026-10-05T09:51:24Z")

</div>

I will try on the next update 🙂

---

<div class="post-metadata">

**Author:** ![master3395](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/master3395/32/46687_2.png) [@master3395](https://forum.cursor.com/u/master3395)\
**Post date:** [October 7, 2026, 8:38am UTC](https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624/14 "2026-10-07T08:38:29Z")

</div>

It looks like extensions might be parts of the problem.

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/a/d/adbdbb9564c2c1803620d36505c9cdecfdc4211c.png)

PS C:\WINDOWS\system32\> Get-CimInstance Win32\_Process -Filter “Name=‘node.exe’” | Select-Object ProcessId, ParentProcessId, CommandLine | Format-List

ProcessId : 33636  
ParentProcessId : 33868  
CommandLine : “D:\Program Files\nodejs\node.exe” “C:\Users\NAME\AppData\Roaming\npm\node\_modules\npm\bin\npx-cli  
.js” “-y” “mongodb-mcp-server@\<3”

ProcessId : 32204  
ParentProcessId : 14748  
CommandLine : “node” “C:\Users\NAME\AppData\Local\npm-cache\_npx\364f1bc81b0e7c67\node\_modules.bin\..\mongodb-  
mcp-server\dist\esm\index.js”

ProcessId : 30068  
ParentProcessId : 38292  
CommandLine : “D:\Program Files\nodejs\node.exe” “C:\Users\NAME\AppData\Roaming\npm\node\_modules\npm\bin\npx-cli  
.js” “-y” “mongodb-mcp-server@\<3”

ProcessId : 3516  
ParentProcessId : 34860  
CommandLine : “node” “C:\Users\NAME\AppData\Local\npm-cache\_npx\364f1bc81b0e7c67\node\_modules.bin\..\mongodb-  
mcp-server\dist\esm\index.js”

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 7, 2026, 12:34pm UTC](https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624/18 "2026-10-07T12:34:12Z")

</div>

Hey @master3395, thanks for running that, it pinpoints the cause!

All four of those processes are the MongoDB MCP server that comes with the MongoDB plugin in Cursor (two copies, each with a small npx launcher). They keep running after Cursor closes, and that’s what blocks the updater from cleaning up the old install folder (the “Deleting a directory … os error 5” message). Your other MCP servers and your VS Code extensions aren’t involved.

I’ve passed these details to the team working on it.

Until it’s fixed, run this in PowerShell before clicking Restart to Update (or when you see that error, then click Retry):

```auto
Get-CimInstance Win32_Process -Filter "Name='node.exe'" | Where-Object { $_.CommandLine -like "*mongodb-mcp-server*" } | ForEach-Object { Stop-Process -Id $_.ProcessId -Force }

```

It only stops the MongoDB MCP processes, and Cursor starts a fresh one the next time it opens.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [October 28, 2026, 8:37pm UTC](https://forum.cursor.com/t/inconsistent-update-process-for-cursor-ide-windows/173624/20 "2026-10-28T20:37:51Z")

</div>

Closed on October 28, 2026, 8:37pm UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
