Terminal on windows totally broken

[FlamesONE (Nikita)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When agent wants to execute some command in the terminal, it fails.
I’m really tired, every update ruined some of aspects of my work…

Steps to Reproduce

Ask to run any command in powershell.

Expected Behavior

Work at least…

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

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.26100

For AI issues: which model did you use?

Any

Additional Information

It works before.

5c8be793-7242-4603-a4ef-9e91a9c1950b

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. I see the screenshot with running ps-script-*.ps1 and broken encoding in PowerShell.

This is a known issue on Windows. Switching to the legacy terminal tool usually helps:

1. Settings Ctrl+Shift+J → Agents → Inline Editing & Terminal → enable Legacy Terminal Tool
2. Ctrl+Shift+P → Terminal: Kill All Terminals
3. Fully restart Cursor

If it still breaks after these steps, please share:

• Windows system locale and display language
• Your terminal profile in Cursor (PowerShell 5.1 or 7, CMD, WSL)
• Output of $PSVersionTable and chcp from the integrated terminal
• Errors from Help → Toggle Developer Tools → Console when you run the command
• Request ID for the failing run (in chat → Copy Request ID)

Let us know if Legacy Terminal Tool helped.

[FlamesONE (Nikita)]

I already did that, didn’t help.

I fully reinstall cursor on 2.1.50 and it works, on 2.2.50 error the same.

I’m not going to install 2.2.x version again because its too buggy (terminal broken, high cpu usage, memory leaks with browser and other)

[deanrie]

Thanks for confirming that Legacy Terminal Tool didn’t help and that the issue is specific to version 2.2.x.

This is a known terminal issue on Windows in 2.2.x versions. The team is working on a fix. Since 2.1.50 works for you, you can stay on that version for now.