How do I check which PowerShell version I’m using?

PowerShell is an awesome tool created by Microsoft that is used for automating tasks. It was launched by Microsoft in 2006 as an alternative to Command Prompt so that users could automate batch tasks which can often be monotonous and repetitive, maintaining IT efficiency in your organization. 

You can use PowerShell for automation, to help save you time in the long run. There are over 200 cmdlets, or single function commands that can be used within PowerShell, and it’s a really flexible framework that you can use to save yourself a lot of time in your workday. But there are a few questions you need to have answers to in order to maximize its use—what version of PowerShell do I have, and how can I update PowerShell? Today we’ll answer these questions and more!

Is PowerShell just for Windows OS?

If you think PowerShell is only available for Windows, then you may have been hiding under a PowerShell-proof rock since 2016. That was the year that PowerShell Core was announced as open-source and cross-platform. You can install PowerShell on macOS, (PowerShell 7.0 or higher requires macOS 11 and higher), and Linux, too. While Windows PowerShell is native to Windows OS, and Microsoft only supports security updates and bug fixes – the future is firmly with PowerShell Core.

Why do I need to know which PowerShell version I’m using?

There have been many PowerShell versions since the first release back in 2006. The first release was PowerShell 1.0, suitable for Windows XP and Vista, and for Microsoft Server 2003… oh boy, those were the days!. Since then, the framework has cycled through 2.0, 3.0, 4.0, and 5.0, before 5.1 was released in January 2017, which is currently the last version that comes previously installed on Microsoft computers. 

Through 2018 and 2019, PowerShell Core 6.0, 6.1, and 6.2 were released. Then more recently, PowerShell released the 7-series versions of PowerShell, from 7.0 to 7.4, with the latter being released in November 2023.

New features in PowerShell 7 included:

• Parallel processing with the Parallel switch for the ForEach-Object cmdlet.
• A new error-view and the Get-Error cmdlet
• Compatibility with native Windows modules
• Ternary operation with the ?: operator and null coalescing with the ?? operator

In Version 7.4, Microsoft made updates to the Windows MSI package, allowing users to disable telemetry during installation, and improvements to modules like PSResourceGet and PSReadLine. 

They’ve also improved tab completion with better type inference and performance. With PowerShell 7.4, web cmdlets can tackle decompression (including Brotli) better, and improvements have been made to progress bar rendering, HTTP persistent connections, and status code and redirection management.Because not all PowerShell versions are the same, many people need help to check which PowerShell version they are using. And that’s why we’ve put together this guide to help you determine the PowerShell version you have, in case you’ve got some automation to do via PowerShell.

Within PowerShell itself

First, use your search bar to look for the PowerShell application. Simply type in Windows PowerShell, and click on the app. You can also use a Run command, by clicking the Windows key + R and then searching for PowerShell.

A window will open, where you enter the command “$PSVersionTable”, and hit the Enter key. Below you can see the PowerShell version included in the list of information. 

More commands that will provide your PowerShell version

There are two additional commands which you can use from within PowerShell to see which version you are running. These are:

“get-host|Select-Object”

If using get-host, make sure you’re checking the PowerShell version on a local computer. If you attempt to use get-host via remote access, you’ll see the PowerShell version of the host environment.

And finally, by using “$host.version.” This option will show you your PowerShell version in a slightly different format, explaining the major and minor releases and the build number and revision, each separated instead of one long number with decimal points.

Each of these commands will, hopefully, help you to arrive at the same conclusion. But, if for whatever reason you’re doubting what you find from one of the commands, you can always use the other 2 to confirm you did find your PowerShell version. 

Using the registry to obtain my PowerShell version

In some cases, you might not want to (or be able to) use PowerShell itself to find out which version you are using. In that case, you can use the Windows Registry. First, use your search bar to open up the “Registry Editor”. You may be prompted as to whether you want to allow the editor to make changes to your machine, only permit access if you’re confident in your technical abilities.

In the left-hand toolbar, there are a number of options. You want to look under Software, which is found under HKEY-LOCAL-MACHINE, or HKLM.

Next, look for Microsoft under the names of software vendors, scroll down to PowerShell, and choose the option that says 3. Then click on PowerShell Engine. You’ll get a list of information which includes the version number, as seen in the screenshot below.

Can I check my PowerShell version from remote computers?

Yes! There is a specific cmdlet that PowerShell allows you to check which PowerShell version is installed on computers that you control remotely. Use the Invoke-Command snippet, which you edit from the following template:

Invoke-Command -ComputerName comp1 -ScriptBlock {$PSVersionTable.PSVersion} -Credential $cred

Just make sure to edit the computer name where we’ve written “comp1”, and the credentials under $cred.

By separating out the values with commas, you can check multiple remote remote computers at the same time, saving you valuable time and effort.

Which versions of PowerShell come preinstalled with Windows OS?

It can be helpful to see which versions of PowerShell should have come pre-installed as standard with your Windows OS. This table is a useful guide.

How do I upgrade to a newer version of PowerShell?

You can run Windows PowerShell and Powershell 7+ on the same computer, so if you’re worried about the lack of feature compatibility of upgrading – you can simply keep Windows PowerShell installed and also download PowerShell. 

Unfortunately, PowerShell 7 and later isn’t guaranteed to be backwards-compatible with all previous scripts as they are no longer Windows-native, so you’ll need to test all of your scripts before moving over totally to PowerShell 7+. Certain modules will also need to be adapted.If you want to download PowerShell 7+, it will replace PowerShell Core, but they can run side by side together. There are a few ways to do this. One option is to run a script directly from inside PowerShell. You’ll just need to paste this cmdlet snippet into the PowerShell window, and press Enter.

iex “& { $(irm https://aka.ms/install-powershell.ps1) } -UseMSI”

You’ll be prompted to go through the PowerShell wizard and choose the settings and options you want enabled or disabled.

Another way to download PowerShell is to go to its GitHub release page. The most recent update at the time of writing is Version 7.4.2. Scroll down, and you’ll see a list of assets, where you can simply choose the OS you want to download.

The power of Atera’s RMM software

Atera can play a crucial role in helping users determine their PowerShell version through its robust IT management capabilities. By using Atera’s RMM tool, IT professionals can remotely access and query the PowerShell version on all connected devices within their network. 

Atera provides real-time insights and reporting, making it easy to identify which PowerShell version is in use. Additionally, it offers the ability to update or standardize PowerShell versions across multiple devices, ensuring consistent and efficient management of this essential tool. With Atera’s support, checking PowerShell versions becomes a simple, hassle-free process.So don’t delay, get in touch with our sales team today about how you can transform the way you manage your business’ IT operations.