Release Process for v7.7.0 · Issue #28393 · PowerShell/PowerShell · GitHub

Checklist

Please, where is the .msi installer for Windows x64?

MSI has been dropped in favor of MSIX per the announcement from April, unfortunately.

so how do we upgrade from msi installed 7.6 to msix 7.7 ?

Face the same (i gess) issue while tried to upgrade pwsh via winget.

I had to install 7.7.0 (via winget), then manually uninstall previous version (via Settings>Apps) and fix terminal profile to user pwsh instead of full path to pwsh.exe

How to install the msixbundle on a Windows Server Core Edition ?

How to install the msixbundle on a Windows Server Core Edition ?

something like that
some dependencies might be required for Add-AppxProvisionedPackage

$response = Invoke-RestMethod https://api.github.com/repos/PowerShell/PowerShell/releases/latest
[string]$link = $response.assets.browser_download_url -match 'msixbundle$'
$target = "$home\downloads", (Split-Path $link -Leaf) -join '\'
Invoke-WebRequest $link -outfile $target -usebasic
if (Test-Path $target) {
	Add-AppxProvisionedPackage -Online -PackagePath $target -SkipLicense
}

It doesn't work in a Docker image (mcr.microsoft.com/windows/servercore:ltsc2022).
Add-AppxProvisionedPackage: The specified module could not be found.

We'll stay at 7.6.10 for now.

It doesn't work in a Docker image (mcr.microsoft.com/windows/servercore:ltsc2022). Add-AppxProvisionedPackage: The specified module could not be found.

We'll stay at 7.6.10 for now.

This is DISM Module. It's existed since WS2016
you may try this
dism.exe /Online /Add-ProvisionedAppxPackage /PackagePath:$target /SkipLicense

This is honestly really annoying that they would do this, since the msix version moves the bloody newest (7.7) powershell folder to the windowsapps folder in Program Files, and the 7.6.10 version which was updated in the microsoft store is installed in a folder in the Program Files directory, it should be the other way round. Also now there's no more custom install for it

Also now there's no more custom install for it

zip? But this entails manual updates, and the like.

So I updated through Microsoft Store... and now have two versions installed, the default is still 7.6.10.0-x64 when I launch a terminal. And only get 7.7 when launching through Microsoft Store. Also, this new version doesn't use my customized powershell profile.

I'm scared of uninstalling the MSI (7.6) version as I see there's more issues with the msix release.

What a mess....

From the transition announcement in April:

At this time, MSIX doesn’t support all use case scenarios that MSI enabled, such as remoting and execution by system-level services (like Task Scheduler). We recognize this gap and are actively working to address it.

It's disconcerting that the PowerShell team broke the workflows of people who depend on these "case scenarios" without supporting a proper migration path.

We'll be sticking with 7.6.* until this mess is cleaned up.

I have to add that this is a particularly frustrating change considering that MSIX doesn't play nicely with versions of Server prior to 2025, and those versions are still supported. I don't see this being a huge issue for my Windows 11 fleet managed through Intune, and may actually be a positive change... but for Windows Server administration, this is going to be a massive headache. I'd really rather not fork my fleet, either, in having the workstations on one version and the servers on another, but this appears to be the path forward.

Microsoft should have expanded MSIX support before forcing it upon their flagship scripting language.

with winget (https://github.com/microsoft/winget-cli) 7.7.0.0 can be installed, but only after uninstalling the previous version before

winget uninstall --ID Microsoft.PowerShell
winget install --ID Microsoft.PowerShell

did the trick for me

GitHub
GitHub - microsoft/winget-cli: WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface). - micros...

Release Process for v7.7.0 · Issue #28393 · PowerShell/PowerShell · GitHub

Repository navigation

Release Process for v7.7.0 #28393

Checklist

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Release Process for v7.7.0 · Issue #28393 · PowerShell/PowerShell · GitHub

Repository navigation

Release Process for v7.7.0 #28393

Description

Checklist

Activity

Still34 commented on Nov 11, 2026

madhon commented on Nov 11, 2026

tony-sol commented on Nov 11, 2026

devAlex-sys commented on Nov 11, 2026

scriptingstudio commented on Nov 11, 2026

devAlex-sys commented on Nov 11, 2026

scriptingstudio commented on Nov 11, 2026

Foxydapirate12 commented on Nov 11, 2026

237dmitry commented on Nov 11, 2026

remcoros commented on Nov 11, 2026

beevik commented on Nov 11, 2026

SeymourGx commented on Nov 11, 2026

runbikeswim commented on Nov 11, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions