Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

12,231,415

Downloads of v 5.0.10586.20170115:

46,058

Last Update:

16 Jan 2017

Package Maintainer(s):

Software Author(s):

  • Microsoft wrote PowerShell
  • IntelliTect created the Chocolatey Package

Tags:

PowerShell admin Reboot Scripting OneGet

Windows Management Framework and PowerShell

This is not the latest version of Windows Management Framework and PowerShell available.

  • 1
  • 2
  • 3

5.0.10586.20170115 | Updated: 16 Jan 2017

Downloads:

12,231,415

Downloads of v 5.0.10586.20170115:

46,058

Software Author(s):

  • Microsoft wrote PowerShell
  • IntelliTect created the Chocolatey Package

Windows Management Framework and PowerShell 5.0.10586.20170115

This is not the latest version of Windows Management Framework and PowerShell available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Windows Management Framework and PowerShell, run the following command from the command line or from PowerShell:

>

To upgrade Windows Management Framework and PowerShell, run the following command from the command line or from PowerShell:

>

To uninstall Windows Management Framework and PowerShell, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade powershell -y --source="'INTERNAL REPO URL'" --version="'5.0.10586.20170115'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade powershell -y --source="'INTERNAL REPO URL'" --version="'5.0.10586.20170115'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install powershell
  win_chocolatey:
    name: powershell
    version: '5.0.10586.20170115'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'powershell' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '5.0.10586.20170115'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller powershell
{
    Name     = "powershell"
    Version  = "5.0.10586.20170115"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'powershell':
  ensure   => '5.0.10586.20170115',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 16 Jan 2017.

Description

Windows Management Framework 5.0 includes updates to Windows PowerShell, Windows PowerShell ISE, Windows PowerShell Web Services (Management OData IIS Extension), Windows Remote Management (WinRM), Windows Management Instrumentation (WMI), the Server Manager WMI provider, and a new feature for 4.0, Windows PowerShell Desired State Configuration (DSC).
Windows Management Framework 5.0 includes updates to Windows PowerShell, Windows PowerShell Desired State Configuration (DSC), and Windows PowerShell ISE. It also includes OneGet, PowerShellGet, and Network Switch cmdlets

IMPORTANT NOTES for your Operating System:

PowerShell 4 and later requires at least .NET 3.5.1.
This package will warn you and exit if it is not installed.
It is not automatically installed as a dependency so that you
maintain complete control over the .NET version in your build.

Windows 8.1, Windows 2012R2: Installs PowerShell 5.0.
Windows 8: PowerShell 4.0 not supported. PowerShell 3.0 installed by default
Windows 7 SP1, Windows 2008 R2 SP1, or Windows 2012: PowerShell 5.0 installed (as of 5.0.10105 April 2015 Preview)
ATTENTION: Windows 7 and Server 2008 R2 Required WMF/PowerShell 4.0 to be installed first.
This package will install 4 if it is not installed and instruct you to re-run the package using -Force
Or you can just install WMF 4 first if you have this already setup in build automation.
This is a temporary restriction that Microsoft is working on removing for the final release.
Windows Vista or Windows 2008: Directs to PowerShell 3.0 install
WARNING: DO NOT INSTALL ON SCCM SERVERS.
Tested On: Windows 7, Windows 8.1, Windows 2008 R2, Windows 2012, Windows 2012 R2, Windows 10


tools\ChocolateyInstall.ps1
<#
See http://technet.microsoft.com/en-us/library/hh847769.aspx and http://technet.microsoft.com/en-us/library/hh847837.aspx
Windows PowerShell 5.0 runs on the following versions of Windows.
	Windows 10, installed by default
	Windows Server 2012 R2, install Windows Management Framework 5.0 to run Windows PowerShell 5.0
	Windows 8.1, install Windows Management Framework 5.0 to run Windows PowerShell 5.0
	Windows 7 with Service Pack 1, install Windows Management Framework 4.0 and THEN WMF 5.0 (as of 5.0.10105)
	Windows Server 2008 R2 with Service Pack 1, install Windows Management Framework 5.0 (as of 5.0.10105)
	Previous Windows versions - 5.0 is not supported.

Windows PowerShell 4.0 runs on the following versions of Windows.
	Windows 8.1, installed by default
	Windows Server 2012 R2, installed by default
	Windows 7 with Service Pack 1, install Windows Management Framework 4.0 (http://go.microsoft.com/fwlink/?LinkId=293881) to run Windows PowerShell 4.0
	Windows Server 2008 R2 with Service Pack 1, install Windows Management Framework 4.0 (http://go.microsoft.com/fwlink/?LinkId=293881) to run Windows PowerShell 4.0

Windows PowerShell 3.0 runs on the following versions of Windows.
	Windows 8, installed by default
	Windows Server 2012, installed by default
	Windows 7 with Service Pack 1, install Windows Management Framework 3.0 to run Windows PowerShell 3.0
	Windows Server 2008 R2 with Service Pack 1, install Windows Management Framework 3.0 to run Windows PowerShell 3.0
	Windows Server 2008 with Service Pack 2, install Windows Management Framework 3.0 to run Windows PowerShell 3.0
#>

[string]$packageName="PowerShell.5.0"
[string]$installerType="msu"
[string]$ThisPackagePSHVersion = '5.0.10586'
[string]$silentArgs="/quiet /norestart /log:`"$env:TEMP\PowerShell.Install.evtx`""

[string]$urlWin81x86   =                 'https://download.microsoft.com/download/2/C/6/2C6E1B4A-EBE5-48A6-B225-2D2058A9CEFB/Win8.1-KB3134758-x86.msu'
[string]$urlWin81x86checksum   =         'F9EE4BF2D826827BC56CD58FABD0529CB4B49082B2740F212851CC0CC4ACBA06'
[string]$urlWin2k12R2andWin81x64 =       'https://download.microsoft.com/download/2/C/6/2C6E1B4A-EBE5-48A6-B225-2D2058A9CEFB/Win8.1AndW2K12R2-KB3134758-x64.msu'
[string]$urlWin2k12R2andWin81x64checksum = 'BB6AF4547545B5D10D8EF239F47D59DE76DAFF06F05D0ED08C73EFF30B213BF2'
[string]$urlWin7x86   =                  'https://download.microsoft.com/download/2/C/6/2C6E1B4A-EBE5-48A6-B225-2D2058A9CEFB/Win7-KB3134760-x86.msu'
[string]$urlWin7x86checksum   =          '0486901B4FD9C41A70644E3A427FE06DD23765F1AD8B45C14BE3321203695464'
[string]$urlWin2k8R2andWin7x64 =         'https://download.microsoft.com/download/2/C/6/2C6E1B4A-EBE5-48A6-B225-2D2058A9CEFB/Win7AndW2K8R2-KB3134760-x64.msu'
[string]$urlWin2k8R2andWin7x64checksum = '077E864CC83739AC53750C97A506E1211F637C3CD6DA320C53BB01ED1EF7A98B'
[string]$urlWin2012 =                    'https://download.microsoft.com/download/2/C/6/2C6E1B4A-EBE5-48A6-B225-2D2058A9CEFB/W2K12-KB3134759-x64.msu'
[string]$urlWin2012checksum =            '6E59CEC4BD30C505F426A319673A13C4A9AA8D8FF69FD0582BFA89F522F5FF00'
[string]$ChecksumType       =            'sha256'

[string[]] $validExitCodes = @(0, 3010) # 2359302 occurs if the package is already installed

$osversionLookup = @{
"5.1.2600" = "XP";
"5.1.3790" = "2003";
"6.0.6001" = "Vista/2008";
"6.1.7600" = "Win7/2008R2";
"6.1.7601" = "Win7 SP1/2008R2 SP1"; # SP1 or later.
"6.2.9200" = "Win8/2012";
"6.3.9600" = "Win8.1/2012R2";
"10.0.*" = "Windows 10/Server 2016"
}

function Install-PowerShell5([string]$urlx86, [string]$urlx64 = $null, [string]$checksumx86 = $null,[string]$checksumx64 = $null) {
    $Net4Version = (get-itemproperty "hklm:software\microsoft\net framework setup\ndp\v4\full" -ea silentlycontinue | Select -Expand Release -ea silentlycontinue)
    if ($Net4Version -ge 378675) {
        Install-ChocolateyPackage "$packageName" "$installerType" "$silentArgs" -url $urlx86 -url64 $urlx64 -checksum $checksumx86 -ChecksumType $ChecksumType -checksum64 $checksumx64 -ChecksumType64 $ChecksumType -validExitCodes $validExitCodes
        Write-Warning "$packageName requires a reboot to complete the installation."
        #}
    }
    else {
        throw ".NET Framework 4.5.1 or later required.  Use package named `"dotnet4.5.1`"."
    }
}

try {
  # Get-CimInstance was completely crashing on win7 psh 2 even with try / catch
  $osVersion = (Get-WmiObject Win32_OperatingSystem).Version
}
catch {
    $osVersion = (Get-WmiObject Win32_OperatingSystem).Version
}

$ProductName = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name 'ProductName').ProductName
$EditionId = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name 'EditionID').EditionId

#This will show us if we are running on Nano Server (Kernel version alone won't show this)
Write-Output "Running on: $ProductName, ($EditionId), Windows Kernel: $osVersion"

If ((get-service wuauserv).starttype -ieq 'Disabled')
{
  Throw "Windows Update Service is disabled - PowerShell updates are distributed as windows updates and so require the service.  Consider temporarily enabling it before calling this package and disabling again afterward."
}

try
{
    if ($PSVersionTable -and ($PSVersionTable.PSVersion -ge [Version]$ThisPackagePSHVersion)) {
	    Write-Warning "PowerShell version, $($PSVersionTable.PSVersion), is already installed."
	}
    elseif ($PSVersionTable -and ($PSVersionTable.PSVersion -ge [Version]'5.0') -and ($PSVersionTable.PSVersion -lt [Version]$ThisPackagePSHVersion)) {
        Write-Warning "The existing PowerShell version, $($PSVersionTable.PSVersion), must be uninstalled, before you can install version $ThisPackagePSHVersion."
    }
    else {
        #The following should not occur as PowerShell 5 is already installed
        if( ([version]$osVersion).Major -eq "10" ) {
            $osVersion = "$(([version]$osVersion).Major).$(([version]$osVersion).Minor).*"
        }

        Write-Output "Installing for OS: $($osversionLookup[$osVersion])"

		    switch ($osversionLookup[$osVersion]) {
            "Vista/2008" {
                Write-Warning "PowerShell 3 is the highest supported on Windows $($osversionLookup[$osVersion])."
                Write-Output "You can install PowerShell 3 using these parameters: 'PowerShell -version 3.0.20121027'"
            }
            "Win7/2008R2" {
                Write-Warning "PowerShell $ThisPackagePSHVersion Requires SP1 for Windows $($osversionLookup[$osVersion])."
                Write-Warning "Update to SP1 and re-run this package to install WMF/PowerShell 5"
                Write-Output "You can install PowerShell 3 using these parameters: 'PowerShell -version 3.0.20121027'"
            }
            "Win7 SP1/2008R2 SP1" {
                Install-PowerShell5 -urlx86 "$urlWin7x86" -checksumx86 $urlWin7x86checksum -urlx64 "$urlWin2k8R2andWin7x64" -checksumx64 $urlWin2k8R2andWin7x64checksum
            }
            "Win8/2012" {
                if($os.ProductType -gt 1) {
                    #Windows 2012
                    Install-PowerShell5 -urlx86 "$urlWin2012" -checksumx86 $urlWin2012checksum
                }
                else {
                    #Windows 8
                    Write-Verbose "Windows 8 (not 8.1) is not supported"
                    throw "$packageName not supported on Windows 8. You must upgrade to Windows 8.1 to install WMF/PowerShell 5.0."
                }
            }
            "Win8.1/2012R2" {
              Install-PowerShell5 -urlx86 "$urlWin81x86" -checksumx86 $urlWin81x86checksum -urlx64 "$urlWin2k12R2andWin81x64" -checksumx64 $urlWin2k12R2andWin81x64checksum
            }
            "Windows 10/Server 2016" {
                #Should never be reached.
                Write-Warning "Windows 10 / Server 2016 has WMF/PowerShell 5 pre-installed which is maintained by Windows Update."
            }
            default {
                # Windows XP, Windows 2003, Windows Vista, or unknown?
                throw "$packageName $ThisPackagePSHVersion is not supported on $ProductName, ($EditionId), Windows Kernel: $osVersion"
            }
	    }
    }
}
catch {
  Throw $_.Exception
}
tools\chocolateyUninstall.ps1
Write-Debug ("Starting " + $MyInvocation.MyCommand.Definition)

[string]$packageName="PowerShell.5.0"

<#
Exit Codes:
    3010: WSUSA executed the uninstall successfully.
    2359303: The update was not found.
#>

#5.0.10586
$osVersion = (Get-WmiObject Win32_OperatingSystem).Version
if(-not (($osVersion -ge [version]"6.4") -or ($osVersion -ge [version]"10.0"))) {
    Start-ChocolateyProcessAsAdmin "/uninstall /KB:3094174 /quiet /norestart /log:`"$env:TEMP\PowerShell.PowerShell.Uninstall.5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
    Start-ChocolateyProcessAsAdmin "/uninstall /KB:3134760 /quiet /norestart /log:`"$env:TEMP\PowerShell.PowerShell.Uninstall.5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
    Start-ChocolateyProcessAsAdmin "/uninstall /KB:3134759 /quiet /norestart /log:`"$env:TEMP\PowerShell.PowerShell.Uninstall.5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
    Start-ChocolateyProcessAsAdmin "/uninstall /KB:3134758 /quiet /norestart /log:`"$env:TEMP\PowerShell.PowerShell.Uninstall.5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
}


Write-Warning "$packageName may require a reboot to complete the uninstallation."

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Windows Management Framework and PowerShell 5.1.14409.20180105 552283 Saturday, January 6, 2018 Approved
Windows Management Framework and PowerShell 5.1.14409.20170510 986454 Thursday, May 11, 2017 Approved
Windows Management Framework and PowerShell 5.1.14409.20170402 255680 Monday, April 3, 2017 Approved
Windows Management Framework and PowerShell 5.1.14409.20170301 76666 Thursday, March 2, 2017 Approved
Windows Management Framework and PowerShell 5.1.14409.20170214 73832 Tuesday, February 14, 2017 Approved
Windows Management Framework and PowerShell 5.1.14409.1005 59989 Monday, January 30, 2017 Approved
Windows Management Framework and PowerShell 5.0.10586.20170115 46058 Monday, January 16, 2017 Approved
Windows Management Framework and PowerShell 5.0.10586.20161216 37331 Friday, December 16, 2016 Approved
Windows Management Framework and PowerShell 5.0.10586.20161201 5610 Thursday, December 8, 2016 Exempted
Windows Management Framework and PowerShell 5.0.10586.20151218 171350 Monday, April 11, 2016 Approved
Windows Management Framework and PowerShell 5.0.10514-ProductionPreview 8316 Wednesday, September 2, 2015 Exempted
Windows Management Framework and PowerShell 5.0.10105-April2015Preview 4050 Friday, May 1, 2015 Exempted
Windows Management Framework and PowerShell 5.0.10018-February2015Preview 1245 Friday, March 20, 2015 Exempted
Windows Management Framework and PowerShell 5.0.9883-November2014Preview 677 Friday, March 20, 2015 Exempted
Windows Management Framework and PowerShell 4.0.20141001 152210 Monday, October 6, 2014 Approved
Windows Management Framework and PowerShell 4.0.20140915 3920 Monday, September 29, 2014 Unknown
Windows Management Framework and PowerShell 3.0 3.0.20121027 49373 Monday, October 29, 2012 Unknown
Windows Management Framework and PowerShell 3.0 3.0.20120905 955 Thursday, September 6, 2012 Unknown
Windows Management Framework and PowerShell 3.0 3.0.20120904 2764 Wednesday, September 5, 2012 Unknown
Windows Management Framework and PowerShell 3.0 RC 3.0.20120823-Beta 764 Friday, August 24, 2012 Unknown
Windows Management Framework and PowerShell 3.0 Beta 3.0.20120627-Beta 989 Sunday, July 1, 2012 Unknown

2016.12.01 (5.0.10586.20170115)
- Fixed: Package generates error that you must upgrade to Windows 8.1 on Server 2012 (not-R2) domain controllers.

2016.12.01 (5.0.10586.20161201)
- IMPORTANT: This package no longer updates a machine to an older version of PowerShell when 5 cannot be applied, the package must
be explicitly called with the -version parameter if the system being configured cannot take PowerShell 5.
- Updated to use checksums
- Updated to use re-released MSUs discussed here (old ones getting 404s):
https://blogs.msdn.microsoft.com/powershell/2016/02/24/windows-management-framework-wmf-5-0-rtm-packages-has-been-republished/
- Checks and errors if Windows Update service is disabled, the error message suggests enabling it just for the time this package runs
(it is a common good practice to disable Windows Update when doing long running orchestration,
however, it must be enabled for this package to run)

2016.3.28:
Fixed bug with Windows Server 2012 installation

2015.12.19:
Updated for PowerShell 5.0.10586.20151218 RTM - Released 2015-12-18.

2015.09.02:
Updated for PowerShell 5.0.10514.6 (Production Preview) Released 8/31/15 (Darwin).
Checks if you already have 5.0 installed and requires previous versions of 5 to be uninstalled first.

2015.04.29:
Updated for PowerShell 5.0.10105 (April 2015 Preview) (Darwin).
Windows 7 SP1 and Server 2008 R2 SP1 NOW SUPPORTED FOR PSH 5!

2015.03.18:
Updated for PowerShell 5 (Darwin).

2014.10.01:
Changed to report success when PowerShell 4.0 is already installed.

2014.09.15:
Support added for PowerShell 4.0


This package has no dependencies.

Discussion for the Windows Management Framework and PowerShell Package

Ground Rules:

  • This discussion is only about Windows Management Framework and PowerShell and the Windows Management Framework and PowerShell package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Windows Management Framework and PowerShell, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus