Cursor

Cursor Update Failed / Won't Update — How to Fix It

Cursor periodically prompts users to install new updates, but sometimes the update fails silently, hangs midway, or the editor continues running the old version after a restart. This issue affects Windows, macOS, and Linux users alike, often appearing after a network interruption or a permissions conflict. If Cursor shows an update available but nothing changes, the steps below will get you back on the latest release.

Why does this error happen?

Cursor's auto-updater relies on downloading a delta or full installer package in the background, then applying it on restart. The update can fail for several reasons: a partial download caused by a dropped connection, insufficient write permissions to the installation directory, a corrupted local cache that causes the updater to reference stale files, or an antivirus or firewall blocking the update payload. On Windows in particular, the updater may lack elevation privileges needed to overwrite system-level files, causing it to exit silently without completing the installation.

✓

How to fix it

Download the Latest Version Manually from cursor.sh

Visit cursor.sh and download the installer for your operating system directly. This bypasses the in-app auto-updater entirely and guarantees you get the full, uncorrupted package. Run the installer over your existing installation — it will upgrade Cursor without erasing your settings or extensions.

Uninstall and Reinstall Cursor

If the manual installer still fails or Cursor behaves unexpectedly after the update, perform a clean reinstall. Uninstall Cursor through your system's standard app manager (Add/Remove Programs on Windows, drag-to-Trash on macOS), then download and install a fresh copy from cursor.sh. Your project files are stored separately and will not be affected.

Run the Installer as Administrator on Windows

Right-click the downloaded Cursor installer (.exe) and select 'Run as administrator' before launching it. This grants the installer the elevated permissions it needs to write files to protected directories and register the application correctly. After installation completes, open Cursor normally — administrator mode is not required for everyday use.

Clear the Cursor Cache Folder

A corrupted update cache can cause repeated failures even when you try to update multiple times. On Windows, delete the contents of %APPDATA%\Cursor\Cache and %LOCALAPPDATA%\cursor-updater. On macOS, remove ~/Library/Application Support/Cursor/Cache and ~/Library/Caches/cursor-updater. Restart Cursor after clearing the cache and attempt the update again.

💡 Pro Tip

Enable automatic background downloads in Cursor's settings so updates are fully staged before you restart, reducing the chance of a partial download causing a failed update during a busy work session.

Frequently Asked Questions

Will reinstalling Cursor delete my extensions and settings?

A standard reinstall preserves your settings and extensions because they are stored in a separate user-data directory, not inside the application folder. However, if you manually delete the Cursor application support folder as part of a deep clean, you will lose those preferences and will need to reconfigure them.

Why does Cursor keep showing the same update notification after I already installed it?

This usually means the updater downloaded the package but failed to apply it, leaving the version number unchanged. Clearing the updater cache folder and reinstalling manually resolves the loop in most cases.

Can a VPN or firewall block Cursor updates?

Yes — corporate firewalls or strict VPN configurations can block the download endpoints that Cursor's updater contacts. Try disconnecting from the VPN and downloading the installer manually from cursor.sh as a reliable workaround.

How do I check which version of Cursor I am currently running?

Open Cursor, go to Help > About (Windows/Linux) or Cursor > About Cursor (macOS) to see the installed version number. Compare this against the latest release listed on cursor.sh to confirm whether your update succeeded.

✓

Quick diagnostic checklist

Before diving into the full fix, run through these quick checks — they resolve the issue in most cases without additional steps:

1.Restart the Cursor application completely

2.Check your Cursor subscription is active at cursor.com/account

3.Update Cursor to the latest version via Help → Check for Updates

4.Disable conflicting VS Code extensions

5.Re-enter your API key in Cursor Settings → Models

Common root causes

Understanding why this error occurs helps you prevent it in the future. The most frequent causes are:

Outdated Cursor version with known bugs
API key expired or quota exhausted
Conflicting VS Code extensions interfering with Cursor
Context window exceeded in large files or codebases
Network proxy or firewall blocking Cursor API calls

Still not working?

If none of the steps above resolved the issue, the next step is to contact Cursor support directly. When reaching out, include:

• The exact error message or code you see
• The steps you already tried from this guide
• Your account plan and the approximate time the error started
• Your browser/OS version if it is a web interface issue

Open Cursor Forum →

About Cursor

Cursor is an AI-powered code editor built on VS Code, developed by Anysphere Inc. It integrates GPT-4 and Claude models directly into the editor for autocomplete, code generation, and natural language chat. Cursor is popular among developers for pair programming and large codebase navigation.

Browse all Cursor error guides →

Cursor →