Cursor desktop app won't open after login

Support Bug Reports
1

I’m experiencing a problem similar to what @Lucas_Minchillo reported. My Cursor desktop app is not working at all, and I’ve already tried deleting all local data and cache related to Cursor, but the issue persists.

When I attempt to log in:

  • The web login works fine and confirms that I’m logged in.

  • However, the desktop app still does not open and continues asking me to log in.

I’ve followed all troubleshooting steps I could find, including clearing %AppData%, %LocalAppData%, the cursor-updater folder, and registry entries. Despite this, I cannot access Cursor.

This is very frustrating and blocks me from using the app. Any guidance on how to resolve this would be greatly appreciated. @condor

image
image1906×650 20.7 KB

image
image783×541 2.76 KB

2

hi @ignacioNinci thank you for the detailed report. The team is investigating similar cases.

To help us diagnose the login loop issue better, could you please provide the following:

  • Any errors or warnings from the browser console (F12 > Console tab) during approval of desktop login.
  • Your operating system and Cursor app version. (full version info)
  • Any VPN, firewall, or antivirus software that might affect network calls.
  • Have you tried logging in with different browsers? Which ones?
  • Are you using privacy mode, any special security settings, privacy extensions?
  • Exact timestamps of your login attempts to cross-check with backend logs.

This info will help us get more details and pinpoint the cause. Thanks!

5

hi @condor
I’ve checked the browser console during the desktop login approval flow and found relevant errors. Attaching a screenshot as well.

Key console messages observed:

  • “Tracking Prevention blocked access to storage”
    This appears during the login approval step, which suggests cookies or localStorage needed for the auth nonce may be blocked between cursor.com and auth domains.

  • Multiple failed requests to:
    /next/static/chunks/*.js
    returning net::ERR_ABORTED 500 (Internal Server Error)

  • “Refused to execute script because its MIME type is not executable”, likely caused by the 500 responses returning unexpected content instead of JS.

This seems consistent with the desktop login loop:

  • Web login completes successfully (“All set! Feel free to return to Cursor”)

  • Desktop briefly shows logged-in state

  • Immediately returns to Sign Up / Log In screen

I tested with:

  • Edge and Chrome

  • Normal and incognito mode

  • No VPN

  • Windows Defender only

Please let me know if you want me to provide desktop logs or test a backend/session reset.

6

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