# Wsl error since the new update

**URL:** <https://forum.cursor.com/t/wsl-error-since-the-new-update/128458>\
**Category:** Bug Reports\
**Created:** [August 11, 2025, 3:22pm UTC](https://forum.cursor.com/t/wsl-error-since-the-new-update/128458 "2025-08-11T15:22:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jorge\_castillo](https://avatars.discourse-cdn.com/v4/letter/j/3be4f8/32.png) [@jorge\_castillo](https://forum.cursor.com/u/jorge_castillo)\
**Post date:** [August 11, 2025, 3:22pm UTC](https://forum.cursor.com/t/wsl-error-since-the-new-update/128458/1 "2025-08-11T15:22:54Z")

</div>

### Describe the Bug

since the last update I’ve being getting this error using cursor with wsl

```auto
Connection to Cursor server failed: [wsl exec: installServerScript] Command failed with exit code 4294967295: stdout: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Error code: Wsl/Service/0x8007274c  

```

The only solution is restarting my pc.

have to restart my pc 4 5 times at day because of this !!!

### Steps to Reproduce

the bug show itself nothing to do

### Screenshots / Screen Recordings

 ![Screenshot 2025-08-11 112023.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/5/05f17af59c8a36525cae210b45a01ad4e1f46f10.png)

### Operating System

Windows 10/11

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

current version with wsl

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<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:** [August 12, 2025, 7:19am UTC](https://forum.cursor.com/t/wsl-error-since-the-new-update/128458/3 "2025-08-12T07:19:26Z")

</div>

Hi @jorge_castillo, this happens when the WSL process becomes unresponsive. To avoid restarting your PC, you can try running `wsl --shutdown`, and then reopen Cursor. This will restart just the WSL process.

---

<div class="post-metadata">

**Author:** ![buzzthedev1](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/buzzthedev1/32/45471_2.png) [@buzzthedev1](https://forum.cursor.com/u/buzzthedev1)\
**Post date:** [August 12, 2025, 10:38pm UTC](https://forum.cursor.com/t/wsl-error-since-the-new-update/128458/4 "2025-08-12T22:38:54Z")

</div>

I am getting this too and it’s really annoying. It stops me from using Cursor all together because of this

---

<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:** [September 3, 2025, 10:39pm UTC](https://forum.cursor.com/t/wsl-error-since-the-new-update/128458/6 "2025-09-03T22:39:21Z")

</div>

Closed on September 3, 2025, 10:39pm UTC

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