# Timeout waiting for EverythingProvider Error

**URL:** <https://forum.cursor.com/t/timeout-waiting-for-everythingprovider-error/158146>\
**Category:** Bug Reports\
**Tags:** crashes, installation, windows, teams-enterprise\
**Created:** [April 16, 2026, 7:20am UTC](https://forum.cursor.com/t/timeout-waiting-for-everythingprovider-error/158146 "2026-04-16T07:20:01Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 17, 2026, 5:56am UTC](https://forum.cursor.com/t/timeout-waiting-for-everythingprovider-error/158146/21 "2026-04-17T05:56:58Z")

</div>

I see you reinstalled Clash Verge again with the Delete application data option checked, but the issue is back. The normal uninstaller often leaves system-level leftovers that can still mess with Cursor.

Try cleaning these up manually:

1. Check for leftover TUN or TAP adapters

Open Device Manager \> Network adapters. Look for anything named Wintun Userspace Tunnel or Clash, or any unknown virtual adapter. Right-click and uninstall each one. If you see a prompt, also check Delete the driver software.

1. Check system proxy settings

Run this in Command Prompt:

```bat
netsh winhttp show proxy

```

If it shows anything other than Direct access, reset it:

```bat
netsh winhttp reset proxy

```

Also check Windows Settings \> Network & Internet \> Proxy. Make sure Automatically detect settings and Use a proxy server are off, or set back to defaults.

1. Check for leftover Clash services

Run this in Command Prompt:

```bat
sc query type= service state= all | findstr /i "clash"
sc query type= service state= all | findstr /i "wintun"

```

If anything shows up, paste the output here.

1. Check environment variables

Run:

```bat
echo %HTTP_PROXY%
echo %HTTPS_PROXY%
echo %ALL_PROXY%

```

If any of these return a value, Clash Verge left proxy environment variables behind. Clear them in System Properties \> Environment Variables.

1. Reboot after all cleanup, then try Cursor again.

Also, since 360 Terminal Security is still running on this machine, it could be a combined issue. Last time removing Clash Verge alone fixed it, but now with 360 still active, it might be blocking the cursor-socket process.

Can you also share the extension host logs?

```auto
%APPDATA%\Cursor\logs\

```

Open the latest session folder and look for files named `exthost` or `extension-host`. This will help us see where cursor-socket is getting stuck.

The team knows about this issue in corporate Windows setups. Your report helps us prioritize it.

---

_[View the full topic](https://forum.cursor.com/t/timeout-waiting-for-everythingprovider-error/158146)._
