# Start of the Cursor will trigger a Wsl Start pop up cmd window

**URL:** <https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065>\
**Category:** Bug Reports\
**Created:** [September 19, 2025, 5:45am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065 "2025-09-19T05:45:25Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Apaca](https://avatars.discourse-cdn.com/v4/letter/a/a698b9/32.png) [@Apaca](https://forum.cursor.com/u/Apaca)\
**Post date:** [September 19, 2025, 5:45am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/1 "2025-09-19T05:45:25Z")

</div>

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

Cursor IDE

### Describe the Bug

Recently whenever i launch the cursor , it will pop out a cmd window of my wsl env  
same thing happen in my :

- my Win 10 home pc
- my Win 11 work pc

I tried to uninstall all the wsl / remote related Addin but it still happening

### Steps to Reproduce

launch the cursor

### Expected Behavior

Not lanuch it maybe ?

### Operating System

Windows 10/11

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

My home pc :  
Version: 1.6.27 (user setup)  
VSCode Version: 1.99.3  
Commit: d750e54bba5cffada6d7b3d18e5688ba5e944ad0  
Date: 2025-09-17T20:21:17.042Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Windows\_NT x64 10.0.19045

My Work :  
Version: 1.6.27 (user setup)  
VSCode Version: 1.99.3  
Commit: d750e54bba5cffada6d7b3d18e5688ba5e944ad0  
Date: 2025-09-17T20:21:17.042Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Windows\_NT x64 10.0.22631

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![wKovacs64](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/wkovacs64/32/75367_2.png) [@wKovacs64](https://forum.cursor.com/u/wKovacs64)\
**Post date:** [September 19, 2025, 11:46pm UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/2 "2025-09-19T23:46:34Z")

</div>

Same, and it tries to run a few commands that all fail.

```auto
awk: cmd. line:1: "BEGIN
awk: cmd. line:1: ^ unterminated string
awk: cmd. line:1: "BEGIN
awk: cmd. line:1: ^ unterminated string
awk: cmd. line:1: "BEGIN
awk: cmd. line:1: ^ unterminated string
awk: cmd. line:1: "BEGIN
awk: cmd. line:1: ^ unterminated string
base64: invalid input
/bin/bash: line 8: $' \\"$var_name\\"\n builtin printf ': command not found
__CURSOR_STATE_MARKER__

-x: command not found

[process exited with code 127 (0x0000007f)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

```

---

<div class="post-metadata">

**Author:** ![tienlx91](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tienlx91/32/67760_2.png) [@tienlx91](https://forum.cursor.com/u/tienlx91)\
**Post date:** [September 20, 2025, 12:08am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/4 "2025-09-20T00:08:36Z")

</div>

I just report exact the same as yours

 ![Clipboard Image (29)](https://us1.discourse-cdn.com/cursor1/original/3X/3/a/3addcab28c069f16e2efc652be8e6877a8886316.jpeg)

---

<div class="post-metadata">

**Author:** ![nattapon-weaverbase](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/nattapon-weaverbase/32/80298_2.png) [@nattapon-weaverbase](https://forum.cursor.com/u/nattapon-weaverbase)\
**Post date:** [September 20, 2025, 3:55am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/6 "2025-09-20T03:55:26Z")

</div>

I am having the same problem.

The problem occurs every time when I do any of these.

1. When I start Cursor from the start-menu.
2. When I click on “File =\> New Windows” in a Cursor window.
3. When I run `cursor .` at the working directory in WSL Ubuntu shell.

It seems like any action that create new window of Cursor can trigger the problem.

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/4/3/43a31334c11b780839776c35482edf4fca57a3a4.png)

---

<div class="post-metadata">

**Author:** ![tienlx91](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tienlx91/32/67760_2.png) [@tienlx91](https://forum.cursor.com/u/tienlx91)\
**Post date:** [September 20, 2025, 4:08am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/8 "2025-09-20T04:08:01Z")

</div>

While waiting for Cursor to look at it, did you also just install cursor-cli like I did? I think the potential culprit might actually be cursor-cli

---

<div class="post-metadata">

**Author:** ![hcw\_han](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/hcw_han/32/80300_2.png) [@hcw\_han](https://forum.cursor.com/u/hcw_han)\
**Post date:** [September 20, 2025, 5:09am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/10 "2025-09-20T05:09:43Z")

</div>

I am having the same problem.

---

<div class="post-metadata">

**Author:** ![andrewh](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/andrewh/32/65515_2.png) [@andrewh](https://forum.cursor.com/u/andrewh)\
**Post date:** [September 20, 2025, 6:36am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/12 "2025-09-20T06:36:08Z")

</div>

Could you share a screenshot of what you are seeing?

---

<div class="post-metadata">

**Author:** ![andrewh](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/andrewh/32/65515_2.png) [@andrewh](https://forum.cursor.com/u/andrewh)\
**Post date:** [September 20, 2025, 6:36am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/13 "2025-09-20T06:36:37Z")

</div>

> [@Apaca](#):
>
> Recently whenever i launch the cursor , it will pop out a cmd window of my wsl env  
> same thing happen in my :

Is this from launching with `cursor`?

---

<div class="post-metadata">

**Author:** ![Tsuk1ko](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tsuk1ko/32/80314_2.png) [@Tsuk1ko](https://forum.cursor.com/u/Tsuk1ko)\
**Post date:** [September 20, 2025, 7:56am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/14 "2025-09-20T07:56:50Z")

</div>

The same issue is occurring, it seems to have appeared in the latest version, as the previous version didn’t have this problem.

This happens when opening Cursor, including when reloading the window.

![Cursor_dkXY3xCejP](https://us1.discourse-cdn.com/cursor1/original/3X/1/7/17cfb72981521b26f471f803a4049ac68539220a.gif)

---

<div class="post-metadata">

**Author:** ![user616](https://avatars.discourse-cdn.com/v4/letter/u/ee7513/32.png) [@user616](https://forum.cursor.com/u/user616)\
**Post date:** [September 20, 2025, 9:09am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/16 "2025-09-20T09:09:48Z")

</div>

I have the same problem , when I launch cursor, I will encounter this situation.

---

<div class="post-metadata">

**Author:** ![tienlx91](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tienlx91/32/67760_2.png) [@tienlx91](https://forum.cursor.com/u/tienlx91)\
**Post date:** [September 20, 2025, 9:26am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/18 "2025-09-20T09:26:29Z")

</div>

After Cursor window launched and right after that the cmd window appear, it seem like the Cursor.exe somehow trigger that cmd run wsl.exe window

---

<div class="post-metadata">

**Author:** ![person1](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@person1](https://forum.cursor.com/u/person1)\
**Post date:** [September 20, 2025, 12:03pm UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/20 "2025-09-20T12:03:32Z")

</div>

Same issue

---

<div class="post-metadata">

**Author:** ![Grzegorz96](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/grzegorz96/32/80339_2.png) [@Grzegorz96](https://forum.cursor.com/u/Grzegorz96)\
**Post date:** [September 20, 2025, 1:08pm UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/22 "2025-09-20T13:08:51Z")

</div>

I have the same problem, after updating Cursor to the newest version i have the same bug and also i saw in Output: Remote - WSL logs like this, I don’t know if it’s related to this bug.

![Cursor_R5T1MlKkPg](https://us1.discourse-cdn.com/cursor1/original/3X/1/f/1f2b505bdd7f034b059aa7b49bf8ccb655d50338.png)

---

<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:** [September 20, 2025, 3:23pm UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/24 "2025-09-20T15:23:00Z")

</div>

Hi all, thank you for reporting this issue. We are working on testing a fix for it and should have an update available soon.

---

<div class="post-metadata">

**Author:** ![kevinmarrec.steeple](https://avatars.discourse-cdn.com/v4/letter/k/e47774/32.png) [@kevinmarrec.steeple](https://forum.cursor.com/u/kevinmarrec.steeple)\
**Post date:** [September 20, 2025, 10:29pm UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/25 "2025-09-20T22:29:51Z")

</div>

I had this issue for the whole day and an update popped few minutes ago.

Looks good to me, here’s my Cursor info:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/9/5/955664f41dc07039ab92392ff8a070f375778885.png)

---

<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:** [September 21, 2025, 5:00pm UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/27 "2025-09-21T17:00:06Z")

</div>

Hi all, as @kevinmarrec.steeple noted, this issue should be fixed in version 1.6.42. Could you try upgrading?

---

<div class="post-metadata">

**Author:** ![Apaca](https://avatars.discourse-cdn.com/v4/letter/a/a698b9/32.png) [@Apaca](https://forum.cursor.com/u/Apaca)\
**Post date:** [September 23, 2025, 7:05am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/28 "2025-09-23T07:05:12Z")

</div>

After upgrade both my win10 and win11 works fine without the pop up. Thanks !

---

<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:** [October 15, 2025, 7:05am UTC](https://forum.cursor.com/t/start-of-the-cursor-will-trigger-a-wsl-start-pop-up-cmd-window/134065/29 "2025-10-15T07:05:52Z")

</div>

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