# Bug report for WSL on win 11

**URL:** <https://forum.cursor.com/t/bug-report-for-wsl-on-win-11/141992>\
**Category:** Bug Reports\
**Created:** [November 10, 2025, 5:22pm UTC](https://forum.cursor.com/t/bug-report-for-wsl-on-win-11/141992 "2025-11-10T17:22:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Del1ght](https://avatars.discourse-cdn.com/v4/letter/d/2bfe46/32.png) [@Del1ght](https://forum.cursor.com/u/Del1ght)\
**Post date:** [November 10, 2025, 5:22pm UTC](https://forum.cursor.com/t/bug-report-for-wsl-on-win-11/141992/1 "2025-11-10T17:22:13Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Connection to Cursor server failed: [wsl exec: installServerScript] Command failed with exit code 4294967295: stdout: Catastrophic failure Error code: Wsl/Service/E\_UNEXPECTED

### Steps to Reproduce

Using WSL connection on Windows 11 after the recent update.

### Expected Behavior

Remote WSL asks to reinstall or reload, which doesn’t solve the issue unless I restart my device.

### Operating System

Windows 10/11

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.64 (user setup)  
VSCode Version: 1.99.3  
Commit: 25412918da7e74b2686b25d62da1f01cfcd27680  
Date: 2025-11-06T04:35:14.424Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Windows\_NT arm64 10.0.26200

### Additional Information

I have seen a similar bug report in August, but I couldn’t find a solution to resolve it.

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [November 10, 2025, 6:46pm UTC](https://forum.cursor.com/t/bug-report-for-wsl-on-win-11/141992/2 "2025-11-10T18:46:47Z")

</div>

Hey, thanks for the report. This is a known WSL system error. “Catastrophic failure” with code `Wsl/Service/E_UNEXPECTED` indicates an issue with WSL itself, not Cursor.

Solution - try these steps in order:

1. Run: `wsl --shutdown`
2. If that doesn’t help, reboot your computer
3. Check for pending Windows updates (some users fixed it by installing OS updates)

Let me know if the issue persists after these steps!

---

<div class="post-metadata">

**Author:** ![wistb](https://avatars.discourse-cdn.com/v4/letter/w/f08c70/32.png) [@wistb](https://forum.cursor.com/u/wistb)\
**Post date:** [November 13, 2025, 5:34am UTC](https://forum.cursor.com/t/bug-report-for-wsl-on-win-11/141992/3 "2025-11-13T05:34:55Z")

</div>

this has been happening to me incessantly. what can we provide to help debug?

---

<div class="post-metadata">

**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\
**Post date:** [November 14, 2025, 4:51pm UTC](https://forum.cursor.com/t/bug-report-for-wsl-on-win-11/141992/5 "2025-11-14T16:51:51Z")

</div>

Could you run a `htop` within WSL to see if it is running out of CPU or memory? Usually when this happens the WSL environment is resource constrained.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [December 6, 2025, 4:52pm UTC](https://forum.cursor.com/t/bug-report-for-wsl-on-win-11/141992/6 "2025-12-06T16:52:14Z")

</div>

Closed on December 6, 2025, 4:52pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.