Signature check failures in the Windows in-app updater

• Status: Open. Staff are tracking it, with no timeline as of 7:30 PM ET on Oct 8. No release note mentions a fix.
• First seen: Sep 4, according to the first forum report, posted Sep 10.
• Symptoms: The Windows in-app updater downloads a new version, then says the downloaded update could not be verified and doesn't install it. The app stays on the old build.
• Workaround: Download Setup.exe from cursor.com/download/bot and run it.

On Windows, Grok Bot's in-app updater can download a new installer and then refuse to install it. Reports cover several versions, including 0.36.0, 0.44.0, and 0.61.0.

Colin, a Cursor community support engineer, said on Oct 8 that the installer is fine and that the failure is in the app's own check right after the download. "This is a known issue we're tracking," he wrote, with no timeline.

Why it matters#

Stuck on an old build, you miss fixes. The help center says Grok Bot shows Update required once your version is more than 14 days old and a newer one is out.

How to use it#

Staff gave this workaround, first on Sep 11 and again on Oct 8.

1. Go to cursor.com/download/bot and download Setup.exe.
2. Run it to install the new version over the old one.
3. If the app shows the full-window Update required screen, its Download the latest version link gets you the same installer.

Good to know#

• The Agent Computer doesn't need a reset for this. It only affects the desktop app.
• The installer.exe under %LOCALAPPDATA%\sand-updater is the last installer you ran, not the one the failed update downloaded.
• Staff said the error message doesn't yet record why the check failed, and that recording the reason is part of what the team is looking at.
• What to watch: a release note that mentions the Windows updater. Until one appears, keep using Setup.exe.