Hey, thanks for the report. This issue was fixed before in v2.1.36, but it looks like it’s happening again on your setup.
A couple quick clarifications. The report says Win11, but the system info shows Windows 10 build 17763 (LTSC 2019). Which Windows version are you actually on?
Also a few questions:
After Cursor closes during the update and doesn’t restart, if you open it manually, does the update apply (does the version actually change)?
Are you using any antivirus or corporate security policies?
Do you run Cursor as an admin or as a regular user?
The team knows this can still happen in some cases. Let me know the answers above, it’ll help us narrow down the cause.
Sorry I’m actually going to correct that I’m actually running it on a few machines I remote into and it’s just dawned on me actually where the issue is showing is on a Windows Server Data Center 2019 VM which is I guess why it’s showing up as Windows 10.