Hey, this is a known issue. On some corporate Windows machines, the extension host cursor-socket fails to initialize. That causes everything routed through it, Auth UI, Cursor Tab, Agent, Indexing, to fail with the error “Timeout waiting for EverythingProvider.” Your network is fine. The basic checks, DNS, SSL, Marketplace, Authentication, all pass. The problem is client-side.
The team is aware and tracking this. A few things to try:
- Check the cursor-socket folder
Open Command Prompt Run as Admin and run:
dir "C:\Program Files\cursor\resources\app\extensions\cursor-socket\"
If you see dist\ but no out\, that’s a known trigger. Fix it:
cd "C:\Program Files\cursor\resources\app\extensions\cursor-socket"
xcopy dist out\ /E /I
Restart Cursor.
- Try a custom extensions directory
Launch Cursor with an isolated extensions folder to rule out corruption:
cursor --extensions-dir C:\cursor-extensions
- Check AV or EDR software
This is the most likely culprit in corporate environments. Enterprise security tools, endpoint protection, EDR agents, application whitelisting, can block cursor-socket from starting. Can you share:
- What antivirus or endpoint protection is installed on these machines?
- Is there any application whitelisting or DLP software running?
- Check if your AV logs show any blocks related to files under
C:\Program Files\cursor\resources\app\extensions\cursor-socket\
If your security team can whitelist the entire Cursor installation directory C:\Program Files\cursor\, that often resolves it.
- Turn off Codebase Indexing
Cursor Settings (not VS Code settings) > Indexing & Docs > turn off Codebase Indexing. Reload the window via Ctrl+Shift+P then run Developer: Reload Window.
Similar thread with the same error for reference: Timeout waiting for EverythingProvider
Send the output from step 1 and info about your security software. That’ll help narrow it down.