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.
Start-Process -FilePath "powershell.exe" -ArgumentList "-Command Add-AppxPackage -Path 'C:\Deploy\MyApp.msixbundle' -ErrorAction Stop" -WindowStyle Hidden -Wait To install an MSIX bundle on a remote machine:
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: install msixbundle using powershell
Get-AppxPackage -Name "*MyApp*" To see detailed info:
Add-AppxPackage -Path "C:\Deploy\MyApp.msixbundle" -DependencyPath "C:\Dependencies\*.msix" Or force install ignoring non-critical dependency errors (use cautiously): Whether you are automating a lab environment, deploying
Invoke-Command -ComputerName "PC-01" -ScriptBlock Add-AppxPackage -Path "\\server\share\MyApp.msixbundle"
Add-AppxPackage -Path "C:\Deploy\MyApp.msixbundle" -ForceApplicationShutdown For automation (CI/CD, MDM, or configuration management), run it silently without progress bars: deploying via Intune
Note: CredSSP or Kerberos delegation may be needed if accessing network paths from the remote machine. After installation, confirm the app exists: