Your New PowerShell ISE Is Visual Studio Code
ISE Is Gone, Not Just Superseded
For years the answer to "where do I write PowerShell" was the ISE — a light editor bundled with Windows, no installation, syntax highlighting and a console panel.
It is no longer part of the picture. The ISE is built on an old WPF editor control that cannot run on PowerShell 7 or .NET Core, so it was not ported. It is still present on Windows PowerShell 5.1, but it has not received feature work in years, and Microsoft's guidance is to move to Visual Studio Code with the PowerShell extension.
On a machine where you have removed Windows PowerShell 5.1, or where you work across Windows and Linux, the ISE simply does not exist. VS Code does, on all three platforms.

What You Need
- Visual Studio Code from code.visualstudio.com — free, and available for Windows, macOS and Linux.
- The PowerShell extension by Microsoft, installed from the Extensions panel (
Ctrl+Shift+X, search "PowerShell").
That is the whole install. The extension gives you:
- IntelliSense with real cmdlet metadata, including parameter types
- A script analyser that flags common bugs as you type
- F5 to run the current script, F8 to run the selection
- An integrated terminal with a PowerShell session you can step through
- Debugging with breakpoints, stepping, variable inspection and the call stack
That last item is the one that makes the ISE feel primitive in retrospect. The ISE had no real debugger; VS Code does, and it is the reason I stopped missing it within a week.
The Settings Worth Changing First
Open settings (Ctrl+,) and set these:
Default terminal profile. If you work with PowerShell 7, set terminal.integrated.defaultProfile.windows to PowerShell so new terminals do not drop you into Windows PowerShell 5.1.
Format on save. editor.formatOnSave with the PowerShell extension's formatting gives you consistent indentation without thinking about it.
Script analysis severity. The analyser (PSScriptAnalyzer) reports style issues as warnings by default. In a one-off script, those warnings are noise; in a module, they are worth fixing. Adjust powershell.scriptAnalysis.settingsPath if you want a custom ruleset.
Line numbers and render whitespace. Small things that make a script readable a year later.
Workspaces For Script Collections
If you keep a folder of scripts — a C:\Scripts tree, or a repository of modules — open the folder rather than individual files. VS Code then indexes the whole tree, so IntelliSense resolves functions across files and Ctrl+P jumps to any script instantly.
For anything larger than a handful of files this is the difference between an editor and a tool. Save it as a workspace (.code-workspace) and it opens in one step with the right folder set.

The Cross-Platform Point
This is the part that mattered most to me: the same editor runs on Ubuntu, and the PowerShell extension works there too. That means one environment for scripting Windows machines and Linux machines, with the same keyboard shortcuts, the same snippet library and the same formatter.
The ISE could never do that, because it was Windows-only by construction. Once you are scripting both — a Pi, a Linux server, a Windows desktop — a single editor is worth more than the familiarity of the old one.

If You Genuinely Prefer Something Else
Windows Terminal plus a text editor works, and is what some people use, because the editor matters less than you think once you are comfortable in the console.
Sublime Text or Neovim with a PowerShell language server are legitimate choices if you already live in them. The important thing is having the language server, not which editor hosts it.
The ISE on 5.1 still runs if you need it, and if you maintain Windows PowerShell 5.1 scripts specifically, it is not wrong — it is just a dead end with no path forward.
The honest summary: the ISE was fine, it is over, and VS Code is the supported replacement with a debugger that makes it a genuine upgrade rather than a migration.
Don't trust the download button. Trust the hash.
If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.