Install Msixbundle Using Powershell May 2026

Whether you are automating a lab environment, deploying via Intune, or just prefer the command line, is the most powerful way to install an MSIX bundle.

To automatically install required dependencies from a folder:

Add-AppxPackage -Path "C:\Deploy\MyApp.msixbundle" -ForceApplicationShutdown For automation (CI/CD, MDM, or configuration management), run it silently without progress bars: install msixbundle using powershell

Invoke-Command -ComputerName "PC-01" -ScriptBlock Add-AppxPackage -Path "\\server\share\MyApp.msixbundle"

Get-AppxPackage -Name "YourAppPublisher.YourAppName" | Select-Object -Property Name, Version, InstallLocation | Error | Likely Cause | Fix | |--------|--------------|------| | 0x80073CF3 | Missing dependency | Install required frameworks first | | 0x80073CF0 | Corrupt bundle | Re-download the file | | 0x80073D0A | Bundle not signed/trusted | Install the publisher certificate first | | 0x80073D05 | Already installed | Remove old version: Remove-AppxPackage -Package "..." | Uninstalling an MSIX Bundle via PowerShell For completeness, here is how to remove what you installed: Whether you are automating a lab environment, deploying

The MSIX packaging format is the future of Windows application deployment. It’s clean, containerized, and reliable. But when you receive an .msixbundle file (a package that contains versions for different CPU architectures or system configurations), double-clicking isn’t always the best option.

Get-AppxPackage -Name "*MyApp*" To see detailed info: But when you receive an

Add-AppxPackage -Path "C:\Deploy\MyApp.msixbundle" -DependencyPath "C:\Dependencies\*.msix" Or force install ignoring non-critical dependency errors (use cautiously):