If you use .deb version; auto update will download .AppImage

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On every Linux system under my administration, the AppImage variant consistently fails to operate—presumably due to my rigorous security settings. In contrast, the .deb package has proven entirely reliable. While the new auto-update feature would be exceptionally convenient, it regrettably downloads the nonfunctional AppImage.

I respectfully request that the auto-update mechanism honor the currently installed package format. An additional commendation would be warranted if “sudo apt-get upgrade cursor” seamlessly updated the application.

Steps to Reproduce

install cursor via .deb
open cursor,
click the update to new version button
see it download AppImage not deb
see that the AppImage fails

Expected Behavior

download and install the deb

Operating System

Linux

Version Information

Version: 2.6.19
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Linux x64 6.14.0-37-generic

For AI issues: which model did you use?

NA

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report. This is a known issue. The update service on Linux doesn’t check what format you installed and always suggests AppImage.

Related thread with the same root cause: Linux `.deb` / `apt` installs get a non-actionable update popup before the package exists

The team is aware. For now, the workaround is to set Update: Mode to none in Settings Ctrl+, to hide the popup. You can update via sudo apt update && sudo apt upgrade cursor as usual.

Let me know if you have any questions.

7

Hey @James_Wood!

The .deb auto-update downloading .AppImage issue has been fixed in a recent Cursor update. Updating to the latest version should resolve this. If you’re still experiencing this on the latest version of Cursor, please raise a new thread and we’ll take a look.