When running scripts via automation tools, pipe the results to a log file to capture verbose error streams: powershell
The MSIX package was built with a minimum OS build version higher than the version running on the target machine. You must update Windows or rebuild the MSIX package with a lower minimum OS target. Automating Deployment via SCCM or Intune
You cannot provision a package if it is already installed for a specific user. Remove it first.
Once you install the MSIX module, life becomes easier: install msix powershell all users
: The full path to your .msix or .msixbundle file.
[switch]$SkipCertificateCheck
Start-Transcript -Path "C:\Logs\MsixInstall.log" Add-AppxProvisionedPackage -Online -FolderPath "E:\Deploy\app.msix" Stop-Transcript When running scripts via automation tools, pipe the
# Install certificate to Trusted Root store (machine-wide) Import-Certificate -FilePath ".\yourApp.cer" -CertStoreLocation "Cert:\LocalMachine\Root"
Right-click the Start menu, select or Windows PowerShell (Admin) . 2. Run the Provisioning Command
Import-Certificate -FilePath "C:\Path\To\Certificate.cer" -CertStoreLocation "Cert:\LocalMachine\TrustedPeople" Use code with caution. 2. Error: "Deployment failed with HRESULT: 0x80073CFB" Remove it first
(Get-AppxPackage -AllUsers | Where-Object Name -eq "YourAppName").InstallLocation
Import-Certificate -FilePath "C:\Path\To\Certificate.cer" -CertStoreLocation Cert:\LocalMachine\TrustedPeople
If you are sideloading an internal app, Windows blocks it. Install the certificate first.
Get-AppxProvisionedPackage -Online | Where-Object $_.PackageName -like "*YourAppName*"