If PowerShell is missing in Windows 11, identify which one you need first: Windows PowerShell 5.1, PowerShell 7, or PowerShell ISE. Each one has a different fix. If you choose the wrong path, you can reinstall the wrong package or miss the shell your script, admin task, or shortcut still expects. This guide shows how to find, restore, or install each one, and where Windows 11 hides them.

Windows PowerShell 5.1 is included with Windows and is commonly kept for legacy compatibility. PowerShell 7 is a separate, current line that installs side by side with Windows PowerShell 5.1. PowerShell ISE is a different desktop editor again, so installing one of the newer shells does not bring back the others. (Microsoft Learn)

What missing PowerShell means on Windows 11
A Windows PowerShell window appears over a blue abstract background

📊 PowerShell 7 installs to a new directory and runs side-by-side with Windows PowerShell 5.1. Source: Microsoft.

PowerShell recovery decision table

Missing item Likely cause Exact fix
Windows PowerShell 5.1 The Start entry is missing, the shortcut was unpinned, or the path entry is broken. Open Start, search Windows PowerShell, then right-click the result and choose Pin to Start or Pin to taskbar. If launching by name fails, open Run and start C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe.
PowerShell 7 It is not installed, or it is installed but not on PATH. Use winget install --id Microsoft.PowerShell --source winget for the default package, or install the MSI with --installer-type wix for managed deployments. Then confirm pwsh.exe is in C:\Program Files\PowerShell\7\.
PowerShell ISE The legacy editor is absent on that device or was never added to the install. Search PowerShell ISE from Start. If it is not present, use Windows PowerShell 5.1 for legacy scripts; PowerShell 7 does not replace ISE.

Command box

  • Find PowerShell 7: winget search --id Microsoft.PowerShell --exact
  • Install PowerShell 7: winget install --id Microsoft.PowerShell --source winget
  • Install MSI package: winget install --id Microsoft.PowerShell --source winget --installer-type wix
  • Check PATH in PowerShell: $env:Path
  • Check PATH in Command Prompt: echo %PATH%
  • Launch 5.1 directly: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  • Launch PowerShell 7 directly: C:\Program Files\PowerShell\7\pwsh.exe

Why is PowerShell missing from Windows 11?

Most often, the app is not truly gone. The Start pin is missing, the search result moved, or you are looking for the wrong shell. Windows PowerShell 5.1 comes with Windows, while PowerShell 7 is installed separately. PowerShell ISE is a third item and does not come back when you install PowerShell 7.

Restore Start entries and pins

  1. Open Start search. Press the Windows key and type PowerShell. Use the exact result name you need: Windows PowerShell, PowerShell, or PowerShell ISE.
  2. Pin the right result. Right-click the app you need and choose Pin to Start or Pin to taskbar. If the app appears in search but not on the tile grid, this restores quick access without reinstalling anything.
  3. Open it once. Launch the app from Start after pinning it. That confirms Windows still knows the shortcut and places a fresh entry in recent results.

On a system where Windows PowerShell still appears in search, but the taskbar pin vanished after cleanup, pin the search result first. That is the quickest fix. If the executable still opens from search, you do not need to reinstall anything.

How do I install PowerShell on Windows 11?

How do I install PowerShell on Windows 11?
A PowerShell setup window appears over the Windows 11 desktop

Use winget first. It is included in Windows 11 as part of App Installer, and Microsoft recommends it for Windows clients. The default WinGet package for PowerShell 7.6.0+ is MSIX, while the MSI path is better for server and enterprise deployment needs.

Install PowerShell 7 with winget

  1. Open Windows Terminal. Start a normal terminal session, not an elevated one unless your environment requires it.
  2. Search the exact package. Run winget search --id Microsoft.PowerShell --exact to confirm the package ID before you install it.
  3. Install the default package. Run winget install --id Microsoft.PowerShell --source winget. That installs the current PowerShell 7 package from the winget source.
  4. Use the MSI when needed. For enterprise or scripted deployment, run winget install --id Microsoft.PowerShell --source winget --installer-type wix. The MSI package is the better fit for that use case.

Say your admin script needs a stable shell on 20 managed laptops. The MSI path is the better choice because it is built for enterprise deployment, while the default MSIX package fits routine installs.

Know the package differences

  • MSIX is the default WinGet install format for PowerShell 7.6.0+.
  • MSI is best for Windows Server and enterprise deployment.
  • ZIP fits sideloading or multiple-version installs.
  • PowerShell 7.7-preview uses a separate preview package ID.
  • PowerShell 7.7.0 does not have an MSI package.

Is Windows PowerShell different from PowerShell 7?

Yes. Windows PowerShell 5.1 is the Windows-built legacy shell. PowerShell 7 is the newer client line, installs in a new directory, and runs side by side with 5.1. If an old module or script expects Windows PowerShell, do not replace it with PowerShell 7 unless the script is known to work there.

Pick the right shell for the job

  1. Use 5.1 for legacy tools. Start Windows PowerShell when a script or module was written for the older Windows-only shell.
  2. Use 7 for new work. Start pwsh when you want the current PowerShell 7 line on Windows 11.
  3. Keep both installed. Do not remove 5.1 just because 7 is present. Some admin scripts still depend on the older host.

Why is PowerShell ISE missing from Windows 11?

PowerShell ISE is a separate older scripting environment, not part of PowerShell 7. Installing PowerShell 7 will not restore it. If ISE is missing, search for the standalone ISE entry in Start first, then fall back to Windows PowerShell 5.1 for scripts that expect the old editor or host.

Recover the old editor path

  1. Search for ISE directly. Open Start and type PowerShell ISE. Use the exact app name, not just “PowerShell.”
  2. Open the matching result. If it appears, launch it from the search result, then pin it to Start or the taskbar.
  3. Use 5.1 if ISE is absent. Open Windows PowerShell and run the same command there. That keeps older scripts working without forcing a PowerShell 7 changeover.

Still not working?

Still not working?
A Windows error dialog says PowerShell has stopped working

If search, pins, and direct launch paths fail, check the executable path and then repair the install path that Windows uses to discover the shell. For managed systems, the MSI package is the cleaner recovery route. For broken launches, a PATH issue is more likely than a missing app.

Check the executable path

  1. Verify the 5.1 path. Confirm that C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe exists for Windows PowerShell.
  2. Verify the 7 path. Confirm that C:\Program Files\PowerShell\7\pwsh.exe exists for PowerShell 7.
  3. Check PATH entries. Run $env:Path or echo %PATH% and look for the PowerShell 7 folder. If it is missing, reinstall PowerShell 7 so the installer can add the path entry again.

Repair the installer path

  1. Reinstall with winget. Run winget install --id Microsoft.PowerShell --source winget again if the shell still will not launch by name.
  2. Switch to MSI for managed use. Use winget install --id Microsoft.PowerShell --source winget --installer-type wix when you need a deployment-friendly package.
  3. Restore explorer entries. If the shell is installed but Explorer does not show the context entries, reinstall with the package that sets them. The installer properties are ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL for the Open PowerShell entry and ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL for the Run with PowerShell file entry.

The Windows Explorer context menu is controlled by the installer. If the right-click commands are gone, the install likely skipped the context-menu options. Reinstall with the correct installer switches.

Context-menu recovery steps

  1. Run the installer again. Use the package path that your environment allows, then include the context-menu options you need.
  2. Confirm both entries. Check for Open PowerShell on folders and Run with PowerShell on files where your workflow expects them.
  3. Pin a launcher too. Keep a Start pin or taskbar pin so you have a second way in if Explorer integration changes later.

Keep reading

Frequently asked questions

How do I get PowerShell back in Windows 11 Start menu?

Open Start, search the exact app name, then right-click the result and choose Pin to Start or Pin to taskbar. If the result exists but the pin is gone, this restores the shortcut without changing the install.

How do I update PowerShell on Windows 10?

Use the same package name and WinGet command if winget is present: winget install --id Microsoft.PowerShell --source winget. If winget is missing on that machine, install from the Microsoft package path that your environment allows, then relaunch the shell after the update.

Where is the PowerShell executable located in Windows 11?

Windows PowerShell 5.1 is in C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe. PowerShell 7 is in C:\Program Files\PowerShell\7\pwsh.exe. If a search launch fails, try those paths directly from Run or File Explorer.

Why does Windows PowerShell keep popping up?

That usually means a shortcut, script, or right-click action is calling the older shell on purpose. Check the file association or the task that launches it, then pin the newer shell you want and update the target path to pwsh.exe if the newer version is installed.

Can I install PowerShell with winget on Windows 11?

Yes. Windows 11 includes winget through App Installer, and Microsoft recommends it for Windows clients. Use winget search --id Microsoft.PowerShell --exact first, then install with winget install --id Microsoft.PowerShell --source winget.