Notices: This section not yet converted to new layout. Download stats are rolling back out.

631,845

Downloads

61,479

Downloads of v 5.1.14409.20170214

2/14/2017

Last update

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

Windows Management Framework and PowerShell

5.1.14409.20170214

Package test results are passing.

This package was approved as a trusted package on 2/14/2017.

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 Product Incompatibility Notes: https://msdn.microsoft.com/en-us/powershell/wmf/5.0/productincompat

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

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

C:\> choco install powershell -version 5.1.14409.20170214

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

C:\> choco upgrade powershell -version 5.1.14409.20170214

Files

Hide
  • tools\ChocolateyInstall.ps1 Show
    <#
    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"
    [string]$installerType="msu"
    [string]$ThisPackagePSHVersion = '5.1.14409.1005'
    [string]$silentArgs="/quiet /norestart /log:`"$env:TEMP\PowerShell.Install.evtx`""
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    
    [string]$urlWin81x86   =                 'https://download.microsoft.com/download/6/F/5/6F5FF66C-6775-42B0-86C4-47D41F2DA187/Win8.1-KB3191564-x86.msu'
    [string]$urlWin81x86checksum   =         'F3430A90BE556A77A30BAB3AC36DC9B92A43055D5FCC5869DA3BFDA116DBD817'
    [string]$urlWin2k12R2andWin81x64 =       'https://download.microsoft.com/download/6/F/5/6F5FF66C-6775-42B0-86C4-47D41F2DA187/Win8.1AndW2K12R2-KB3191564-x64.msu'
    [string]$urlWin2k12R2andWin81x64checksum = 'A8D788FA31B02A999CC676FB546FC782E86C2A0ACD837976122A1891CEEE42C0'
    [string]$urlWin7x86   =                  'https://download.microsoft.com/download/6/F/5/6F5FF66C-6775-42B0-86C4-47D41F2DA187/Win7-KB3191566-x86.zip'
    [string]$urlWin7x86checksum   =          'EB7E2C4CE2C6CB24206474A6CB8610D9F4BD3A9301F1CD8963B4FF64E529F563'
    [string]$urlWin2k8R2andWin7x64 =         'https://download.microsoft.com/download/6/F/5/6F5FF66C-6775-42B0-86C4-47D41F2DA187/Win7AndW2K8R2-KB3191566-x64.zip'
    [string]$urlWin2k8R2andWin7x64checksum = 'F383C34AA65332662A17D95409A2DDEDADCEDA74427E35D05024CD0A6A2FA647'
    [string]$urlWin2012 =                    'https://download.microsoft.com/download/6/F/5/6F5FF66C-6775-42B0-86C4-47D41F2DA187/W2K12-KB3191565-x64.msu'
    [string]$urlWin2012checksum =            '4A1385642C1F08E3BE7BC70F4A9D74954E239317F50D1A7F60AA444D759D4F49'
    [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`"."
        }
    }
    
    $os = Get-WmiObject Win32_OperatingSystem
    $osVersion = $os.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."
    	}
        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" {
                    #Special Procedures for WMF 5.1
                    $Net4Version = (get-itemproperty "hklm:software\microsoft\net framework setup\ndp\v4\full" -ea silentlycontinue | Select -Expand Release -ea silentlycontinue)
                    if ($Net4Version -lt 378758)
                    {
                      throw ".NET Framework 4.5.1 or later required.  Use package named `"dotnet4.5.1`"."
                    }
                    Else
                    {
                      If ($PSVersionTable.PSVersion.Major -eq 3)
                      {
                        Write-Warning "Found WMF 3 On Win 7 or Server 2008 R2"
                        If (!(test-path env:ChocolateyForce))
                        {
                            Throw "This package will not install WMF 5.1 over 3.0 on Windows 7 or Server 2008 R2 Unless you use the -Force switch on the package command line."
                        }
                        Else
                        {
                            Write-Host " " 
                            Write-Host "  ***********************************************************************************************"
                            Write-Host "  *  This machine is running Windows or Server 2008 R2 with WMF 3 installed and                 *"
                            Write-Host "  *  -Force was used, Experimental PSModulePath Backup and Attempted Restore Will Be Performed  *"
                            Write-Host "  *     What will be done:                                                                      *"
                            Write-Host "  *       1) The custom parts of the PSModulePath backed up to BackupPSModulePath               *"
                            Write-Host "  *       2) A fix up script that appends those values to the PSModulePath is written to:       *"
                            Write-Host "  *             %WINDIR%\Temp\psmodulepathfixup.ps1                                             *"
                            Write-Host "  *       3) A scheduled task is setup for the next reboot that runs the fix up script          *"
                            Write-Host "  *                                                                                             *"
                            Write-Host "  *   If you find that #3 does not work correctly, then you can use #1 or #2 with some of your  *"
                            Write-Host "  *   own automation to recover from the situation                                              *"
                            Write-Host "  ***********************************************************************************************"
                            Write-Host " " 
                            
                            $StandardPathsToFilterOut = @('%ProgramFiles%\WindowsPowerShell\Modules','%SystemRoot%\System32\WindowsPowerShell\v1.0\Modules','%SystemRoot%\System32\WindowsPowerShell\v1.0\Modules\')
                            [string[]]$currentpsmodulepath = (get-Item 'hklm:system\CurrentControlSet\Control\Session Manager\Environment').GetValue("PsModulePath","Default",[Microsoft.WIN32.RegistryValueOptions]::DoNotExpandEnvironmentNames).split(';')
                            $FilteredList = ($CurrentPSModulePath | Where {$StandardPathsToFilterOut -inotcontains $_}) -join ';'
                            Write-host "PSModulePath contains the following values that are not in the PSH 5 default values: $FilteredList, backing them up to BackupPSModulePath Environment Variable"
                            If ($FilteredList) {New-Itemproperty 'hklm:system\CurrentControlSet\Control\Session Manager\Environment' -name 'BackupPsModulePath' -PropertyType 'ExpandString' -value "$FilteredList" | out-null}
                            $WMF5Over3WasForced = $True
                        }
                      }
                      Install-ChocolateyZipPackage -PackageName "$packagename" -unziplocation "$toolsdir" -url "$urlWin7x86" -checksum "$urlWin7x86checksum" -checksumtype "$ChecksumType" -url64bit "$urlWin2k8R2andWin7x64" -checksum64 "$urlWin2k8R2andWin7x64checksum" -checksumtype64 "$ChecksumType"
                      $x64MSUName = "$toolsdir\$(($urlWin2k8R2andWin7x64.split('/') | select -last 1).replace('.zip','.msu'))"
                      $x86MSUName = "$toolsdir\$(($urlwin7x86.split('/') | select -last 1).replace('.zip','.msu'))"
                      Write-Host "64-bit file: $x64MSUName"
                      Install-ChocolateyPackage "$packageName" 'MSU' "$SilentArgs" -url $x86MSUName -url64 $x64MSUName -validExitCodes $validExitCodes
                      If ($WMF5Over3WasForced)
                      {
                        If (!$FilteredList)
                        {
                            Write-Host "PSModulePath does not contain any customized paths that need to be preserved."
                        }
                        Else
                        {
                            $scriptlocation = "$env:windir\temp\psmodulepathfixup.ps1"
    
                            $code = "set-Itemproperty 'hklm:system\CurrentControlSet\Control\Session Manager\Environment' -name 'PsModulePath' -value `$((get-Item 'hklm:system\CurrentControlSet\Control\Session Manager\Environment').GetValue('PsModulePath','Default',[Microsoft.WIN32.RegistryValueOptions]::DoNotExpandEnvironmentNames)" + "+`';$(invoke-expression -command '(get-variable FilteredList).value')`'" + ')'
                            $code | out-file $scriptlocation
                            "start-sleep -s 2" | out-file $scriptlocation -append
                            "schtasks.exe /delete /f /tn `"PSModulePathFixUp`"" | out-file $scriptlocation -append
    
                            schtasks.exe /create /tn "PSModulePathFixUp" /ru SYSTEM /Sc ONSTART /tr "powershell.exe -file $scriptlocation"
    
                            Write-Host "`"$scriptlocation`" is scheduled to run on reboot."
    
                            Write-Warning "ATTENTION: This Computer Must Be Restarted."
                        }
                      }
                    }
                }
                "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 Updates."
                }
                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 Show
    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:3191566 /quiet /norestart /log:`"$env:TEMP\PowerShellUninstall5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
        Start-ChocolateyProcessAsAdmin "/uninstall /KB:3191565 /quiet /norestart /log:`"$env:TEMP\PowerShellUninstall5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
        Start-ChocolateyProcessAsAdmin "/uninstall /KB:3191564 /quiet /norestart /log:`"$env:TEMP\PowerShellUninstall5.evtx`"" -exeToRun "WUSA.exe" -validExitCodes @(3010,2359303)
    }
    
    
    Write-Warning "$packageName may require a reboot to complete the uninstallation."
    

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Maintainer(s)

Software Author(s)

  • Microsoft wrote PowerShell
  • IntelliTect created the Chocolatey Package

Copyright

2013 Microsoft Corporation

Tags

Release Notes

WMF 5.1 Release Notes: https://msdn.microsoft.com/en-us/powershell/wmf/5.1/release-notes

2017.02.14
WMF Version: 5.1.14409.1005
Pkg Version: 5.1.14409.20170214
- fixed bug causing Server 2012 (non-R2) from being detected as windows 8

2017.01.26 (5.1.14409.1005)
- New: Installs WMF 5.1
- Tested On: Win7 + PSH 2, Win7 + WMF 3, Win 8.1 + WMF 4, 2012 R2 + WMF 5.0, Windows 10
- EXPERIMENTAL: Attempts to Preserve the PSModulePath when WMF 5.1 is
installed over WMF 3 on Windows 7 or Server 2008.

How it the experimental support works:
*) It only takes effect on Windows 7 and Server 2008 R2 and only if WMF 3 is installed
*) You must pre-install at least .NET 4.5.1 (required by WMF 4 and later)
*) You must use the -force switch on the package

What steps are taken to preserve PSModulePath:
1) The custom parts of the PSModulePath backed up to BackupPSModulePath
2) A fix up script that appends those values to the PSModulePath is written to:
%WINDIR%\Temp\psmodulepathfixup.ps1
3) A scheduled task is setup for the next reboot that runs the fix up script

If you find that #3 does not work correctly, then you can use #1 or #2 with some of your
own automation to recover from the PsModulePath overwrite.

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

Version History

Version Downloads Last updated Status
Windows Management Framework and PowerShell 5.1.14409.20170301 75245 Thursday, March 2, 2017 approved
Windows Management Framework and PowerShell 5.1.14409.20170214 61479 Tuesday, February 14, 2017 approved
Windows Management Framework and PowerShell 5.1.14409.1005 26877 Monday, January 30, 2017 approved
Windows Management Framework and PowerShell 5.0.10586.20170115 28312 Monday, January 16, 2017 approved
Windows Management Framework and PowerShell 5.0.10586.20161216 36615 Friday, December 16, 2016 approved
Windows Management Framework and PowerShell 5.0.10586.20161201 5073 Thursday, December 8, 2016 exempted
Windows Management Framework and PowerShell 5.0.10586.20151218 161850 Monday, April 11, 2016 approved
Windows Management Framework and PowerShell 5.0.10514-ProductionPreview 7210 Wednesday, September 2, 2015 exempted
Windows Management Framework and PowerShell 5.0.10105-April2015Preview 3449 Friday, May 1, 2015 exempted
Show More

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