Updated 02/24/2016 – 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’s Download Center.
Updated 02/08/2016 – Thank you for your continued patience. We have fixed the offending PSModulePath issue and tested it thoroughly. We are working towards getting properly signed WMF 5.0 RTM builds. Now, we expect that around end of February you will be able to download the revised packages.
Updated 01/20/2016 – Thank you for patiently waiting for the release of WMF 5.0 RTM. We understand there’s a high demand for the release of WMF 5.0 RTM and we are actively working on fixing the PSModulePath issue to ensure that our revised release has a seamless installation experience. Unfortunately, the fix has been more complex than we initially expected. We expect that in couple of weeks (around end of Jan to early Feb) you will be able to download the revised WMF 5.0 RTM packages.
Updated 01/06/2016 – To clarify, this only affects users who install PowerShell 5.0 using the WMF installer. Anyone who has or plans on upgrading PowerShell 5.0 in Windows 10 via Windows Update (specifically the Windows 10 1511 Update) is not affected.
We recently released Windows Management Framework (WMF) 5.0 RTM delivering many requested improvements and fixes, via the Microsoft Download Center as announced in a previous blog post. However, we have discovered a bug which resets the PowerShell module environment during installation. As this issue can have a serious impact on our customers, we are taking the action to stop delivery of WMF 5.0 RTM, and have removed the packages from the Download Center. Additionally, we will be unpublishing Azure DSC Extension Handler versions 2.11 and 2.12 as they automatically install WMF 5.0 RTM.
We will deliver a revised WMF package as soon as the issue can be isolated, corrected, and validated. This issue only impacts users that have installed WMF 5.0 RTM (KB3094174, KB3094175, KB3094176), and does not affect preview versions of WMF 5.0, including WMF 5.0 Production Preview. We will publish further updates regarding a new WMF package to this blog post.
Specifically, this bug resets the PSModulePath environment variable to default values, losing any changes made prior to the WMF 5.0 RTM installation. If you have already installed WMF 5.0 RTM, this issue has already affected you – we will provide guidance on moving forward to the new WMF packages as soon as we have validated a fix.
– Windows PowerShell Team