Recent update:
- Froze every time I opened it
- I restarted my PC twice, reinstalled 2.4, still broken
- Rolled back to 2.3
- All chats are now corrupted
…
1 Like
Hi there!
We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.
To help us investigate and fix this faster, could you edit your original post to include the details from the template below?
Bug Report Template - Click to expand
Where does the bug appear (feature/product)?
- Cursor IDE
- Cursor CLI
- Background Agent (GitHub, Slack, Web, Linear)
- BugBot
- Somewhere else…
Describe the Bug
A clear and concise description of what the bug is.
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
- …
- …
- …
Expected Behavior
What is meant to happen here that isn’t working correctly?
Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)
Operating System
- Windows 10/11
- MacOS
- Linux
Version Information
- For Cursor IDE: Menu → About Cursor → Copy
- For Cursor CLI: Run
agent aboutin your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......
CLI:
CLI Version 2026.01.17-d239e66
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!
Hey, thanks for the report. Both issues are known bugs related to the 2.4.x updates.
About the freeze on startup
Usually, reinstalling from the official website helps. Someone with the same issue resolved it this way: Cursor stuck at start up.
About the “corrupted” chats
I need to clarify what exactly is happening with the chats:
- Are they visible in the list but won’t open when clicked?
- Or have they completely disappeared from the list?
Most likely, the data isn’t lost, the DB just can’t read it after the rollback. Here’s what you should try:
- Close Cursor completely (check Task Manager).
- Open
%APPDATA%\Cursor\User\globalStorage. - Are there any files like
state.vscdb.corrupted.1767...?
If there are, a full recovery guide is here: Tutorial: How to Fix "Loading Chat" and Recover History (Cursor v2.3.x).
If there are no such files, please send a screenshot of the contents of globalStorage, and we’ll help you recover it another way.
Important for the future: This issue usually occurs when there’s little disk space during the update, and the DB migration doesn’t complete. Make sure there’s enough free space before the next updates.
Have the same issue after the last update ((((
This makes me wonder - does Cursor have QA at all?
hi @bladerunner2020 we do have QA, and test always Cursor also ourselves on various platforms as well as releasing it in Nightly (alpha) & Early Access (beta) channels before sending to Default channel. That does not mean that some issues may not occur.
To which issue do you refer to specifically?
Note that chats were migrated from DB to files in ~/.cursor/projects/<projectname>/<chathash>.txt and can be referenced now as files in 2.4 under @Past Chats feature.
Here I am referring to this issue, but my frustration stems from Cursor’s overall decline in stability. Each update introduces new bugs, and critical ones like the file deletion bug (I and other users are reported) are simply unacceptable.
Extend your release cycles. Currently, it feels like we’re paying to be your beta testers.
2 Likes
@bladerunner2020 could you post a full separate Bug Report with more info Create Bug Report
It is not common that Cursor freezes and we would like to track down the cause so we can fix it. Not as part of this thread as OP has yet to provide additional info about their case.
The reason we are doing frequent updates are performance and stability improvements. Yours may still be a case we need to fix but that requires more info.
Maybe others see these improvements, but unfortunately I’m seeing just the opposite.
2 Likes
I agree thats why a bug report would be important. If we can’t reproduce it its hard to fix it.
You agree…. (sad)
Cursor QA: Powered By Cursor
*Verified by the verifier it verifies
*
But also, lots of new features intermingled therein. Perhaps the cadence of new features could be slowed so that stability improvements take center stage.
2 Likes