After the last update Cursor 3.0 service reconnection error

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Error to conecting to services cursor failed on network section when i run diagnostics

Steps to Reproduce

i try write a prompt an send it and mini log say “take longer than i expected”

Expected Behavior

i think some services are down

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
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
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

All

For AI issues: add Request ID with privacy disabled

i don hava any ID because service are not responding

Additional Information

i contact Cursor Support and i try this steps and doesnt work

Try these steps in order:

  1. Reload the window:

Press Cmd+Shift+P (Mac) / Ctrl+Shift+P (Windows)
Type “Developer: Reload Window”
Select it and wait for the window to reload
2. If that doesn’t work, clear the state database:

Fully quit Cursor (make sure no processes remain)
Navigate to:
Windows: %APPDATA%\Cursor\User\globalStorage\state.vscdb
macOS: ~/Library/Application Support/Cursor/User/globalStorage/state.vscdb
Delete (or rename) the state.vscdb file
Relaunch Cursor
Note: Clearing state.vscdb will reset chat history and some session state.

  1. If the issue persists, try opening your workspace in a new window:

Close the problematic window
Open Cursor fresh
File > Open Folder and select your workspace
Let me know if any of these steps resolve it!

Best,

Sam

Cursor’s AI Support Assistant

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, I saw your diagnostic screenshots, and it’s the exact same pattern: the basic network checks (Downloads, CDN) pass, but all 4 providers fail with “Timeout waiting for EverythingProvider”. That means your network is fine, and the problem is the extension host not being able to start.

This is a known issue on Windows. Let’s go through the steps:

  1. Do you have any VPN software installed? Clash Verge, v2rayN, sing-box, or anything else.

Even if the VPN is turned off, it can still break the extension host. In most cases, that’s the root cause. If you have one, fully uninstall it (including the app’s local data), reboot your PC, and launch Cursor again.

  1. Check the cursor-socket folder

Open Command Prompt and run:

dir "%LOCALAPPDATA%\Programs\cursor\resources\app\extensions\cursor-socket\"

If you see dist\ but there’s no out\, that’s the issue. Fix it like this:

cd "%LOCALAPPDATA%\Programs\cursor\resources\app\extensions\cursor-socket"
xcopy dist out\ /E /I

Restart Cursor.

  1. Start Cursor without extensions:
cursor --disable-extensions
  1. If nothing helped, temporarily disable your antivirus or firewall and try again.

Send me the result of each step, and especially your answer to the VPN question. We’ve already fixed a similar case here: Timeout waiting for EverythingProvider

Socker Folder works for me, thanks so much