How to install the new preview version of the PowerShell ISE

The PowerShell team released a new preview version of the PowerShell ISE (Integrated Scripting Environment) this week. This is the first time a new version of the PowerShell ISE has been released separately from a new version of the WMF (Windows Management Framework). This new approach reminds me of how they shipped the help separately from the WMF beginning with PowerShell version 3.0.

isepBest of All, this new preview version of the ISE is a module which is distributed via the PowerShell Gallery and installing it doesn’t interfere with the current version of the ISE so there’s no chance of hosing up the development of any mission critical work that you may be working on. With that said, I would NOT recommend installing this preview version on a server because GUI’s belong on PC’s, not servers <period>.

PowerShell version 5 RTM or the WMF 5 Production Preview is required so be sure to check the PowerShell version on the machine that you plan to install the ISE preview on before getting started. If you have Windows 10, the necessary PowerShell version is already installed, otherwise you can find the production preview here. This blog article was written with and all of my testing has been performed using Windows 10 Enterprise Edition version 1511.


The Install-Module cmdlet which is part of the PowerShellGet module is used to install the ISE preview module from the PowerShell Gallery. The PowerShell Gallery is an untrusted repository so you’ll be prompted to make sure that you want to install software on your machine from an untrusted source. Be aware that although this module is written by the PowerShell team, that most of the modules on the PowerShell Gallery are written by third party’s and there are potential security issues with installing software from untrusted repositories.

The Force parameter could be used to suppress the untrusted repository message. There is also a Scope parameter if you prefer to install the module only for the current user and not in the all users path.


Note: Specifying the Scope parameter with a value of CurrentUser installs the module only for the current user who is running PowerShell which may not be the same user who is logged into Windows depending on whether or not an alternate user was specified when running PowerShell elevated.

The Install-ISEPreviewShortcut cmdlet creates shortcuts in the start menu for the ISE preview:


Note: The shortcuts are created in the user’s start menu who is running PowerShell. If an alternate user was specified when running PowerShell elevated, the shortcuts will be created in that users start menu, not the user who is currently logged into Windows. If you’re running PowerShell as an alternate user and the ISE preview module was installed for all users, the solution to this is to run PowerShell non-elevated when creating the shortcuts.

To launch the ISE preview, enter the isep alias:


One of the awesome things about shipping the ISE separately as a module is how quickly bug fixes can be released:


Updating the ISE preview is as easy as running Update-Module:


I noticed that a list of the bug fixes can be found on the about page:


For more information, see the PowerShell team blog announcement: “Introducing the Windows PowerShell ISE Preview“.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: