Cursor fails to update beyond 1.6.45 on macos

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor continually prompts with the “update available” pop-up and when “update now” is clicked, the pop-up disappears, cursor quits, and neither updates nor re-starts. Starting cursor by hand results in version 1.6.45 running.

Using the “check for updates” menu item results in the menu item becoming “restart to update”. restarting to update fails to update and the re-started cursor application is again 1.6.45

Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Steps to Reproduce

Install 1.6.45 on a mac. try to update

Expected Behavior

cursor would update when it says it is updating

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. It’s likely an error occurs during the update, causing the process to fail. Please try downloading the latest version from the website. The next update may succeed after a clean install.

yes of course an error occurs during the update. we know this because an error occurs during the update. this wasn’t a request for advice or assistance. this is a bug report. that is why i chose the “bug reports” flair to attach to this message rather than “how to”. and obviously i know how to install cursor from the website because i had to install it in the first place.

the reason for this report is that an error is occurring when attempting to upgrade from 1.6.45 in some cases. like all bug reports, it is submitted under the assumption that the developers would prefer their product to not have a bug. i would be happy to help narrow down what the failure cases are if you have any specific requests for additional information which would be useful.

Yes, unfortunately this is a known issue where version 1.6 can’t update. We fixed it in version 1.7, so we recommend downloading that version from the website.

please verify your information before replying. no, this bug was not fixed in 1.7. see, for example, this bug report:

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