To check the PowerShell engine currently running on a Windows Server, run $PSVersionTable in that shell and read PSVersion. To update PowerShell 7, use the installation method already in use—or install it side-by-side with Windows PowerShell 5.1. Windows PowerShell 5.1 is updated through Windows Update; it is not replaced by PowerShell 7.
Check which PowerShell version a workload is using
Run the version command in the same kind of shell that runs the script or task you are checking. A server can have Windows PowerShell 5.1 and PowerShell 7 installed at the same time, so checking one shell does not establish which engine another workload uses.
$PSVersionTableRead PSVersion for the engine version and PSEdition for the edition. $PSHOME shows the installation directory and can help identify how PowerShell 7 was installed.
$PSVersionTable.PSVersion
$PSVersionTable.PSEdition
$PSHOMEThe executable name is a useful cross-check: powershell.exe starts Windows PowerShell, while pwsh.exe starts PowerShell 7 or later on Windows. Use the executable explicitly when checking a particular runtime:
#1 Best Overall
- 64 bit | 1 Server with 16 or less processor cores | provides 2 VMs
- For physical or minimally virtualized environments
- Requires Windows Server 2025 User and/or Device Client Access Licenses (CALs) | No CALs are included
- Core-based licensing | Additional license packs required for servers with more than 16 processor cores or to add VMs | 2 VMs whenever all processor cores are licensed.
- Product ships in plain envelope | Activation key is located under scratch-off area on label |Beware of counterfeits | Genuine Windows Server software is branded by Microsoft only.
powershell.exe -NoProfile -Command "$PSVersionTable"
pwsh.exe -NoProfile -Command "$PSVersionTable"If pwsh.exe is not found, PowerShell 7 may not be installed or its directory may not be on the current process’s PATH. That does not mean Windows PowerShell is absent: try powershell.exe or launch Windows PowerShell from the Start menu.
Check the operating-system version separately
$PSVersionTable reports the engine running the command, not a complete Windows Server version check. Use winver.exe or a documented Windows version command to inspect the operating-system build. The table’s BuildVersion is used for Windows PowerShell OS information; PowerShell 7 uses OS for OS information. Do not mistake the PowerShell engine version for the Windows Server release.
Know what an update changes
Windows PowerShell 5.1
Windows PowerShell 5.1 is built into Windows Server. Microsoft no longer develops it as a separate, advancing PowerShell product; security updates arrive through the normal Windows Update channels. Keep the server’s ordinary update management in place rather than looking for a PowerShell 5.1 installer to move it to PowerShell 7.
PowerShell 7 and later
PowerShell 7 is a separate product with its own installation and update path. Installing it does not remove or overwrite Windows PowerShell 5.1. Stable releases replace earlier stable releases through supported servicing, while preview releases can coexist with stable releases. Updating PowerShell 7 therefore means updating that installation—not changing the version returned by a separately launched powershell.exe.
Rank #2
- Offers quick and easy installation on PC
- The software is licensed for 5 User CAL
Identify how PowerShell 7 was installed
If you do not know the original installation method, inspect $PSHOME from pwsh.exe. These path clues are typical indicators, not a substitute for checking your deployment records:
- A path under
Program FilesPowerShell7usually indicates an MSI installation. - A path under
WindowsAppsindicates MSIX. - A path under
.dotnettoolsindicates the .NET global tool. - Another location is likely a ZIP-based installation or a manually managed copy.
Use the same installation method for the upgrade where possible. Mixing methods can leave multiple installations or make it unclear which executable a script, service, or scheduled task will launch. Check the actual path of the executable used by the workload, not just the version shown in an interactive terminal.
Choose an installation or upgrade route
| Route | When it fits | Operational detail |
|---|---|---|
| MSI | Preferred for Windows Server and enterprise deployment. | Can be run interactively or deployed with management software. MSI properties can opt into Microsoft Update, WSUS, or Configuration Manager servicing. |
| ZIP | Useful for Server Core, side-loading, or keeping multiple versions. | Administrators manage package replacement themselves; it does not provide the same integrated servicing behavior as MSI. |
| WinGet | Available on Windows Server 2025 with Desktop Experience. | Not available on Windows Server 2022 or earlier, according to Microsoft’s stated availability. |
MSI: the usual server and enterprise choice
Obtain the appropriate PowerShell 7 MSI and run it with suitable administrator rights, or deploy it through your organization’s management software. For managed environments, decide whether the MSI should participate in Microsoft Update, WSUS, or Configuration Manager servicing, and configure the relevant MSI properties in accordance with your update policy. The installer and package version available can change, so select the supported package appropriate to your server rather than relying on an old download or remembered version number.
ZIP: Server Core and controlled side-by-side installations
The ZIP package is useful when you need a side-loaded installation, are working on Server Core, or deliberately keep more than one PowerShell version. Extract and manage it in a location appropriate to your environment, then invoke the intended pwsh.exe explicitly. Unlike an MSI-managed installation, the ZIP package does not provide the same integrated servicing behavior: plan how administrators will replace the package and verify which version automation launches.
Recommended Free Tools
Rank #3
- Server 2022 Standard 16 Core
WinGet: Windows Server 2025 with Desktop Experience
On Windows Server 2025 with Desktop Experience, search the catalog and install PowerShell with these commands:
winget search --id Microsoft.PowerShell --exact
winget install --id Microsoft.PowerShell --source wingetTo see whether an upgrade is available and apply it:
winget list --id Microsoft.PowerShell --upgrade-available
winget upgrade --id Microsoft.PowerShellWinGet is not available on Windows Server 2022 or earlier. On those releases, use an appropriate MSI or ZIP installation route rather than treating a missing winget command as a PowerShell failure.
Verify the update and protect production workloads
- Record the current state. Run
$PSVersionTablein both the shell you administer and the shell used by important workloads. Note the executable and$PSHOME. - Choose the route deliberately. Match the update method to the existing installation where possible. Confirm Server release, Desktop Experience availability, administrative access, and your organization’s change process.
- Install or upgrade. Use MSI, ZIP, or WinGet only where appropriate for that server and deployment. Do not assume an installer has completed simply because a command prompt returned.
- Open a new shell and verify. Launch the intended executable, then check
$PSVersionTableand$PSHOMEagain. A shell that was already open may not reflect the newly installed runtime or environment changes. - Test before switching workloads. Validate scripts, modules, remoting, scheduled tasks, services, and automation accounts under the target executable before changing production launch commands.
PowerShell 7 does not replace Windows PowerShell 5.1. Keep 5.1 available when a script or module requires it, and avoid changing a task’s executable from powershell.exe to pwsh.exe solely because the latter is newer. Confirm behavior in the context and account that will actually run the workload.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteRank #4
- Server 2025 will be delivered by post, FPP version
- Enterprise Security – Built-in advanced security features including Hotpatching for seamless updates and Credential Guard to protect against unauthorized access.
- Hybrid Cloud Integration – Connects seamlessly with cloud-based services for efficient management of on-premise and cloud infrastructure
- Optimized Performance – Enhanced networking and storage capabilities with improved data handling and support for high-performance workloads
- User-Friendly Interface – A modernized desktop experience with streamlined management tools such as WinGet and Terminal.
Modules and remoting need explicit validation
Compatibility is not guaranteed by installing a new engine. Test the modules and commands the workload depends on, including the versions and import behavior used by its execution account. PowerShell 7 can use the existing Microsoft.PowerShell remoting endpoint. If you need a PowerShell 7-specific remoting endpoint, Microsoft’s migration guidance calls for Enable-PSRemoting. Validate endpoint configuration and authentication in your environment rather than assuming that installing PowerShell 7 automatically changes remoting behavior.
Troubleshoot common update problems
$PSVersionTable still shows 5.1
You are likely running powershell.exe, which starts Windows PowerShell. Launch pwsh.exe to check PowerShell 7. If that command is not found, inspect whether PowerShell 7 is installed and use its installed path or repair the relevant PATH configuration.
WinGet is not recognized
First check the server release and installation experience. WinGet availability here is limited to Windows Server 2025 with Desktop Experience; it is not available on Windows Server 2022 or earlier. Use MSI or ZIP on unsupported releases.
The upgrade command reports no available upgrade
Check that the package is installed through the expected source and that the command is querying the intended package. If PowerShell was installed by MSI, ZIP, MSIX, or the .NET global tool, follow that installation’s servicing route instead of assuming a WinGet upgrade will manage it. Verify the runtime actually launched by the workload as well as any interactive shell.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Best Value
- CLIENT ACCESS LICENSES (CALs) are required for every User or Device accessing Windows Server Standard or Windows Server Datacenter
- WINDOWS SERVER 2022 CALs PROVIDE ACCESS to Windows Server 2019 or any previous version.
- A USER CLIENT ACCESS LICENSE (CAL) gives users with multiple devices the right to access services on Windows Server Standard and Datacenter editions.
- GENUINE WINDOWS SERVER SOFTWARE IS BRANDED BY MICROSOFT ONLY.
A script behaves differently after migration
Run it under its previous executable to establish whether the change is tied to the engine. Then test dependencies, module imports, remoting, credentials, and the workload’s launch context under PowerShell 7. Keep the 5.1 launch path for workloads that require it; do not make a production switch until the relevant tests pass.
The installer or update appears to have succeeded, but the version looks unchanged
Open a new shell and check both the executable and $PSHOME. Multiple installations or a pre-existing process can make a successful installation appear absent. For ZIP installations, confirm that the package was replaced at the directory actually used by the workload. No universal reboot requirement is established; follow installer prompts and your server’s change procedures rather than assuming a reboot is always required or never required.
Or skip the browser setup
This PowerShell administration task does not require browser capture, but developers who also need website screenshots can make one GET request with ScreenshotNeo. Its API returns an image or PDF. The service removes cookie banners, popups and chat widgets before the shot; bot checks, blank pages and failed loads are never billed; an MCP server lets AI agents take screenshots; and 1,000 screenshots a month are free with no card, with paid plans starting at $5 for 3,000. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
