After about two months of Microsoft PowerShell developers working around the clock (probably), the bug that wound up causing the WMF 5.0 RTM installer to be pulled is now fixed. There was an issue with the original release dealing with PSModulePath ($Env:PSModulePath) which was reset to default after installation of the original PowerShell v5 installer.
The Windows Management Framework (WMF) 5.0 RTM packages for Windows 2008 R2 SP1/2012 R2/2012 and Windows 7 SP1/8.1 are available for download in the Microsoft Download Center.
As I’ve stated before, due to the security enhancements including logging, updating to PowerShell v5 is highly recommended. More details on the advantages of enabling PowerShell logging and attack detection, including PowerShell v5 security enhancements are in two posts:
Download PowerShell version 5 aka “Windows Management Framework (WMF) 5.0 RTM”
Microsoft’s PowerShell blog post on the updated PowerShell v5 download:
Today, we have republished the Windows Management Framework (WMF) 5.0 RTM packages for Windows Server 2012 R2, Windows Server 2012, Windows 2008 R2 SP1, Windows 8.1, and Windows 7 SP1 to Microsoft Download Center. These packages replace previously released WMF 5.0 RTM packages and WMF 5.0 Production Preview packages.
Important Note: For systems running Windows 7 SP1 or Windows Server 2008 R2 SP1, you’ll need WMF 4.0 and .NET Framework 4.5 or higher installed to run WMF 5.0.
We want to extend our sincere thanks to the PowerShell Community for your continued patience and support while we were addressing the PSModulePath issue found in the previously released WMF 5.0 RTM packages.
To learn about the new features and improvements in WMF 5.0 RTM, please refer to (and contribute to) the WMF 5.0 release notes.
Please continue to provide feedback via our new UserVoice site.
Instructions specific to Windows 7 SP1 and Windows Server 2008 R2 SP1
- Ensure following prerequisites have been met:
- Latest service pack is installed.
- WMF 4.0 is installed.
- Microsoft .NET Framework 4.5 or above is installed.
- WinRM Dependency:
- Windows PowerShell Desired State Configuration (DSC) depends on WinRM. WinRM is not enabled by default on Windows 7 and Windows Server 2008 R2. To enable WinRM, in a Windows PowerShell elevated session, run Set-WSManQuickConfig.
Changes in the republished packages
- The KB numbers of these packages (KB3134758, KB3134759, and KB3134760) are different than previously released WMF 5.0 RTM packages (KB3094174, KB3094175, and KB3094176).
- These packages have fixes only for the PSModulePath issue compared to the previously released WMF 5.0 RTM packages.
Uninstall previously released WMF 5.0 RTM packages
You must uninstall previously released WMF 5.0 RTM (KB3094174, KB3094175, and KB3094176) packages.
No impact to Windows 10 and Windows Server 2016 Technical Preview builds
Windows 10 and Windows Server 2016 Technical Previews builds are not impacted by the above mentioned PSModulePath issue. This issue was only impacting down-level systems where WMF 5.0 RTM can be installed.