Powershell & PWSH

Question

As a new user trying to learn different aspects of Windows Microsoft Platform. I’m left with some confusion. Is there some profound reasoning behind when pwsh download is installed it is not amalgamated with Powershell automatically or are they kept separate to keep system stability of Microsoft Core elements because pwsh is cross platform?

It seems the syntax for most cmdlets are similar or the same . The variable is ever so slight and I can’t understand reasoning why these have not been repurposed or tied in to make both programs of similar nature collated and seamless.

This would only seem practical as a majority of the requested syntax overall have the same or similar outcome. I understand it is also dependent on which version or package manager is used when integrating

both. It would seem prudent to use say the same package manager (winget) for both installs as a baseline before the introduction of what you could say “third party” variables or add on’s. (like choco)

I guess the question is what is the most practical and stable way to ensure both programs work in harmony as a solid baseline.

Many Thanks

Noob

Answer 1

Hello, my name is Anis. I'll be glad to help you today.

The separation between PowerShell (Windows PowerShell, i.e., powershell.exe) and PowerShell Core (now simply called PowerShell, i.e., pwsh) is intentional and stems from several technical, compatibility, and strategic reasons:

Windows PowerShell (powershell.exe) is deeply integrated into Windows. Many system administration scripts, modules (like ActiveDirectory, Exchange), and legacy applications depend on it.

PowerShell (Core) (pwsh) is cross-platform and modular. While it brings modern improvements, it lacks some Windows-specific APIs and modules.

Merging them automatically could break existing scripts that rely on Windows-specific features, leading to system instability in managed environments.

Answer 2

Thanks for your reply. I thought that was the case. More over what is the best route to take to provide a more symbiotic relationship between both or is it advisable to keep the separation given Powershell being a core element.

Is it best to only use winget as the preferred package manager.

Many Thanks

Noob

Answer 3

The best approach to managing PowerShell (pwsh) and Windows PowerShell (powershell.exe) depends on your use case, environment, and long-term goals.

I have created a comparison chart (Picture attached) where you can find key considerations and recommendations for fostering a symbiotic relationship between the two, along with guidance on package management (including winget).

Please refer to the attached image.