Cursor Startup Error on Windows 11

[mcdaqc]

When running Cursor on Windows 11 with a project stored in the Linux environment (WSL), an issue occurs during system shutdown. The workflow involves using Docker Compose inside WSL while storing Docker data on the Windows host machine.

Steps to Reproduce

1. Open Cursor within a project located in WSL.
2. Build or run the project using Docker Compose inside WSL, with Docker stored on the Windows host.
3. Close everything and attempt to shut down the system.
4. Windows displays a message stating that Cursor is still installing, preventing shutdown.
5. After forcing the shutdown and restarting the system, the following message appears:
   

Observed Behavior

• Cursor appears installed, with its icon and folders present, but cannot be uninstalled via Control Panel or Start Menu.
• Running the Cursor installer again is the only way to use it, as it installs over the existing (broken) installation.

This is my experience; it may vary, but I have noticed this issue since I started using these services.

[SimarMann]

I'm also experiencing this error.
Windows 10
WSL2
Cursor 0.45

Here's a previous issue post referencing this error :
https://github.com/getcursor/cursor/issues/1122

For me the error started when I closed cursor but noticed it was still running in task manager so I ended the process, now when I attempt to start cursor I get this error.

[saadfarooq07]

Hey chat

…

On Wed, Feb 5, 2025 at 12:18 AM SimarMann ***@***.***> wrote: I am also experiencing this error. Windows 10 WSL2 Cursor 0.45 Here's a previous issue post referencing this error : #1122 (comment) <http://url> — Reply to this email directly, view it on GitHub <#2650 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIIRGGI7CICVDLK3Z6NDE2T2OGNKDAVCNFSM6AAAAABWPOV3EGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVG4ZDKNJUGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[menix1337]

I get the same. I reinstalled it yesterday - because it for some reason had "Removed itself?", booted up today and get these errors too.