Hey, this is a known Windows issue: the retrieval-always-local extension host crashes because the cursor-socket extension structure is malformed. Your screenshots match the usual pattern: exit code 18446744072635810000, failed extension verification.
Try this:
Fix cursor-socket
Open Command Prompt as admin:
cd "%LOCALAPPDATA%\Programs\cursor\resources\app\extensions\cursor-socket"
xcopy dist out\ /E /I
If Cursor is installed in C:\Program Files\cursor, use:
cd "C:\Program Files\cursor\resources\app\extensions\cursor-socket"
xcopy dist out\ /E /I
Turn off Instant Grep
Cursor Settings (not VS Code settings) > Indexing & Docs > turn off Index Repositories for Instant Grep (BETA)
Restart Cursor
This combo worked for other users with the same issue:
I see the screenshot from Developer Tools, that helps.
There are two issues here. xcopy created the out/ folder, but in Cursor v3.0.12 it checks extension integrity and rejects cursor-socket because of extra files: Extension verification failed: Extra files: out/main.js. The main crash is coming from cursor-retrieval with exit code 18446744072635810000, and that’s a separate issue.
Try this first without reinstalling:
Delete the out folder that xcopy created, it’s now causing problems. Open Command Prompt as admin:
Turn off Codebase Indexing. Cursor Settings (not VS Code settings) > Indexing & Docs > turn off Codebase Indexing. If you don’t see the toggle in the UI, open the Command Palette with Ctrl+Shift+P, then Preferences: Open User Settings (JSON) and add:
"cursor.codebaseIndexing.enabled": false
Restart Cursor.
If it still doesn’t help, do a clean reinstall. Uninstall Cursor, then delete these folders:
%LOCALAPPDATA%\Programs\cursor
%APPDATA%\Cursor
%USERPROFILE%\.cursor
Download it again from Cursor · Download. Note that this will reset settings, extensions, and chat history, so if you need it, back up %APPDATA%\Cursor and %USERPROFILE%\.cursor before deleting.
Also, do you have a VPN client installed on this machine, even if it’s not active right now? In a few cases, removing the VPN fixed the retrieval crash.