Hello, Cursor closes a few seconds after opening on my Windows PC, preventing me from using the editor or the agent.
The issue started after an agent task involving a GitHub repository. The task finished, and then Cursor closed. Since then, it keeps closing shortly after launch.
What I have tried:
Reinstalling Cursor.
Installing the Windows x64 System version instead of the User version. The issue persists.
Launching with a separate user-data directory.
Launching with --disable-extensions.
Launching with --disable-gpu.
Launching with --classic.
After the window closes, there are no Cursor.exe processes left in Task Manager.
I checked Reliability Monitor and Windows Application events 1000/1001, but found no entries corresponding to the recent launch attempts.
Logs collected BEFORE switching to the System Installer showed the following messages. Personal file paths have been redacted:
update#ctor - updates are disabled due to running as Admin in user setup
CodeExpectedError: ENOPRO: No file system provider found for resource ‘[REDACTED]/User/globalStorage/storage.json’
The renderer log also contained several warnings:
Missing property “…” in oldValue. Filling with value from initValue.
The Chromium startup log contained:
This document requires ‘TrustedScript’ assignment. The action has been blocked.
I do not know whether these messages cause the exit or occur during shutdown.
The previous installer version was 3.24.18. I have not yet confirmed the exact build of the new System installation.
Could you help identify why the application exits and tell me which additional logs or crash dumps you need?
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Where does the bug appear (feature/product)?
Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
Describe the Bug
Cursor closes a few seconds after opening, preventing me from using the editor or the agent.
The problem started after an agent completed a task involving a GitHub repository. After the task finished, Cursor closed and has continued closing shortly after launch ever since. I cannot confirm that the task caused the issue.
I have reinstalled Cursor and switched from the Windows x64 User Installer to the System Installer, but the problem persists.
After the window disappears, no Cursor.exe processes remain in Task Manager.
Steps to Reproduce
On my affected installation:
Launch the Cursor desktop application.
Wait a few seconds.
Cursor closes without displaying an error dialog.
The issue also occurred with a separate user-data directory, without manually opening the repository.
Expected Behavior
Cursor should remain open and allow me to use the editor and agent normally.
Screenshots / Screen Recordings
No recording attached at this time. I can provide one if needed.
Operating System
Windows 10/11.
Exact Windows version and build have not yet been confirmed.
Version Information
Previous User installer version: 3.24.18.
Current System installation version: not yet verified.
VSCode version: not available.
Commit: not available.
I cannot access Menu → About Cursor because the application closes shortly after launch.
This report concerns the Cursor desktop IDE, not the standalone Cursor CLI.
For AI issues: which model did you use?
Not confirmed. The current problem occurs during application startup, before I can interact with a model.
For AI issues: add Request ID with privacy disabled
Request ID: not available.
Background Agent ID: not available.
Additional Information
Troubleshooting already attempted:
Reinstalled Cursor.
Switched from the Windows x64 User Installer to the System Installer.
Tested a separate user-data directory.
Tested with --disable-extensions.
Tested with --disable-gpu.
Tested with --classic.
The launch-flag tests were performed before switching to the System installation. The System installation also closes shortly after launch.
I checked Reliability Monitor and Windows Application events 1000/1001, but found no events matching the recent launch attempts.
Logs:
The following excerpts were collected BEFORE switching to the System Installer. Personal paths have been redacted. Logs from the new System installation have not yet been included.
main.log:
[info] [AgentHostUpdater] following channel stable (by release track stable)
[info] update#setState disabled
[info] update#ctor - updates are disabled due to running as Admin in user setup
[error] CodeExpectedError: ENOPRO: No file system provider found for resource ‘[REDACTED]/User/globalStorage/storage.json’
Stack trace, with installation paths omitted:
at nm.withProvider
at async nm.withWriteProvider
at async nm.writeFile
at async r7.doSave
Hey @Gustavo_Benatti, thanks for the detailed report and for trying all of those steps already.
The ENOPRO storage.json line is written while Cursor is shutting down, so it’s a side effect of the close rather than the cause. Cursor also doesn’t pass crashes to Windows Error Reporting, which is why Reliability Monitor and Event Viewer show nothing.
Since a reinstall and a fresh user-data directory didn’t help, the cause is most likely something outside Cursor’s install and profile folders. Could you try these in order and tell me after which step (if any) Cursor stays open:
Restart Windows (Start > Power > Restart, not Shut down). Then open Cursor normally from the Start menu, not “Run as administrator”.
If it still closes: with Cursor closed, rename the folder %USERPROFILE%\.cursor to .cursor-backup (nothing is deleted). Open Cursor again.
If it still closes: open Command Prompt and run this (adjust the path if Cursor is installed elsewhere):
“C:\Program Files\cursor\Cursor.exe” --verbose --log trace
Wait for it to close, then attach:
the text printed in the Command Prompt window
the newest main.log from %APPDATA%\Cursor\logs\ (open the most recent folder)
any files in %APPDATA%\Cursor\Crashpad\reports\
It would also help to know:
What the agent task was doing right before Cursor first closed (for example starting or stopping a server, killing processes, installing tools, or changing environment variables). Commands like these can leave something running after Cursor closes.
Your Windows version (Settings > System > About) and the Cursor version (Settings > Apps > Installed apps).