Cursor Frequently Stuck on 'Taking Longer Than Expected' After Every Reboot

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am experiencing a persistent issue with Cursor where Composer frequently gets stuck on “Taking longer than expected…” and never produces a response.

Here are the details:

Environment:

  • Cursor Version: 3.7.36
  • Windows 11 Version 25H2 (OS Build 26200.8457)
  • Pro Plan
  • UT Austin managed laptop
  • No VPN in use

Issue Description:

  • The problem occurs across multiple models and projects.
  • Creating a new chat does not help.
  • Re-indexing and deleting indexes do not help.
  • Restarting Cursor does not help.
  • After approximately 5–10 retries, Composer occasionally starts working—very stressful…
  • Once it starts working, it usually remains stable until the next system reboot.
  • After rebooting Windows, the issue returns and the cycle repeats.

I tried to solve this problem by myself, spending a lot of times, talked to ChatGPT and found relevant log messages including:

[auth] Timeout waiting for auth ready signal
[composer] Extension host became UNRESPONSIVE
The local extension host did not send its ready message within 60s

I have attached the relevant logs and would appreciate any guidance on whether this may be related to Cursor itself, authentication, extension host initialization, or a known compatibility issue with managed Windows environments.

Steps to Reproduce

I can not understand this section

Screenshots / Screen Recordings

Taking longer than expected.png
Taking longer than expected.png477×297 5.97 KB

Operating System

Windows 10/11

Version Information

Version: 3.7.36 (user setup)
VS Code Extension API: 1.105.1
Commit: 776d1f9d76df50a4e0aeca61819a88e7c1b861e0
Date: 2026-06-13T00:31:56.287Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Composer 2.5 Standard seems unusually slow tonight.

6

Hey, thanks for the detailed report and logs, that really helps. In your case, Taking longer than expected is not a server error. It means the response has not started coming in yet. The logs Timeout waiting for auth ready signal, Extension host became UNRESPONSIVE, and did not send its ready message within 60s point to the extension host not finishing startup in time. On managed or corporate Windows this is almost always AV or EDR like Defender real time protection scanning or slowing down Cursor processes on a cold start. That matches the after every reboot pattern. After a few retries the files get cached and it starts working.

What to try, in order:

  1. Instead of a full restart, use Developer: Reload Window Ctrl+Shift+P then type Reload Window. This usually recovers right away.
  2. Since this is an IT managed laptop at UT Austin, ask them to add AV or EDR exclusions for the Cursor install folder, %APPDATA%\Cursor, and %USERPROFILE%\.cursor. This is the real fix for corporate Windows.
  3. If that does not help, try a clean extensions folder by launching cursor --extensions-dir C:\cursor-extensions.

This is known behavior and others have the same signature. Main thread for context: Extension Host fails to initialize (Timeout waiting for auth and plugins), breaking AI Agents and Source Control

One more thing. Your account currently shows as Free, even though you mentioned Pro Plan. It does not affect this bug, but double check you are logged into Cursor with the right email.

Let me know if the AV exclusions help. That usually fixes it on managed Windows.

8

Thanks a lot!! I will follow your guidance :slight_smile: