Cursor 3.17.8 becomes unresponsive immediately after launch on Windows 11

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Problem:
Cursor becomes unresponsive immediately after launching. No action is required to trigger the issue.

Environment:

Cursor: 3.17.8 (User Setup)
OS: Windows 11 x64, Version 10.0.26200
Build Type: Stable
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
Layout: IDE
Release Track: Default

Steps to reproduce:

Launch Cursor.
The application becomes unresponsive immediately.
Windows displays “The window is not responding.”
No interaction or additional action is required.

Expected behavior:
Cursor should launch normally and remain responsive.

Actual behavior:
Cursor freezes immediately after launch and cannot be interacted with.

Additional information:
Because Cursor becomes unresponsive immediately after launch, I cannot access Developer Tools or obtain console errors.

Steps to Reproduce

  1. Launch Cursor 3.17.8 on Windows 11.
  2. Wait for the application window to open.
  3. Immediately after launch, Cursor becomes unresponsive.
  4. Windows displays the message: “The window is not responding.”
  5. No additional action is required to trigger the issue.

Expected Behavior

Cursor should launch normally and remain responsive, allowing me to interact with the editor and use its features.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Environment:

Cursor: 3.17.8 (User Setup)
OS: Windows 11 x64, Version 10.0.26200
Build Type: Stable
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
Layout: IDE
Release Track: Default

For AI issues: which model did you use?

cursor grok 4.6

For AI issues: add Request ID with privacy disabled

Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1

Does this stop you from using Cursor

No - Cursor works, but with this issue

Exact same behavior here on CachyOS (Arch-based Linux) !!! This needs to be fixed ASAP… I cannot work because of this issue …

Hi @Hussien_Alajouz @PerkyZZ Thanks for the posts. Although the visible symptom is similar, Windows and CachyOS may have different causes.

@Hussien_Alajouz, could you confirm:

  1. Does Cursor eventually recover if you select Keep Waiting, or must you force-close it?
  2. From PowerShell, does either cursor -n or cursor --disable-extensions open normally?
  3. If Cursor becomes responsive, please run Developer: Open Logs Folder from the Command Palette and attach the latest logs.

@PerkyZZ, please share your exact Cursor version and installation method. Please make sure you use official AppImage from Cursor · Download . A previous CachyOS report traced similar behavior to the AUR launcher using an incompatible system Electron version. If the official AppImage also freezes, please run cursor --verbose --enable-logging=stderr and share the terminal output.

the cursor not recover when clicking keep waiting it forces me to close it also if i run it using PowerShell moreover if i use developer tools i cant see any logs just one think i can do it is to force close.