Powershell: Can't install msix

Created on 31 Aug 2019  路  16Comments  路  Source: PowerShell/PowerShell

Support Question

Hi. I want to try the new PowerShell-7.0.0-preview.3-win-x64.msix, but I got a This app package is not supported for installation by App Installer because it uses certain restricted capabilities.

How to solve this? I have googled it but get nothing. Thanks.

鍥剧墖

Area-Maintainers-Build Issue-Enhancement Resolution-Answered

Most helpful comment

Yeah, I notified @SteveL-MSFT on Twitter when I ran into this.

I had to actually enable Developer Mode in my Security settings on windows 10, and then I also had to install it using Add-AppxPackage -Path $PathToMsix before it would let me install it.

All 16 comments

Yeah, I notified @SteveL-MSFT on Twitter when I ran into this.

I had to actually enable Developer Mode in my Security settings on windows 10, and then I also had to install it using Add-AppxPackage -Path $PathToMsix before it would let me install it.

It can't be successfully added to Intune either

image

image

Can't find any info in Azure on why it failed.

It's not Store signed so you can't just install it. As @vexx32 noted, you have to be in Developer mode and use the cmdlet to side-load it. At some point, we will be publishing this to the Store.

I opened an administrative PowerShell (legacy) window and ran Add-AppxPackage -Path $PathToMsix. This resulted in a progress bar that filled up and no visible errors. However, when I launch PowerShell (via start button and typing PowerShell) I still get the old version.

@MicahZoltu it's pwsh

I opened an administrative PowerShell (legacy) window and ran Add-AppxPackage -Path $PathToMsix. This resulted in a progress bar that filled up and no visible errors. However, when I launch PowerShell (via start button and typing PowerShell) I still get the old version.

Same for me.

The solution is to make sure, the PATH env variable has priority for %LocalAppData%\Microsoft\WindowsApps

I think it's best to just have the MSI or MSIX installed, not both.

@SteveL-MSFT

Windows Terminal does not recognize the MSIX / Store installation. That's why I need to have both for now!

@Nirmal4G I'm working with the WT team to have it detect the MSIX installed version, so that should hopefully be temporary (installing both)

This issue has been marked as answered and has not had any activity for 1 day. It has been closed for housekeeping purposes.

Hey everyone, just to add to all this:
When running Add-AppxPackage -Path $PathToMsix from PowerShell 5,
I got the following error:
Cannot find path 'C:\Users\Jonas\downloads\PowerShell-7.1.0-preview.2-win-x64.msixw' because it does not exist.

Turns out the filename was too long. I renamed it to PowerShell-7.msix and away we go...

Hey everyone, just to add to all this:
When running Add-AppxPackage -Path $PathToMsix from PowerShell 5,
I got the following error:
Cannot find path 'C:\Users\Jonas\downloads\PowerShell-7.1.0-preview.2-win-x64.msixw' because it does not exist.

Turns out the filename was too long. I renamed it to PowerShell-7.msix and away we go...

Most likely due to the typo in your $PathToMsix variable (see the 'w' on the end).

I'm seeing the same issue when trying to install 7.1.3.0 msix (PowerShell-7.1.0-preview.3-win-x64) on Windows 10.

image

@wx-yz, that seems to be as expected. The thread above points out that this is not signed from the Store yet and as such it must be sideloaded as a developer tool if you are using the MSIX. When they finally release PowerShell to the store, I suspect in a way similar to how Python is available, then it will install this way. Until then you will have to sideload, use dotnet.exe tools install powershell -g, or the MSI. Personally I had been using the global dotnet install method and just uninstalled it to try the MSIX installer... I'm not sure I see the advantage of using MSIX until the Store is managing the updates. I'm debating my options.

Thanks @rbeesley, I did not know that. I ended up using winget. Starting to like that a lot.

@wx-yz, oh, you're right. I hadn't considered Chocolatey, Scoop, or WinGet... I went with sideloading the MSIX just to see what complications the additional restrictions being containerized will bring, but this does seem like the perfect opportunity to kick the WinGet tires.

Was this page helpful?
0 / 5 - 0 ratings