When I open Cursor since a few updates ago, the source control section shows “No source control providers registered”, there is nothing in extensions, the output tab has no dropdown for me to check outputs, the terminal tab does not load the terminal. It seems as though nothing initialises.
I have to restart Cursor a few times and after perhaps 4 or 5 times it loads properly.
I have tried deleting my cache, I have updated a few times since this started happening and I have launched cursor with --disable-extensions but the issue is still there.
Hey, this is a known issue. The Extension Host sometimes can’t finish initializing on startup, so the built-in Git extension doesn’t come up and the SCM panel shows “No source control providers registered”. At the same time, extensions, the terminal, and output can break. We’re tracking it internally, but there’s no ETA for a fix yet.
A workaround that helps most users is to delete the workspaceStorage folder (Cursor will regenerate it automatically). On Windows, the path is: %APPDATA%\Cursor\User\workspaceStorage.
To add your case to the report, please send logs:
Ctrl+Shift+P > Developer: Open Logs Folder
Zip the folder and attach it here. We need the Window, Main, and Extension Host sections
Important: grab the logs before you delete workspaceStorage or restart a few times, otherwise the most useful parts may get overwritten
Also, please confirm if you’re on Windows 10 or 11 since you mentioned both in the report.
Thanks, I got the Windows 10 logs and confirmation. The logs show the usual pattern: the extension hosts start and immediately exit, and near the end it gets stuck on No search provider registered for scheme: file, waiting. That’s what breaks SCM, Terminal, extensions, and Output.
We’re tracking the issue, but I can’t share an ETA for a fix yet. Once there’s an update, I’ll reply in the thread.
For now, as a temporary workaround, I still recommend deleting %APPDATA%\Cursor\User\workspaceStorage (Cursor will recreate it). Please make a backup first. This fixes the symptoms for most users who hit the same pattern. If it still doesn’t initialize on the first try after that, let me know.
Hey @francis-ohara, it’s the same symptom as on Windows. The Extension Host doesn’t have time to initialize, so SCM, terminal, extensions, and output crash. We’re tracking the issue, but there’s no ETA for a fix yet.
The workaround that helped on Windows should also help on Mac. Close Cursor and delete this folder first make a backup:
Is there no ETA on a fix for this? I’m a bit surprised that a tech company is taking months to resolve an issue on a product that results in some users being unable to use the app without a workaround (which they will only know about by searching or raising a bug ticket, and isn’t ideal anyway as it clears the workspace history).
Hey, I get the frustration. Bugs like this at startup really get in the way, and it sucks to rely on a workaround.
I can’t give an ETA, but one important thing. You’re still on 3.1.17 from April 19. Since then, there have been a few releases, and some Extension Host initialization improvements are already shipped in newer builds. So the first and most helpful step is to update to the latest version via Help > Check for Updates, or reinstall from Cursor · Download.
If the issue still happens after updating, please grab fresh logs and I’ll add them to the report:
Ctrl+Shift+P > Developer: Open Logs Folder
Zip the folder and attach it here. We need the Window, Main, and Extension Host sections
Make sure to collect the logs before deleting workspaceStorage and before doing a bunch of restarts, otherwise the most useful info gets overwritten
Thanks for the update, at the time of making the post I was on that version but i’ve been updating regularly. Today it was still happening on version 3.7.27. I’ve just updated again and it did open without an issue on restart, but i’ll post a reply if it happens again.
Thanks for getting back to me. The fact that it launched on the first try after the update is a good sign. The newer builds include a few improvements to Extension Host initialization.
Since you’re already on the latest 3.7.27, the older logs and notes are from a much older version. So if the bug happens again, fresh logs from the current version will help a lot. Next time it fails to launch, before deleting workspaceStorage and before doing a bunch of restarts, please collect:
Ctrl+Shift+P > Developer: Open Logs Folder
Zip that folder and attach it here. We need the Window, Main, and Extension Host sections
It’s important to grab the logs before the workaround, otherwise the most useful parts get overwritten. The workaround of deleting %APPDATA%\Cursor\User\workspaceStorage with a backup is still OK as a temporary measure. Let me know if it happens again and we’ll dig into the fresh logs.