# New update results in WSL breaking

**URL:** <https://forum.cursor.com/t/new-update-results-in-wsl-breaking/157601>\
**Category:** Bug Reports\
**Tags:** installation, crashes, wsl\
**Created:** [April 14, 2026, 9:27am UTC](https://forum.cursor.com/t/new-update-results-in-wsl-breaking/157601 "2026-04-14T09:27:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Plumelz](https://avatars.discourse-cdn.com/v4/letter/p/ccd318/32.png) [@Plumelz](https://forum.cursor.com/u/Plumelz)\
**Post date:** [April 14, 2026, 9:27am UTC](https://forum.cursor.com/t/new-update-results-in-wsl-breaking/157601/1 "2026-04-14T09:27:52Z")

</div>

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

Cursor IDE

### Describe the Bug

Upon updating Cursor this morning and reopening my project via WSL: Ubuntu, I get “The editor could not be opened due to an unexpected error. Please consult the log for more details.”  
Also, I noticed the WSL extension has been updated today, could be related?

In Remote - WSL logs, is the following:  
2026-04-14 10:14:03.253 [error] Failed to patch code.sh launcher: Error: ENOENT: no such file or directory, open ‘c:\Users\user\AppData\Local\Programs\cursor\resources\app\bin\code’  
2026-04-14 10:14:16.860 [error] Failed to patch code.sh launcher: Error: ENOENT: no such file or directory, open ‘c:\Users\user\AppData\Local\Programs\cursor\resources\app\bin\code’  
2026-04-14 10:14:16.921 [info] Resolving wsl remote authority ‘wsl+ubuntu’ (attempt #1)  
2026-04-14 10:14:16.938 [info] Installing cursor-server with options: {“id”:“f8cbd6fc47c57be2c27f1133”,“commit”:“dacbe9b31599a253763e4910eb6ab38704653320”,“line”:“production”,“realCommit”:“dacbe9b31599a253763e4910eb6ab3870465332c”,“extensionIds”:,“serverApplicationName”:“cursor-server”,“serverDataFolderName”:“.cursor-server”,“forceReinstall”:true,“killRunningServers”:false,“host”:“127.0.0.1”}  
2026-04-14 10:14:17.132 [info] [wsl exec: installServerScript][stderr]: your 131072x1 screen size is bogus. expect trouble  
2026-04-14 10:14:19.789 [info] [wsl exec: installServerScript][stderr]: 2026-04-14 10:14:19 URL:[https://downloads.cursor.com/production/dacbe9b31599a253763e4910eb6ab3870465332c/linux/x64/cursor-reh-linux-x64.tar.gz](https://downloads.cursor.com/production/dacbe9b31599a253763e4910eb6ab3870465332c/linux/x64/cursor-reh-linux-x64.tar.gz) [104151084/104151084] → “/tmp/tmp.fYgyXNBLEE” [1]  
2026-04-14 10:14:24.944 [info] [wsl exec: installServerScript][stderr]: your 131072x1 screen size is bogus. expect trouble  
2026-04-14 10:14:24.964 [info] [wsl exec: installServerScript][stderr]: ++ ‘[’ ‘!’ -d /home/user//bin/ ‘]’  
2026-04-14 10:14:24.964 [info] [wsl exec: installServerScript][stderr]: ++ ‘[’ ‘!’ -d /home/user//bin\_commit ‘]’  
2026-04-14 10:14:24.964 [info] [wsl exec: installServerScript][stderr]: ++ set -e  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: ++ fix\_download  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: ++ case “$QUALITY” in  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: ++ echo 'unknown quality: ’  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: unknown quality:  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: ++ return 1  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: + release\_lock  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: + lockfile=/home/user/.cursor-server/.installation\_lock  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: + ‘[’ -n 12235 ‘]’  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: + kill 12235  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: + echo ‘Unlocking /home/user/.cursor-server/.installation\_lock’  
2026-04-14 10:14:24.965 [info] [wsl exec: installServerScript][stderr]: + rm -f /home/user/.cursor-server/.installation\_lock  
2026-04-14 10:14:24.969 [info] [wsl exec: installServerScript][stderr]: + ‘[’ -n /home/user/.cursor-server/.installation\_lock.target.23025-31102-12206-1776158058 ‘]’  
2026-04-14 10:14:24.969 [info] [wsl exec: installServerScript][stderr]: + rm -f /home/user/.cursor-server/.installation\_lock.target.23025-31102-12206-1776158058  
2026-04-14 10:14:24.971 [info] [wsl exec: installServerScript][stderr]: + rm -f /home/user/.cursor-server/.installation\_lock.target  
2026-04-14 10:14:25.359 [error] Error installing Cursor server [wsl exec: installServerScript] Command failed with exit code 1: stdout: Killing all running Cursor servers  
No running servers found  
Killing running servers:  
Removing all existing Cursor installations  
**CURSOR\_LOCK\_PREEMPT** component=remote-wsl reason=forceReinstall lock\_file=/home/user/.cursor-server/.installation\_lock

### Steps to Reproduce

Install latest cursor update.  
Attempt to open project via WSL: Ubuntu

### Expected Behavior

Should open my project without failing. Currently Cursor is unusable.

### Operating System

Windows 10/11

### Version Information

Version: 3.1.10 (user setup)  
VSCode Version: 1.105.1  
Commit: dacbe9b31599a253763e4910eb6ab38704653320  
Date: 2026-04-13T11:39:16.806Z  
Layout: editor  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<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:** [April 14, 2026, 10:20am UTC](https://forum.cursor.com/t/new-update-results-in-wsl-breaking/157601/5 "2026-04-14T10:20:59Z")

</div>

Hey, this is a known issue with WSL in the latest versions. The logs show two things: a missing `code.sh` launcher file and `unknown quality:` when installing cursor-server. Both can block the connection.

Try this workaround that helped other users:

- Open Cursor locally, not in WSL
- Go to Extensions and find the WSL extension
- Switch it to version v0.08 via Install Another Version…
- Restart Cursor
- Then update the WSL extension back to the latest version
- Restart Cursor and try connecting to WSL again

If that doesn’t help, also try:

- Inside WSL run `rm -rf ~/.cursor-server`
- In PowerShell run `wsl --shutdown`
- Reconnect to WSL from Cursor

More context in a similar resolved thread: [Cursor WSL error: Failed to patch code.sh launcher](https://forum.cursor.com/t/cursor-wsl-error-failed-to-patch-code-sh-launcher/155773)

The team is aware of this issue, and your report helps with prioritization. Let me know if the workaround doesn’t work.

---

<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:** [April 14, 2026, 10:21am UTC](https://forum.cursor.com/t/new-update-results-in-wsl-breaking/157601/6 "2026-04-14T10:21:40Z")

</div>

Split this topic on April 14, 2026, 10:21am UTC

A post was merged into an existing topic: [Can’t connect to WSL anymore](https://forum.cursor.com/t/cant-connect-to-wsl-anymore/153737)

---

<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:** [April 14, 2026, 10:21am UTC](https://forum.cursor.com/t/new-update-results-in-wsl-breaking/157601/7 "2026-04-14T10:21:46Z")

</div>

Closed on April 14, 2026, 10:21am UTC