Hey, thanks for the report. This is a known WSL connection issue. Error code 0x8007274c is a Windows socket timeout, which means the WSL process stops responding and Cursor can’t reach its server.
Try these steps in order:
Run wsl --shutdown in PowerShell, then reopen the project
If that doesn’t help, reboot your computer
Check if you have any pending Windows updates. This fixed it for some users
Run htop inside WSL to check CPU and memory usage. WSL can quietly hit resource limits
If it keeps happening, these long term fixes can help:
Create or edit .wslconfig in your Windows user folder and raise the memory and CPU limits
Make sure you’re on the latest WSL version: wsl --update
Let me know if the issue still happens after these steps.
Yes, I’ve been using wsl --shutdown as a workaround. It temporarily fixes the issue, but it always comes back after some time, which makes it very disruptive.
I’ll try adjusting the memory and CPU limits using .wslconfig and make sure WSL is fully up to date. I’ll report back if the issue still happens after that.
After increasing the WSL resources to 8GB of memory, the issue is no longer happening as frequently. It hasn’t completely disappeared, but it’s much less constant now, so the situation is definitely more stable than before.
