Get-AppxPackage -Name "MyCompany.MyApp" | Select-Object * Removal is straightforward:
Add-AppxPackage -Path "C:\Downloads\MyApp.msix" -ErrorAction SilentlyContinue For fully unattended scripts, combine with -ForceApplicationShutdown to close running instances of the app:
Add-AppxPackage -Path "C:\Downloads\MyApp.msix" -ForceApplicationShutdown If you receive an error like "The root certificate of the signature is not trusted" , you must install the signing certificate before installing the MSIX. install msix powershell
$Url = "https://example.com/apps/MyApp.msix" $TempFile = Join-Path $env:TEMP "temp_install.msix" Invoke-WebRequest -Uri $Url -OutFile $TempFile Add-AppxPackage -Path $TempFile Remove-Item $TempFile -Force To confirm the package installed correctly:
Get-AppxPackage -Name "MyCompany.MyApp" | Remove-AppxPackage For machine-wide installations (requires admin): Get-AppxPackage -Name "MyCompany
$Dependencies = @( "C:\Dependencies\Microsoft.VCLibs.x64.14.00.msix", "C:\Dependencies\Microsoft.UI.Xaml.2.7.msix" ) Add-AppxPackage -Path "C:\Downloads\MyApp.msix" -DependencyPath $Dependencies For .msixbundle files (which contain multiple architectures and variants), use the same -Path parameter:
MSIX is the modern Windows application packaging format that combines the best features of MSI, AppX, and ClickOnce. While double-clicking an .msix or .msixbundle file works for interactive installations, PowerShell provides a more powerful, scriptable, and automated approach—essential for IT pros, developers, and enterprise deployments. By mastering these commands, you can integrate MSIX
By mastering these commands, you can integrate MSIX deployment into CI/CD pipelines, remote management tools, and automated configuration scripts—making application lifecycle management simpler and more reliable. Last updated: March 2025. For the latest cmdlet parameters, run Get-Help Add-AppxPackage -Detailed in your PowerShell environment.
Get-AppxPackage -Name "MyCompany.MyApp" | Select-Object * Removal is straightforward:
Add-AppxPackage -Path "C:\Downloads\MyApp.msix" -ErrorAction SilentlyContinue For fully unattended scripts, combine with -ForceApplicationShutdown to close running instances of the app:
Add-AppxPackage -Path "C:\Downloads\MyApp.msix" -ForceApplicationShutdown If you receive an error like "The root certificate of the signature is not trusted" , you must install the signing certificate before installing the MSIX.
$Url = "https://example.com/apps/MyApp.msix" $TempFile = Join-Path $env:TEMP "temp_install.msix" Invoke-WebRequest -Uri $Url -OutFile $TempFile Add-AppxPackage -Path $TempFile Remove-Item $TempFile -Force To confirm the package installed correctly:
Get-AppxPackage -Name "MyCompany.MyApp" | Remove-AppxPackage For machine-wide installations (requires admin):
$Dependencies = @( "C:\Dependencies\Microsoft.VCLibs.x64.14.00.msix", "C:\Dependencies\Microsoft.UI.Xaml.2.7.msix" ) Add-AppxPackage -Path "C:\Downloads\MyApp.msix" -DependencyPath $Dependencies For .msixbundle files (which contain multiple architectures and variants), use the same -Path parameter:
MSIX is the modern Windows application packaging format that combines the best features of MSI, AppX, and ClickOnce. While double-clicking an .msix or .msixbundle file works for interactive installations, PowerShell provides a more powerful, scriptable, and automated approach—essential for IT pros, developers, and enterprise deployments.
By mastering these commands, you can integrate MSIX deployment into CI/CD pipelines, remote management tools, and automated configuration scripts—making application lifecycle management simpler and more reliable. Last updated: March 2025. For the latest cmdlet parameters, run Get-Help Add-AppxPackage -Detailed in your PowerShell environment.