Fully quit Cursor (File > Exit — don’t just close the window).
Open Task Manager and go to the Details tab. If any Cursor.exe, node.exe, or rg.exe processes are still running, end them.
Reopen Cursor.
Run the update again.
Does the error still appear after step 4? If so, please reply with the exact error message.
The updater logs would also help a lot. In File Explorer, paste %TEMP% into the address bar and look for files named cursor-inno-updater-<numbers>.log or Setup Log <date> #<number>.txt dated when the error occurred. Attach the most recent ones here and we’ll dig in from there.
Hey @liang_ding — thanks for the logs, they pinpoint exactly what went wrong.
When you accepted the update, Cursor had already shut down, but another process on your PC was still holding a lock on the resources folder inside C:\Users\liang\AppData\Local\Programs\cursor, so the updater couldn’t move it.
To track down what’s holding that folder, could you help us with two things?
Security software: Which antivirus or security suite is installed on this PC (e.g. 360, Tencent PC Manager, Huorong, or just Windows Defender)?
Next update attempt: Before you accept it, fully quit Cursor (File > Exit), then open Task Manager > Details and check whether any node.exe, rg.exe, or cursor-*.exe processes are still running. If so, let us know their names, end those tasks, and then retry the update.
only have Windows Defender. mybe I use both VS Code and Cursor simultaneously. Could this cause a problem? This issue didn’t exist before version 3.18. I noticed the problem after the 3.18 update.
