STOP shipping updates before you update your updates!

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor on windows self-update fails >50% of the time.
When this happens, and we go to Download · Cursor - that web page only has OLD INSTALLERS - and NOT the update that was trying to be downloaded.
This is VERY ANNOYING - we end up with a broken windows setup, and no way to actually get the update…

Steps to Reproduce

Today -

  1. install the latest windows from Download · Cursor
  2. it wants to update immediately
  3. the update fails

Expected Behavior

Download · Cursor should be the FIRST place where any update gets shipped to - shipping updates first then the installers second is wasting everyone time and patience.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

CursorSetup-x64-2.0.34 (1).exe
cursor shortcut no longer works due to failed update…

Additional Information

Loads of people have update issues on windows - this at least would be a concrete step you can take to help solve some of those - ship (publish) installers for new versions BEFORE you ship auto-update versions to customers!

Does this stop you from using Cursor

Yes - Cursor is unusable

2

This is the current, as-of-now Cursor version:-

Version: 2.0.60 (system setup)
VSCode Version: 1.99.3
Commit: c6d93c13f57509f77eb65783b28e75a857b74c00
Date: 2025-11-05T00:50:54.645Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.17763

This is the current as-of-now, download for Cursor:

downloads[.]cursor[.]com /production/45fd70f3fe72037444ba35c9e51ce86a1977ac11/win32/x64/system-setup/CursorSetup-x64-2.0.34.exe

downloads[.]cursor[.]com /production/45fd70f3fe72037444ba35c9e51ce86a1977ac11/win32/x64/user-setup/CursorUserSetup-x64-2.0.34.exe

That’s a LOT of versions behind.

3

Also, so you are aware, the Linux version of cursors “Update” feature is different to windows - it DIRECTLY uses the website to download the update - so it NEVER actually gets the update, because the website is never updated to ship it…

4

Hey, thanks for the report.

To diagnose the update failure, please share:

  • Error details: the exact message shown when the update fails
  • Disk space: confirm you have enough free space (low space often breaks updates)
  • Logs: Ctrl+Shift+P “Developer: Open Logs Folder” - attach the relevant logs from the failure

Temporary workaround (Windows):

I’ll pass this to the team as a deployment/release process issue - the download page shouldn’t lag this far behind auto‑updates, since it blocks recovery from failed updates.

5

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