You must first install PowerShell / WMF 4 before you can install PowerShell / WMF 5. This is an interim dependency that the PowerShell team is planning to eliminate for the production release. However if you try to install PowerShell 5 without 4 present, you just get a standard Windows Update WUSA error "This Update is not applicable to your system" (Error: 2149842967 or 0x80240017). PowerShell 5 installs via one of the following windows updates:KB3055381, KB3055377 or KB2908075. The below quick config also detects this situation and installs PowerShell 4 and instructs you to reboot and re-run the quick config.
NET 4.5.1 and then reinstall PowerShell 4. If you use the quick config below - this is detected for you and you are instructed to issue a chocolatey command to easily pull. NET 3.5.1 or later to install PowerShell 4. However, the PowerShell 4 installer does not block you if you don't have it. It successfully installs and then when you reboot you are still on your previous version (2 or 3). You have to uninstall the PowerShell 4 Windows Update and then install. You must have SP1. If you are using source media that does not have it slipstreamed (like the downloadable Server 2008 R2 VHD), then you'll need to apply it before getting started. Most cloud based VMs should have SP1 on Server 2008 already.Here are the challenges in getting a Windows 7 or Server 2008 R2 machine to PowerShell 5:ĭO NOT USE THIS PROCEDURE - SKIP TO THE ARTICLE CITED AT THE TOP OF THIS PAGE. Windows 7 and Server 2008 R2 are the worst case scenarios and therefore are the focus of the below, howver, all of these steps work for Server 2012, 2012 R2 and Windows 8.1 - they take fewer steps because they have more of the prerequisites. I am very excited that the PowerShell team has just delivered the April Preview that allows version 5 to run on Windows 7 SP1 and Server 2008 R2 (PowerShell version 5). For this preview version there are a few foibles to getting it running on Windows 7. The PowerShell team hopes to sort these out, but in the mean time I have put together a quick config that steps you though everything with one command line. Some additional information on the WMF 5 Production Preview is in this post: Poodles Through Burning Hoops: Plan for PowerShell 5 on Windows 7 and Server 2008. If you don't use Chocolatey (I feel sorry for you ) ), you can just steal my PowerShell code that does this piece of the puzzle. I have attempted to address this in the Chocolatey package I help maintain for the PowerShell package on. Update: WMF 5.1 now installs directly on top of WMF 3, however it can lose your PSModulePath customizations in the process.
0 kommentar(er)
