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:
- 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.
- Check system proxy settings
Run this in Command Prompt:
netsh winhttp show proxy
If it shows anything other than Direct access, reset it:
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.
- Check for leftover Clash services
Run this in Command Prompt:
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.
- Check environment variables
Run:
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.
- 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?
%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.