@clean128 the solution is already up in the thread, thanks to @code_ranger for the diagnosis. The culprit is Astrill registering a Winsock LSP C:\WINDOWS\system32\ASProxy64.dll that gets injected into the process and crashes the extension host. That’s why VS Code crashes the exact same way, and why everything works in an Ubuntu VM. It’s a Windows networking issue, not a Cursor issue.
Important detail: just disabling or uninstalling the Astrill client isn’t enough. The LSP stays registered in the Winsock catalog. That’s why the crash doesn’t go away after turning off the VPN.
Things to try:
-
Reset the Winsock catalog. Open PowerShell or CMD as admin and run:
netsh winsock resetThen reboot Windows. This removes the stuck LSP entries. Note that if you launch Astrill again, it may register the LSP again.
-
You can check what’s still in the catalog with:
netsh winsock show catalogIf Astrill adds
ASProxy64.dllagain after the reset and the crashes come back, this needs to be fixed on Astrill’s side. For example their split tunneling or App Filter to exclude the Cursor process, or updating or reinstalling their client.
Since VS Code behaves identically, the final fix here is on Astrill’s side. Let us know if netsh winsock reset helped. If the crash comes back, paste the output of netsh winsock show catalog and we’ll take a look at what’s registered there.