Cursor Taking time to full boot

Support Help
,
1

I’m using the windows 10 Home, Cursor Latest version I don’t know when i open the cursor it takes a lot of time to boot up, terminals doesn’t open properly and extensions also take time why this issue is there and how to solve this problem!

5

Hey, the symptoms slow boot, terminals not opening, and extensions lagging on Windows look like a known issue with the extension host. To confirm and suggest next steps, I need a bit more info:

  1. Your exact Cursor version: Help > About I need the number like 3.1.x.
  2. Start Cursor with extensions disabled and check if there’s any difference. In Command Prompt run cursor --disable-extensions. If it starts fast and terminals work, the issue is on the extension host side.
  3. If it doesn’t go away, open Ctrl+Shift+P > Developer: Open Process Explorer after launch and see which process is stuck, especially extensionHost and ptyHost. Send a screenshot here.

As a temporary workaround, Ctrl+Shift+P > Reload Window sometimes unsticks the extension host without a full Cursor restart.

Let me know what you see with --disable-extensions and what version you’re on.

6

Version:

image
image364×330 5.94 KB

Processes:

image
image1366×673 34.9 KB

although via --disable-extensions load the cursor fast but the thing is extensions are important to me without extensions my experience is not getting good.

7

image
image219×252 8.59 KB

I’m using these extensions only so on disable i don’t know how i can activate them

9

Thanks for the screenshots, it’s clearer now. A few things that might be slowing down startup:

  1. The MCP server starts via npx -y on every launch. In Process Explorer you can see the chain cmd.exe -> conhost -> node (npx-cli.js) -> cmd -> brave-search-mcp-server. npx re-checks and re-resolves the package each time, plus you get a bunch of wrapper processes. Install the package globally and set a direct path to the binary in your MCP config instead of npx -y:
npm install -g @brave/brave-search-mcp-server

Then in mcp.json replace npx -y @brave/brave-search-mcp-server with brave-search-mcp-server or the full path. This should remove a few seconds of cold start.

  1. You have a large laravel.log open, that window is using 596 MB. Big logs are better viewed via tail in a terminal or an external viewer. In the editor they trigger tokenization and syntax highlighting overhead.

  2. You have multiple Cursor windows open at the same time. Each window starts its own extensionHost, so you get 4 processes instead of 1. If you don’t need multiple windows, close the extras.

  3. Remote-SSH and WSL extensions only matter when you actually connect to remote or WSL. If you’re only opening local folders on Windows, you don’t need them and can disable them with right click then Disable. That won’t uninstall them, you can re-enable later when needed.

Try item 1 first, the MCP change is most likely the main source of the startup slowdown. Let me know if it helps.