Hey, thanks for the report. This is a known issue. The extension host crashes on Windows, and that can trigger the Agent Execution Timed Out error. Since it started right after a Windows update, that matches what we’ve been seeing.
Let’s try a few things in order:
-
Disable Codebase Indexing:
Cursor Settings (not VS Code settings) > Indexing & Docs > turn off Codebase Indexing. If you also see Index Repositories for Instant Grep (BETA), turn that off too. Restart Cursor. -
Try a temporary profile:
cursor --profile-temp
This starts Cursor with a completely clean state. If it works, the issue is in your profile or state data.
- Check cursor-socket:
Open Command Prompt and run:
dir "%LOCALAPPDATA%\Programs\cursor\resources\app\extensions\cursor-socket\"
We’ve seen cases where the out/ folder is missing inside cursor-socket, and that makes the extension host crash right away.
- Check for VPN software:
Another user with the exact same issue found that uninstalling VPN software fixed it, even if it wasn’t running. If you have any VPNs installed, try removing them temporarily.
Extension host terminated unexpectedly no matter what i try
Also, since this started after a Windows update, a fully clean reinstall might help:
- Uninstall Cursor
- Delete
%APPDATA%\Cursorand%LOCALAPPDATA%\Programs\cursor - Reinstall from Cursor · Download
The team is aware of extension host crash issues on Windows. Your report helps with prioritization.
Let me know which step helped, or if none of them did.