Closed miketheitguy closed 4 years ago
/dup #5932
these use the same underlying technology
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
LOL OOPS wrong bug
This shouldn't require elevated rights, but it sounds like your app package catalog is horked. Can you follow the troubleshooting steps linked from that link?
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
I know this is closed, but in case others run into this. I was getting this error trying to double click the msix installer. If I run 'add-appxpackager -path filename.msix' it did install Windows Terminal. Oh yea, add-appxpackager worked in PowerShell 5.1 - NOT PowerShell 7.
I know this is closed, but in case others run into this. I was getting this error trying to double click the msix installer. If I run 'add-appxpackager -path filename.msix' it did install Windows Terminal. Oh yea, add-appxpackager worked in PowerShell 5.1 - NOT PowerShell 7.
@dweddig01 Thanks for this information. It saved me.
Note that there is a typo in the line. Should be:
add-appxpackage -path path\to\file.msixbundle
(Delete stray "r" and add "bundle" to the end of extension, at least for me.)
Environment
Steps to reproduce
Expected behavior
For the Terminal to Install.
Actual behavior
App installation failed with error message: Deployment Add operation with target volume C: on Package Microsoft.WindowsTerminal_2020.512.2308.0neutral~_8wekyb3d8bbwe from: (Microsoft.WindowsTerminal_0.11.1333.0_8wekyb3d8bbwe.msixbundle) failed with error 0x8000FFFF. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. (0x8000ffff)