Apaca
September 19, 2025, 5:45am
1
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
6 Likes
Same, and it tries to run a few commands that all fail.
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.
I just report exact the same as yours
I am having the same problem.
The problem occurs every time when I do any of these.
When I start Cursor from the start-menu.
When I click on “File => New Windows” in a Cursor window.
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.
1 Like
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
1 Like
hcw_han
September 20, 2025, 5:09am
10
I am having the same problem.
andrewh
September 20, 2025, 6:36am
12
Could you share a screenshot of what you are seeing?
andrewh
September 20, 2025, 6:36am
13
Is this from launching with cursor?
Tsuk1ko
September 20, 2025, 7:56am
14
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.
user616
September 20, 2025, 9:09am
16
I have the same problem , when I launch cursor, I will encounter this situation.
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
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.
Hi all, thank you for reporting this issue. We are working on testing a fix for it and should have an update available soon.
3 Likes
I had this issue for the whole day and an update popped few minutes ago.
Looks good to me, here’s my Cursor info:
1 Like
Hi all, as @kevinmarrec.steeple noted, this issue should be fixed in version 1.6.42. Could you try upgrading?
1 Like
Apaca
September 23, 2025, 7:05am
28
After upgrade both my win10 and win11 works fine without the pop up. Thanks !
system
Closed
October 15, 2025, 7:05am
29
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.