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.
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:
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):
