Home > Articles > Programming > Windows Programming

Understanding the Windows PowerShell Release Cycle

Timothy Warner, author of Sams Teach Yourself Windows PowerShell 5 in 24 Hours, explains how Windows PowerShell releases are related to Windows version releases and which bits go with what. It's not a 1:1 relationship, so you might need to uninstall if things don't go quite as expected. With Tim's help and the Windows Management Framework, you'll get it right from the start.
Like this article? We recommend

One common question I receive from my students: "Does Windows PowerShell have a release cycle?" Answering this question involves some muddiness; I typically respond, "Yes and no." By the time you finish reading this article, I want you to understand the issues:

  • Which Windows versions are compatible with which PowerShell versions
  • How PowerShell is timed to Windows operating system releases
  • How you can update your PowerShell bits by using the Windows Management Framework (WMF)

Let's begin!

Untangling the Relationship Between Windows and PowerShell

We'll start by studying a table that I included in my book Sams Teach Yourself Windows PowerShell 5 in 24 Hours.

Windows PowerShell Version History in a Nutshell

Windows PowerShell Version

Release Date

Associated Operating Systems

Can Upgrade From

Standout Features

Available via WMF?



Windows Server 2003, Windows Server 2008, Windows XP SP2, Windows Vista


Initial release




Windows Server 2008 R2, Windows 7


Remoting, jobs, modules




Windows Server 2012, Windows 8

Windows Server 2008 R2, Windows 7

Updatable help, code completion, snippets, resumable sessions




Windows Server 2012 R2, Windows 8.1

Windows Server 2008 R2, Windows 7

Desired State Configuration, exportable help, network diagnostics


5.0 (Preview)


N/A (Public preview as of this writing)


OneGet, PowerShellGet, switch management improvements, classes


The table includes some important takeaways for us:

  • Computers running Windows Server 2008 R2 or Windows 7 can upgrade to PowerShell v4, but not PowerShell v5.
  • You can update your PowerShell version by using WMF, starting with PowerShell v3.
  • The PowerShell team appears to ship a new PowerShell version with each major Windows OS release.

To make the point boldly, we can make the first of two general conclusions:

We can expect to see a new PowerShell version whenever the Windows teams release a major version of Windows Server and Windows client.

Cool. But you may wonder what the Windows Management Framework is. We'll address that issue right away, but first I want to say just a couple of words about the .NET Framework.

Windows PowerShell and the .NET Framework

Many IT professionals are confused about what the .NET Framework is. Briefly, the .NET Framework is a runtime environment for Windows applications, including the base operating system. What's cool about the .NET Framework is that its application programming interface (API) has hooks that allow us to access all aspects of local and remote computers: processor, memory, disk, network—you name it.

Windows PowerShell is essentially an IT pro-friendly way to interact with the powerful .NET Framework. Moreover, Windows PowerShell versions are tied to particular .NET Framework versions. Here's the summary for Windows PowerShell versions from v3 to v5 preview:

  • Windows PowerShell v3: .NET Framework v4.0
  • Windows PowerShell v4: .NET Framework v4.5
  • Windows PowerShell v5: .NET Framework v4.5

The good news is twofold:

  • As long as you're using Microsoft Update, Windows will automatically provide you with new .NET Framework versions as Microsoft releases them.
  • You can (and probably do) have multiple .NET Framework versions installed simultaneously on your Windows computers.

Understanding the WMF

If you've ever heard PowerShell inventor Jeffrey Snover speak, you can tell right away how enthused he is about the language. Microsoft's core PowerShell team is so excited about the technology, in fact, that they want Windows systems administrators always to have a) previous major releases available for upgrade; and b) the latest preview bits available for our experimentation.

Enter the Windows Management Framework (WMF). The WMF is a bundle that includes the PowerShell runtime environment and associated assets. For example, to upgrade PowerShell on a Windows 7 workstation to version 4.0, you simply visit the Microsoft Download Center, download the update package, install, reboot, and you're done.

Examining WMF Components

Let's investigate the WMF 3.0 components:

  • PowerShell v3 runtime environment: The PowerShell "engine."
  • Windows Management Instrumentation (WMI): Expands how PowerShell interacts with your computer's WMI systems-management repository.
  • OData IIS Extension: Allows PowerShell to participate in RESTful Web services.
  • Server Manager CIM Provider: Supports PowerShell remoting.

Sometimes WMF includes a new version of the Windows PowerShell Integrated Scripting Environment (ISE); the specific parts and pieces of a WMF release depend upon the features included in that release.

Upgrading Your PowerShell Version

The PowerShell team writes the environment to be backwardly compatible with previous versions as much as possible. For instance, let's say you update a Windows 7 machine (which ships with PowerShell v2) to PowerShell v4. Let's check the version from an elevated PowerShell console session:

PS C:\> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
4      0      -1     -1

Okay. Now we'll type cmd to exit PowerShell and start an "old school" Cmd.exe session. We use the -version 2.0 switch to start a legacy PowerShell session, like so:

C:\>powershell –version 2.0

To finish with a flourish, we'll recheck the PSVersion property in the same session:

PS C:\> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
2      0      -1     -1

Pretty cool, isn't it? The ability to start a v2.0 session might be just what you need for compatibility with old-but-good scripts. Remember that when you're running a legacy PowerShell session, you won't have access to commands present in later releases. Check this out:

PS C:\> Update-Help
Update-Help : The term 'Update-Help' is not recognized as the name of a cmdlet,
 function, script file, or operable program. Check the spelling of the name, or
 if a path was included, verify that the path is correct and try again.


Installing WMF

Once you've performed your due diligence and determined that you do indeed want to update the PowerShell version on your Windows server or client computer, first you need to download the correct WMF version from the Microsoft Download Center. Here are some helpful links:

In this example, I'm going to download the latest WMF v5.0 preview bits to test on my Windows 8.1 computer. The first (minor) hurdle to overcome is figuring out which Microsoft Update .msu package applies to your computer. Take a look at Figure 1 to see what I mean.

Figure 1 Be sure to download the correct WMF installer.

Each .msu package is associated with a Microsoft Knowledge Base (KB) identifier and an architecture specifier (x64 for 64-bit hardware, x86 for 32-bit). The Windows 8-RT package is aimed at Windows RT-based tablets, so in all likelihood we want the x64 .msu. (The "Windows Blue" moniker refers to Microsoft's internal code name for Windows 10 and Windows Server vNext.)

The actual WMF installation process is uninteresting, as you can see in Figure 2. Be aware that you'll need to restart your computer in order for the PowerShell update to go into effect.

Figure 2 Installing a new PowerShell version is an uneventful process in most cases.

Believe me, you'll know right away if you try to install a WMF version that isn't compatible with your operating system. Glance at Figure 3 for evidence.

Figure 3 This is what happened when I tried to install WMF 5.0 on a Windows 7 computer.

Uninstalling PowerShell

The classic answer to the question "How can I uninstall PowerShell?" is another question: "Why would you want to do that?" Frankly, the only reason I can see for wanting to uninstall PowerShell is a situation in which I updated PowerShell and found that the new version conflicted with software I have running on that box.

In this example, I'll remove WMF 4.0 from my Windows 7 computer using (wait for it) PowerShell and Cmd.exe. First, let's look up the WMF 4.0 hotfix by referencing its KB identifier:

PS C:\> Get-HotFix -Id KB2819745

Source        Description      HotFixID      InstalledBy          InstalledOn
------        -----------      --------      -----------          -----------
TIMPC1HMIM    Update           KB2819745     timpc1hmim\Tim       9/30/2014 ...

Next, let's invoke Cmd.exe and the Windows Update Standalone Uninstaller (wusa.exe) to perform the WMF uninstall:

PS C:\> cmd /c wusa.exe /uninstall /KB:2819745 /quiet /norestart

After a reboot, my Windows 7 box is back to Windows PowerShell v2.0:

PS C:\> $PSVersionTable.psversion

Major  Minor  Build  Revision
-----  -----  -----  --------
2      0      -1     -1


So what do you think? Are you wondering when Microsoft will release the next version of Windows, so we can get a final version of PowerShell v5? Well, from the looks of it, PowerShell v5 will be in preview mode for a long time—Microsoft delayed Windows Server vNext until 2016, and Windows 10 isn't expected to ship until (very) late 2015.

In any event, you now understand the Windows PowerShell release cycle. I'll leave you with my two key tips to keep safe in your conceptual "shirt pocket" regarding PowerShell versions:

  • Only use GA PowerShell on production computers.
  • Feel free to experiment with the latest WMF bits on test computers.
  • Microsoft times PowerShell GA releases with Windows OS releases.

I'll see you next month. Until then, more power to the shell!

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020