Hey, thanks for the detailed report. The paths and steps are clear. This is a known Windows auto-updater bug: during the update, the installer renames the install directory, and if the install phase doesn’t finish cleanly, the main Cursor.exe ends up in a folder with the _ suffix, while shortcuts and registry entries still point to the old path. We’re tracking this issue, but I can’t share an exact fix timeline yet.
What you can do right now:
Quick fix, like you found: copy T:\Program Files\cursor\_\Cursor.exe back to T:\Program Files\cursor\Cursor.exe, and your shortcuts should work again.
To prevent it from happening again: turn off auto-update and update manually. In settings Ctrl+,, find update.mode and set it to none. You can install new versions by downloading the installer from Cursor · Download.
If the bug comes back after a manual reinstall, let me know and we’ll dig in more.
Any update to share here? The bug has been around for months, i’ve seen many reports submitted here. Quite frustrating to need to re-install cursor each time an update is applied.
Like Henry, this didn’t happen in older versions, can’t give you a build number but I’m sure you can find that internally. Fixing the update issue would make our lives so much easier. Thanks in advance.
Hey, thanks for the ping. This is the same issue described earlier in the thread. During auto-update, the installer renames the install directory, and if the install phase doesn’t finish cleanly, the main Cursor.exe stays in the folder with the _ suffix, while shortcuts and the registry still point to the old path. We’re tracking it, but I can’t share an exact ETA for a fix yet.
What you can do right now so you don’t have to reinstall every time:
Quick recovery: copy Cursor.exe from the folder with the _ suffix back to the original install path. Your shortcuts should work again.
To prevent it from happening again: disable auto-update and update manually. In settings Ctrl+,, find update.mode and set it to none. You can install new versions manually from Cursor · Download.
If the issue comes back after a manual reinstall, reply here and we’ll dig deeper. I’ll post an update in the thread when I have one.
I’m aware of the bug and the various workarounds I can do. I was asking if there is an update on when you’ll be resolving the bug. Having to manually update or move things around when an update breaks gets real old real quick.
Hey @Mike_Nowakowski, got it, you don’t need a workaround, you need a clear timeline. Honestly, I can’t give an exact ETA. The issue is on our radar and we’re actively tracking it, but I won’t promise a date since that wouldn’t be fair to you or the team.
I know reinstalling or moving files by hand after every update is really exhausting, especially when it’s been going on for months. Until a fix is shipped, the only way to avoid hitting this again is to turn off auto-update by setting update.mode: none in settings Ctrl+,, and then update manually from Cursor · Download.
As soon as I have a status update, I’ll reply here in this thread.
