Capture the failed Windows App Runtime update in the AppX deployment logs before making further package changes; the current SYSTEM workaround identifies a privilege/context difference but does not establish that Windows Firewall is the component blocking installation.
1. Reproduce the failure and capture its actual cause
Do not use PsExec for this test.
- Open Windows Terminal (Admin).
- Run the runtime installer normally and record its exit code:
$installer = "D:\WindowsAppRuntimeInstall-x64.exe"
$p = Start-Process $installer -ArgumentList "--force" `
-Wait -PassThru
"Exit code: 0x{0:X8}" -f ($p.ExitCode -band 0xffffffff)
Get-AppxLog |
Select-Object Time, Id, Message |
Format-List
--force updates the runtime packages and shuts down Windows App SDK processes that could hold packages open. It is supported by Windows App SDK 1.1 and later.^1^
- Open Event Viewer and inspect:
- Applications and Services Logs → Microsoft → Windows → AppXDeployment-Server → Operational
- Applications and Services Logs → Microsoft → Windows → AppxPackagingOM → Microsoft-Windows-AppxPackaging/Operational
- Inventory the runtime packages and retain the output:
Get-AppxPackage *appruntime* |
Select-Object Name, Version, Architecture, Status,
IsPartiallyStaged, PackageFullName |
Sort-Object Name, Architecture
A healthy installation normally contains architecture-appropriate Framework, Main, Singleton, and DDLM packages.^3^
2. Apply the branch matching the logged error
-
0x80070005without a firewall-specific event: This means the system-wide installation or provisioning could not run with sufficient elevation. Confirm that the test was launched from Windows Terminal (Admin), not an ordinary terminal. The runtime installer documents0x80070005for a non-elevated process or an account without administrator privileges.^1^ -
0x80073D02/ERROR_PACKAGES_IN_USE: Close WhatsApp and other Windows App SDK applications, then rerun the elevated installer with--force. Package deployment cannot replace files held by running processes.^4^ -
0x80073CF3: Check the event for the missing dependency, conflicting package, or wrong architecture. That code specifically indicates dependency, update, conflict, or architecture validation failure.^2^ - An event explicitly says access to
windows.Firewallwas denied: This exact deployment condition has been reported to WindowsAppSDK, but the issue was classified as external to Windows App SDK. Microsoft requested a Feedback Hub report under Developer Platform → App Deployment.^5^ Include:- Error code and full package name
- Failure timestamp
- Exported AppXDeployment-Server/AppxPackagingOM events
- Windows build number
- The fact that elevated installation fails but SYSTEM installation succeeds
- Whether the firewall import/export changes the result
This is the appropriate escalation for a confirmed windows.Firewall deployment failure; repeatedly installing as SYSTEM merely preserves the abnormal installation context.
3. Avoid removing runtime packages indiscriminately
Do not purge all Microsoft.WindowsAppRuntime, Main, Singleton, or DDLM packages from this end-user PC. Microsoft warns that removing shared Windows App SDK runtimes can break other applications that depend on them.^6^
Also stop exporting/importing the complete firewall policy unless the logs actually identify firewall configuration as the failure. That operation can overwrite legitimate firewall changes made between export and import.
4. Repair Windows only if targeted diagnosis does not resolve it
If normal elevated deployment still fails and the logs indicate damaged deployment or servicing components rather than a specific package conflict, use:
Settings → System → Recovery → Fix problems using Windows Update → Reinstall now
This is a repair reinstall, not a clean installation: it reinstalls the current Windows version while preserving installed apps, files, and settings. Keep the PC connected to power and the internet; a restart is required.^7^
The option can be absent on managed devices or systems earlier than the supported Windows 11 servicing level. In that case, the remaining supported repair path is an in-place repair using matching Windows 11 installation media; it should likewise be configured to retain apps and personal files.
References
- Windows App SDK deployment guide for framework-dependent apps packaged with external location or unpackaged
- Troubleshooting packaging, deployment, and query of Windows apps
- Check for installed versions of the Windows App SDK runtime
- MSIX troubleshooting guide
- AccessDenied when configuring Capability internetClient for windows.Firewall · Issue #5766 · microsoft/WindowsAppSDK
- Remove outdated Windows App SDK runtime versions from your development computer
- Fix issues by reinstalling the current version of Windows | Microsoft Support