Network issues (Prompts & Marketplace failing) after forced update to latest version - DNS/SSL check hangs

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi everyone,

I’m facing a major network issue with Cursor that started today, right after the app forced an uninstallation of my previous (older) version to compel an update to the latest one. Everything was working perfectly fine yesterday on the older build.

The Symptoms:

Prompts: Sending prompts does not work (stuck/fails). 

Marketplace: The extensions marketplace fails to load/connect. 

Network Diagnostics: When running the built-in network diagnostics in Cursor, it completely hangs on the DNS and SSL checks. (See attached screenshot)

What I have already tried (none of these helped):

DNS Change: Changed my system DNS to Google's 8.8.8.8 / 8.8.4.4.

HTTP Compatibility Mode: Toggled Cursor's network settings from HTTP/2 to HTTP/1.1 and HTTP/1.0.

App Cache/Data: Completely deleted the Cursor folder from AppData (Roaming/Local) to get a clean slate.

System Components: Installed the latest Microsoft Visual C++ Redistributable directly from the Microsoft website.

Since the issue started strictly after the forced update, it feels like the new version introduces a regression in how Cursor handles network requests, SSL handshakes, or handles local certificates/proxies on Windows.

Is anyone else experiencing this, or does the dev team have a workaround? I am currently completely blocked from using the app.

Thanks in advance for any help!

Steps to Reproduce

Send prompt

Screenshots / Screen Recordings

321.png
321.png785×801 22.1 KB

Operating System

Windows 10/11

Version Information

Version: 3.5.33 (user setup)
VSCode Version: 1.105.1
Commit: aac81804b986d739acab348ed96b8bea6e83cc50
Date: 2026-05-22T06:47:48.039Z
Layout: glass
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

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, I can see from the screenshot that Network Diagnostics gets stuck on DNS or SSL and shows Timeout waiting for EverythingProvider for several services.

One quick note. The Network Diagnostics UI itself has a known bug where DNS and TLS checks can spin forever with no timeout, so a stuck spinner alone does not prove your network is broken. This issue is being tracked, there is no ETA for a fix yet.

Now the main point. Timeout waiting for EverythingProvider usually means the Extension Host or cursor-socket did not start. From the symptoms, it looks similar to this thread Timeout waiting for EverythingProvider Error. The comments there include a few fixes you can try.

What to try in your case on Windows after a forced reinstall:

  1. Full reboot of the machine. After reinstall, stale DNS or old network state from the previous process often remains.
  2. Check Windows Firewall and your AV. Rules may have reset during reinstall and Cursor might be blocked. Temporarily disable AV and test.
  3. Disable HTTP/2. Open Settings with Ctrl+Shift+, then search for HTTP/2 and enable Disable HTTP/2. Or add "cursor.general.disableHttp2": true to settings.json.
  4. DevTools. Help > Toggle Developer Tools > Console tab. Try sending a prompt, then paste the red errors from there. They will show whether the request is failing on network, SSL, or not even being sent.

If none of that helps, please share a Request ID from any failed prompt attempt Cursor Settings > top-right of the chat > Copy Request ID.