Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Looks like this exact bug is back -
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 (use…
Steps to Reproduce
Launch Cursor (Windows)
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.46 (user setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Does this stop you from using Cursor
No - Cursor works, but with this issue
deanrie
(Dean Rie)
December 2, 2025, 10:12am
3
Hey, thanks for the report, I’ll pass it to the team.
Is there any further update on this? The wsl popup is vert annoying.
ravirahman
(Ravi Rahman)
December 17, 2025, 4:05am
7
Can you share a screencast / steps to reproduce?
Steps to reproduce:
Launch Cursor. A WSL window pops up along with it.
Close that WSL window.
Click Terminal → New Terminal. A new terminal panel opens, but along with that, WSL Window pops up as well.
Screenshot:
Troubleshooting Done:
Verified Terminal: Select Default Profile is set to PowerShell 7
Confirmed terminal.integrated.defaultProfile.windows is set to PowerShell 7
Verified workspace settings (.vscode/) don’t exist
Confirmed terminal.integrated.automationProfile.windows is empty
No VSCode/Cursor extensions installed
No WSL references found in any Cursor configuration files
Git configuration clean (no WSL credential helpers or paths)
No WSL-related Windows startup items or scheduled tasks
Current working theory: Cursor is probing for available shells/terminals during startup, which triggers WSL even though it’s not configured or selected.
About:
Version: 2.2.20 (user setup)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
ravirahman
(Ravi Rahman)
December 17, 2025, 10:32pm
10
Are you able to upgrade WSL? If so, does the popup go away?
Yep! I updated wsl with that command and now the wsl window popup with Cursor stopped. So, the issue can be considered “solved”, I guess.
But it still confuses me as to why was Cursor tapping WSL anyway?