Open PowerShell as an Administrator and execute the Add-AppxProvisionedPackage cmdlet: powershell
To confirm that the MSIX package has been successfully provisioned or installed for all users, use the following verification commands. Check Provisioned Packages (System-Wide) powershell
$profiles = Get-CimInstance -ClassName Win32_UserProfile | Where-Object -not $_.Special -and $_.Loaded -eq $false foreach ($p in $profiles) $sid = $p.SID $mounted = $true Add-AppxPackage -Path $packagePath -Register -User $sid -ForceApplicationShutdown install msix powershell all users
If you want a ready-to-run script that handles certificate import, provisioning, and per-user installation for all existing profiles, tell me your package path and certificate path and I’ll generate it.
但对于使用 Add-AppxPackage 命令的 MSIX 来说，情况则截然不同。 Add-AppxPackage 命令的核心功能，是将签名应用包添加至。虽然有个名为 -AllUsers 的开关看似能实现为所有用户安装，但在实践操作中，这条命令常常会提示错误，指出使用该命令安装的应用并未向所有用户进行预配（provisioned）。这就是为什么仅靠基础的 Add-AppxPackage 命令无法达成目标的原因。 Open PowerShell as an Administrator and execute the
Switch to a standard user account (not admin) and run:
Get-AppxProvisionedPackage -Online | Select-Object DisplayName, PackageName, Version If you want to optimize this process, tell
Pipe your command outputs to text files in enterprise deployment scenarios to easily trace errors if an installation fails on a remote machine. If you want to optimize this process, tell me:
Many MSIX packages rely on shared runtime dependencies. If your package fails to install due to a missing dependency, you must supply the paths to the dependency .msix files using the -DependencyPackagePath parameter. Here is how to handle a package with dependencies: powershell
PowerShell must be opened with elevated permissions ("Run as Administrator").
Even with the correct command, several issues frequently arise. Here’s how to solve them.