When trying to open cursor IDE on my laptop it causes infinite window spawn

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Devices specs: Lenovo LOQ-15 intel core i5 RTX 4050 24 GB RAM 6 GB Graphics 512 GB SSD OS: Windows 11

Clean reinstall didnt work either and only way the infinite window spawn pauses if i shut down forcefully by using power button. I really need cursor for work purpose but i dont know what to do

Steps to Reproduce

i dont know how you would recreate infinite windows

Expected Behavior

cursor ide opening

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

CURSOR IDE VERSION is 2.0.69

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report - that’s unusual behavior.

Can you access the logs? Go to %AppData%\Cursor\logs and attach the most recent log files here - they may show what’s causing the spawn loop.

I’ll also pass this to the team.

files.zip (8.6 KB)

i am uploading the files as zip there were at this path C:\Users\SENJUTI SAHA\AppData\Roaming\Cursor\logs\20250803T223910

@deanrie hii is there anything else you need for this? please let me know about it

Thanks for the logs! They show Cursor initializing successfully, which suggests the window spawning happens after startup completes. This points to a window management or graphics driver issue.

Please try these steps:

Disable GPU acceleration:
cursor --disable-gpu

Disable hardware acceleration via flag file:

  • Create a file at: %AppData%\Cursor\User\argv.json
  • Add this content:
{
    "disable-hardware-acceleration": true
}
  • Try launching Cursor normally.

Start without any workspace:

  • cursor --new-window --disable-extensions

Update GPU drivers (RTX 4050):

  • Get the latest NVIDIA drivers from nvidia.com.
    Your laptop may have older or buggy drivers causing the spawn loop.

Get fresh logs:

  • After trying the above, find the newest log files in %AppData%\Cursor\logs\ (look for today’s date, not August).
  • Share those - they should show what’s happening during the spawn loop.

Given your RTX 4050 and that the logs show normal initialization before the spawning begins, a GPU/hardware acceleration issue is the most likely cause.

oh sorry i didnt realize that it was the older logs. sorry for inconvenience caused

(i will try the hardware related steps as u said)

I attached the below folder for logs dated 12th November 2025

i can see at least 96 window folders here

files.zip (56.8 KB)

1 Like

update @deanrie now cursor is opening successfully!

updated gpu driver
disabled gpu acceleration (this step almost scared me cz the window spawn happened again)
started new workspace

now its opening
attaching the screenshot of log files after fixing for reference

Thank you very much to you and rest of the team for helping me out! keep up the good work

1 Like