Skip go content

pwsh.exe

Application ProcessMicrosoft Corporation

Catalog search terms pwsh, powershell 7, powershell core

WindowsApplication

PowerShell 7. Na di cross-platform pwsh host, wey dey often dey under Program Files\PowerShell\7. E no be Windows PowerShell 5.1 (powershell.exe).

Wetin you need know

pwsh na PowerShell 7, no be Windows PowerShell 5.1.

pwsh.exe na PowerShell 7, wey dem install from Microsoft as side-by-side host. powershell.exe na still Windows PowerShell 5.1 inside System32\WindowsPowerShell. Windows Terminal and OpenConsole only dey draw di window. To end pwsh no dey comot 5.1.

E safe?
Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
Same tin as powershell.exe?
No. Dat one na Windows PowerShell 5.1
I fit end am?
Dat PowerShell 7 session go stop
Feex tok say
If I see pwsh, I dey read di command line as PowerShell 7. I no dey treat powershell.exe as di same host, and I no dey blame conhost for 7-only module.

Wetin be pwsh.exe?

pwsh na PowerShell 7, no be Windows PowerShell 5.1. Di 5.1 host dey remain powershell.exe. Dis file na di newer runtime wey you install. E no be Windows Terminal.

Wetin e dey do?

E dey run PowerShell 7 scripts and modules. Some 5.1 snap-ins no go load here. E no dey draw di tab UI (WindowsTerminal.exe) and e no be cmd.exe.

Wetin make am dey run?

You open PowerShell 7, VS Code terminal wey dem set to pwsh, or task call dis host. PC wey get only 5.1 no go show Program Files\PowerShell\7 copy.

Inspect the running instance

Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)

Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'pwsh.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List

No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)

Use the file-identity guide to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)

E dey safe?

Host legit. Na di script bi di question

Microsoft-signed pwsh under Program Files\PowerShell na PowerShell 7. pwsh.exe inside Temp no be dat one. Safety na still di parent and di -Command line. Dis na still no be powershell.exe.

Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)

C:\Program Files\PowerShell\7\pwsh.exe

  • PowerShell 7 side-by-side install
  • Windows PowerShell 5.1 na System32\WindowsPowerShell\v1.0\powershell.exe
  • Window fit be Windows Terminal or OpenConsole

I fit end am?

E dey stop dat 7 session

To end pwsh.exe dey kill PowerShell 7. powershell.exe 5.1 fit stay. To end WindowsTerminal.exe only dey close di tab UI, no be every 7 host wey task start.

I fit comot am?

Uninstall PowerShell 7, keep 5.1

Uninstall PowerShell from Apps if you want make pwsh comot. No delete System32\powershell.exe. No delete System32.

E suppose start with Windows?

Scheduled task or profile fit start pwsh. Dat one no be di 5.1 host and no be Windows default wey get name powershell.exe.

Measure resource use

Measure the current process rather than assume a universal baseline
CPU and memory Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm)
Disk and network Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm)

File information

pwsh.exe file information
Executable name pwsh.exe
Recorded installation path C:\Program Files\PowerShell\7\pwsh.exe
Publisher Microsoft Corporation
Signature check Inspect the actual file; this entry no dey certify its certificate identity. (pcm)

Common wahala dem

5.1-only snap-in fail and dem repair powershell.exe

Dis host na 7. Install di 7 module or run Windows PowerShell 5.1. Different exe, different gallery story.

Hidden pwsh from random task

Read -File / -Command. Di 7 host na still Microsoft. Di payload na di line. Dat one no be "Terminal na malware."

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

pwsh -v versus $PSVersionTable inside powershell.exe

7 dey print from dis file. 5.1 dey print from Windows PowerShell. No mix di upgrade docs.

Check parent PID di same way you go do for 5.1

explorer plus shortcut na you. Office wey dey launch pwsh na macro story. No delete di 7 install folder as di first move.

Technical details

Technical details
pwsh.exe technical details
Image name pwsh.exe
Sibling powershell.exe (Windows PowerShell 5.1)

Check the identity of running file

A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Dis article make sense to you?