Contents
- Overview
- Deployment File Types for MSIX
- MSIX Package Installations
- Upgrades and Downgrades
- Per User Installations
- Standard User Installation
- Application Package Signing
- Using the App Installer App
- Installing App Installer App
- Application Management via App Installer App
- App Installer App from Web Sites
- Uninstall an MSIX Package using App Installer App
- Installing MSIX with PowerShell
- The Add-AppXPackage Cmdlet
- The Get-AppXPackage Cmdlet
- The Remove-AppXPackage Cmdlet
- Using Get-AppPackageManifest
- Deployment with DISM
- Offline & Online Installation
- Provisioning Packages
- MSIX and the Windows Store
- MSIX and the App Installer File
- Configuration Manager and MSIX Deployment
- Using Intune with MSIX
- VDI Meets MSIX with App Attach
- MSIX and App Center
Installing MSIX with PowerShell
Before we dive into using PowerShell to manage MSIX installations, here's a list of the primary PowerShell cmdlets used for managing packages:
PowerShell | Description |
|---|---|
Add-AppXPackage | Used to install a signed *.msix or *.appx application along with related and dependent packages. |
Get-AppXPackage | This cmdlet is used to provide a list of *.msix and *.appx applications on the device. |
Remove-AppXPackage | Used to remove a signed *.msix or *.appx application from the device. |
Get-AppXPackageManifest | Can be used to read the manifest of an installed application as an XML object. |
PowerShell cmdlets for managing MSIX applications
Note: Each of these commandlets support appx and msix styled packages and are aliased, such that Add-AppPackage (without the X) is the same as Add-AppXPackage. We will show the name using the X in this book to highlight that we are talking about MSIX. |
With these four cmdlets, you can handle most of your MSIX management needs. Make sure to familiarize yourself with the above cmdlets as they are frequently used.