Takes ages to start a new Cursor window

Support Bug Reports
, ,
1

image
image1355×302 28.4 KB

Has anybody found a solution to agents not working after Cursor restart?

I have to completely close and restart it a few times and then wait for a few minutes to be able to work. This behavior has been there for ages and it’s driving me nuts! I literally need 10-15 minutes, sometimes more to resume my work in Cursor every time the computer is restarted or I open a new Cursor window.

I am running Windows 11 on a Lenovo laptop.

Does anybody know the cure to this? I’ve spent lots of cycles researching and trying to fix this behavior (starting new profiles, disabling/uninstalling extensions, etc.). Driving me crazy already.

Network diagnostics shows this:

image
image695×582 28.6 KB

I am on a fast connection and everything seems to be reachable. No vpns/filters, etc.

The ONLY way I have found to remedy this is to completely restart Cursor (close all the windows, reopen them again - reloading a single window doesn’t work).

Anyone else facing this issue? Any remedy?

6

This is a known issue on Windows. Your network is fine — the checks that pass (DNS, SSL, etc.) confirm connectivity; the ones that fail all depend on the extension host.

A few things to try:

  1. Make sure you’re on the latest version. Download from cursor.com/download. Some improvements to extension host startup have been made in recent releases.

  2. Check the cursor-socket folder. Open Command Prompt and run:

    dir "C:\Program Files\cursor\resources\app\extensions\cursor-socket\"

    If you see dist\ but no out\, copy it:

    cd "C:\Program Files\cursor\resources\app\extensions\cursor-socket"
xcopy dist out\ /E /I

    Then restart Cursor.

  3. Try an isolated extensions directory to rule out corrupted extension state:

    cursor --disable-extensions --extensions-dir C:\cursor-clean-ext

    If this works, the issue is in your existing extensions/workspace storage.

  4. Check Windows Defender or any security software. Even without a VPN, Windows Defender’s real-time protection can sometimes interfere. Try temporarily disabling it, then launching Cursor. If that fixes it, add an exclusion for C:\Program Files\cursor\ and the cursor.exe / cursor-socket processes.

  5. Clear workspace storage for the affected project. Back up first — this will remove chat history for that workspace:

    %APPDATA%\Cursor\User\workspaceStorage\

    Find the folder for the problematic project (check workspace.json inside each folder), delete it, and reopen.

There’s an existing thread tracking this issue with more details: Timeout waiting for EverythingProvider Error

If none of the above helps, could you share the logs from your latest session? Open %APPDATA%\Cursor\logs\, find the newest folder, and share the main.log and any exthost files. That’ll help us pinpoint where the startup hangs.