Hey, this is a known issue with extension host initialization on Windows. The team is aware, but there’s no ETA yet.
Try this:
-
Check the cursor-socket folder. Open PowerShell as admin and run:
dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"If you see a
dist\folder but noout\, create a symlink:cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket" New-Item -ItemType SymbolicLink -Name "out" -Target "dist"Restart Cursor. This workaround helped another user with the exact same error earlier today, thread here: Agent Execution Time Out
-
If that didn’t help, clear the cache. Fully close Cursor, then delete:
%APPDATA%\Cursor\CachedData%APPDATA%\Cursor\Cache%APPDATA%\Cursor\GPUCache
Launch Cursor again.
-
Last resort, rename
%APPDATA%\CursortoCursor_backupand start Cursor with a clean config.
Let me know what worked, or what didn’t.