Version 0.45.14 Downgrade on Boot

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I launched Cursor about an hour ago, I got a pop-up saying it was installing version 0.45.14. It then booted this version, which appears to be a very old version of Cursor. I tried reinstalling the cursor, and also deleting all cursor files off my laptop and reinstalling from the newest release (both universal Mac and ARM64), and both encountered the same issue.

Steps to Reproduce

I reproduced by installing the newest version of Cursor on my Mac.

Expected Behavior

Shows the newest version of Cursor.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 0.45.14
VSCode Version: 1.96.2
Commit: 906121b8c0bdf041c14a15dac228e66ab5505260
Date: 2025-02-19T20:36:48.096Z (1 yr ago)
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, I can see from the screenshot that it’s version 0.45.14, which is a very old build.

Most likely, your Mac still has files from the old update system (ToDesktop) that are conflicting with the new install. When you say you “deleted all files”, the hidden folders in Library probably weren’t removed.

Try a full cleanup:

  1. Fully quit Cursor Cmd + Q

  2. Delete Cursor.app from /Applications

  3. Delete these folders (open Terminal):

    rm -rf ~/Library/Application\ Support/cursor-updater/
    rm -rf ~/Library/Caches/cursor-updater/
    rm -rf ~/Library/Application\ Support/Cursor/
    rm -rf ~/Library/Caches/Cursor/
    
  4. Download the latest DMG from Cursor · Download

If it still installs 0.45.14 after that, let me know. That would mean the issue is on our side.

Thanks for getting back to me. I had already deleted all those files (and just tried again), but unfortunately, it didn’t resolve the issue. I’m on the Ultra plan, so it’s pretty irritating that I can’t use the subscription for a few days. Let me know if there’s other information you need!

Thanks for confirming. Since clearing didn’t help, let’s dig a bit deeper. I want to figure out if the DMG itself contains an old version, or if macOS is somehow launching an older binary.

Can you run the following in Terminal?

  1. Check if there are any other Cursor installs on your system:

    mdfind "kMDItemFSName == 'Cursor.app'"
    
  2. Check the version inside the app that’s currently in /Applications:

    cat /Applications/Cursor.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString
    
  3. Download a fresh copy and check the DMG contents before installing:

    • Download from Cursor · Download (ARM64)
    • Mount the DMG, but don’t drag it into Applications yet
    • Run:
    cat /Volumes/Cursor*/Cursor.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString
    

If the DMG shows the latest version, but after installing it somehow rolls back, that points us in a different direction.

Also, if the first command returns multiple Cursor.app results, that’s probably the cause. There’s likely an old copy somewhere, and macOS keeps launching that one.

It is working again! I am unclear what changed. The results before uninstalling Cursor:

mdfind "kMDItemFSName == 'Cursor.app'"

/Applications/Cursor.app

cat /Applications/Cursor.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString

<key>CFBundleShortVersionString</key>

<string>2.6.19</string>

Then, after uninstalling:

mdfind "kMDItemFSName == 'Cursor.app'"

cat /Applications/Cursor.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString

But when I reinstalled this time, the issue was resolved.

Glad it’s working now! Based on the output, only one Cursor.app was found in /Applications, and it’s version 2.6.19, so the install looks clean.

It’s hard to say what caused the downgrade to 0.45.14 at first. My best guess is there were leftover files from the old ToDesktop updater, and they only got removed after a few cleanup and reinstall attempts. macOS can also cache app info, like Spotlight or Launch Services, which could be why the old version kept showing up.

If this happens again, run mdfind first to check for duplicate installs. For now, you should be all set.