Hey, thanks for the detailed report. The main suspect here is the third-party script fix_cursor_storage_B.ps1. It cut state.vscdb from about 7 GB to about 1.1 GB, and that very likely broke the extension host state. Restoring only state.vscdb from a backup doesn’t roll everything back. There’s related data in globalStorage and workspaceStorage that the script could’ve touched too. The timing with “Activating Extensions” fits that.
What to try, in order:
-
Clean reinstall, not Reload:
- Close Cursor.
- Back up and delete
%APPDATA%\Cursorand%USERPROFILE%\.cursor. - Uninstall Cursor via Add/Remove Programs.
- Download a fresh installer from Cursor · Download and reinstall.
- Sign in, open the project, and test drag-and-drop before installing any extensions.
-
If everything works on a clean profile, add extensions one by one to find the trigger. Office Viewer is already suspicious, even if you disabled it.
-
If it still doesn’t work on a clean profile, please share:
- A short video showing the repro drag works, then “Activating Extensions”, then drag breaks.
- A log from
%APPDATA%\Cursor\logs\the newest folder, especiallyrenderer.logandexthost.log, captured right after the failed drop.
There’s also a closed Windows thread with the same symptom, but without cleanup scripts: Regression: Drag-and-drop from Cursor Explorer to Chat/Composer stopped working (Windows)
One more thing. I wouldn’t recommend community scripts that modify state.vscdb directly. It’s a closed SQLite format with links between tables, and trimming by size can easily break integrity. If you need to clean up, it’s safer to do it via Cursor Settings or a full reinstall.
Let me know how it goes after the clean reinstall.