It's not working in window

Hi, there Cursor Editor won’t open. Nothing appears on the screen when I try to run it. I’ve already tried reinstalling the editor, but it didn’t fix the problem.

This is what it looks like after launch, as shown in the screenshot.

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 about in 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. This looks like a known issue with GPU rendering on Windows.

Try this workaround:

Option 1 (recommended, permanent fix):

  1. Create this file: %AppData%\Cursor\User\argv.json
  2. Add this:
{
    "use-angle": "gl"
}
  1. Restart Cursor normally

Option 2 (quick test):
Run this in Command Prompt:

"C:\Program Files\Cursor\Cursor.exe" --disable-gpu

If option 2 helps, option 1 should give better performance.

Also worth trying:

  • Update your GPU drivers (Nvidia, AMD, Intel) to the latest version
  • If it still doesn’t help, try deleting %AppData%\Cursor completely and reinstalling (if you already removed it this way, you don’t need to)

Similar threads with the same bug:

Let me know if it doesn’t help.

Thank you for your help.

Checking option 2 didn’t resolve the issue, so I tried the following:

  1. Updated NVIDIA graphics drivers

  2. Reinstalled Cursor

  3. Downgraded the Cursor version

However, the same issue persists despite these attempts.

The screenshot below shows the result of running the command.

I see the standard options didn’t help. Let’s try a deeper cleanup.

Option 1: Clear workspace storage (make a backup first)

  1. Fully close Cursor
  2. Go to %AppData%\Cursor\User\workspaceStorage\
  3. Delete everything inside that folder
  4. Restart Cursor

Option 2: Full config wipe (you’ll lose settings and chat history)

  1. Close Cursor
  2. Delete the whole %AppData%\Cursor folder
  3. Delete %LocalAppData%\cursor-updater
  4. Reinstall Cursor

Option 3: If you haven’t tried Option 1 (argv.json) yet
From your post, it looks like you tried Option 2 (--disable-gpu). Have you tried Option 1 with argv.json? If not:

  1. Create %AppData%\Cursor\User\argv.json
  2. Add:
{
    "disable-hardware-acceleration": true
}
  1. Restart Cursor

Need a bit more info to keep debugging

  • What exact Cursor version are you on? (from About, or the installer filename)
  • What’s your exact GPU model? (for example, NVIDIA GTX 1650, RTX 3060)

Let me know what you get.

Thanks for your help!

It’s resolved now. I deleted all the existing cached data before doing a fresh reinstall, and it’s working perfectly.

I verified it after clearing out everything in the path below. Hope this helps anyone else facing the same issue!

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.