Hey, this is a known bug in 3.1.17. The April update caused an uptick in ERROR_EXTENSION_HOST_TIMEOUT, especially on Windows. A couple similar threads:
For now, as a workaround, use Reload Window when you hit the error. Use Ctrl+Shift+P then Developer: Reload Window.
If you can reproduce it reliably, please share the Request ID from the chat via the menu in the top right corner > Copy Request ID. That helps link your case to the issue.
This is happening frequently, and even after trying to reload the window, it is not working; the same issue persists. It is making the cursor unusable. Can I get a refund for my subscription for the account [email protected]?
Hey, thanks for the Request ID. This is a known bug in 3.1.17 on Windows, and we’re already tracking it. I can’t share an ETA for a fix yet.
Since Reload Window doesn’t help, try these one by one:
Full reinstall. Close Cursor, kill all Cursor.exe processes in Task Manager, uninstall the app in Apps & Features, then download the latest installer from Cursor · Download and install again. You don’t need to touch user data %APPDATA%\Cursor, your settings and account will stay. This fixed it for some users with the same issue, there was a corrupted file in the bundle.
Legacy Terminal toggle: Settings → Cursor Settings → Agents → Legacy Terminal → enable. This helped some users with the same timeout.
Roll back to 3.1.16 if nothing else works: Cursor · Download, check the older versions section. This is temporary until the patch is out.
If the bug still happens after a full reinstall, send a fresh Request ID and exthost.log at %APPDATA%\Cursor\logs\<latest session>\exthost\exthost.log and I’ll take a closer look.
About a refund, that’s handled by a separate team. Email [email protected] from the account you want the refund for and they’ll help you sort it out.
