Cant use Powershell 7

Support Help
,
1

Hi!

I am not sure if I am just missing something obvious, but I can not get my agents in Cursor to use Powershell 7. It’s always stuck to the default Powershell 5.1 Installation that ships with Windows 11.

I changed my Default Terminal, which works perfectly fine in the Terminal Window, but not in the Agent Window.

My settings.json:

{
    "window.commandCenter": true,
    "terminal.integrated.defaultProfile.windows": "PowerShell"
}

And here’s my Terminal:

PS C:\Users\roomt> $PSVersionTable.PSVersion

Major  Minor  Patch  PreReleaseLabel BuildLabel
-----  -----  -----  --------------- ----------
7      5      4

PS C:\Users\roomt> ^C
PS C:\Users\roomt>

Vs my agent

# PowerShell version check
_Exported on 2/10/2026 at 11:18:11 GMT+1 from Cursor (2.4.35)_

---

**User**

Check the powershell version, please.

---

**Cursor**

I’ll query PowerShell directly and report the exact version installed.

PowerShell version is:

- **Major:** `5`
- **Minor:** `1`
- **Build:** `26100`
- **Revision:** `7462`

So you’re on **PowerShell 5.1.26100.7462**.

I updated and reinstalled Cursor completely to version 2.4.35.

I also changed my Terminal to Legacy Terminal (which is a suggestion I found somewhere via Google) which also did not help.

I would really like to be able to use PS7 with my Cursor.

As a sidenote, Antigravity which I also use, has no problem picking up PS7 so this would appear to be some kind of problem with Cursor specifically.

I am not 100% though if it is a bug or if I am just missing another setting.

Thanks for the help.

3

your agent’s terminal path in Cursor is probably decoupled from the integrated terminal profile on Windows

try:

  • enable Legacy Terminal Tool (Settings > Agents > Inline Editing & Terminal) and then run “Terminal: Kill All Terminals” and fully restart Cursor. this has worked on some of these issues in the past
  • can workaround the agent shell being in 5.1 by running pwsh -NoLogo -NoProfile -Command “$PSVersionTable.PSVersion”
5

I found a better solution. I had originally installed Powershell 7 via the Microsoft Store. This would just not work whatever I did.

Uninstalling it from the Store and downloading it via WinGet fixed all the issues for me.

1 Like