Recent Build /w WSL Dependency breaking Cursor

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am running Cursor on Windows 11. Have been keeping up on regular updates including the latest one Sep 19 2025.

Since that update, when I open Cursor, I now see the WSL exec run in a Windows command window (it closes quickly after showing a couple error messages I cannot read in time). There have been some functional blocker issues, so I have been doing some troubleshooting.

Evidently you have created a large dependency on running a Ubuntu disto on my laptop. I can deal with that, but a warning would have been nice! I have gone thru the steps and installed Ubuntu and am still having issues.

The primary issues are;

  1. Many Cursor Agent tries command executions in the chat window ‘terminal’ instance and they often just hang or fail

  2. The file explorer on the left side is not updating and keeping in sync with the Windows file system. Its showing me folders and files that have long since been removed

  3. On a regular basis after I do my own build in the terminal (usually a powershell term by default), I need to copy/paste the build errors into the chat. But lately when I do this, CTRL-C in the terminal (regardless if the build is running or not) will just put the C^ chars after the c: drive prompt. So no copy/paste is possible.

There are more but I think overall symptomatic of either a build break or this WSL issue.

Please provide some rapid and exceptional support here, I am working on a deadline and do not want to revert to VS Code with Claude Code CLI.

Steps to Reproduce

Steps are above.

Expected Behavior

I expect WSL to work without errors. I expect the file explorer to remain updated. I expect the terminal commands executing in chat to work properly and I expect to be able to copy/paste text from the terminal window back into chat for troubleshooting.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.35 (user setup)
VSCode Version: 1.99.3
Commit: b753cece5c67c47cb5637199a5a5de2b7100c180
Date: 2025-09-19T17:39:38.846Z
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.26100

For AI issues: which model did you use?

Sonnet 4

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
3

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