Cursor couldn't finish installing the update to version 3.7.21

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When i update though in add restart ti update, ’ using a manullay downloaded app image when i installed it for the first time.

Steps to Reproduce

Help> check for updates > restart to update

Expected Behavior

on Restart to update it shoudl update the cursor version to latest

Operating System

Linux

Version Information

Version: 3.6.31
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z (1 wk ago)
Layout: editor
Build Type: Stable
Release Track: Default

Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Linux x64 6.17.0-35-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, this is a known issue with the in-app updater for Linux AppImage. When it tries to update, it can’t apply the new build correctly and rolls back, so you stay on 3.6.31.

For now, the workaround is to update manually:

  • Download the latest AppImage from Cursor · Download
  • Replace your current Cursor.AppImage file with it where you originally installed it
  • Relaunch Cursor

We’ve logged the bug, but I can’t share a fix timeline yet. I’ll post an update in the thread as soon as I have one. Let me know if the manual update doesn’t work.

Thank you

Can you confirm, previously i did install through app image but now if is use the debian package then will my chats be lost or should i go with app image only

Hey, your chats won’t be lost. Your history, settings, and sessions are stored separately from the app itself in ~/.config/Cursor. The install method AppImage or .deb doesn’t affect it, so when you switch to the Debian package everything should stay in place. Just don’t delete that folder.

Switching to .deb also helps avoid the AppImage update issue mentioned above. Updates are installed via sudo apt update && sudo apt upgrade, and there’s no signed to unsigned problem there.

One more thing. To be safe, you can back up ~/.config/Cursor before switching, just for peace of mind.

Let me know if anything doesn’t carry over after the switch.