MSIX/AppX package resources are currently in use
0x80073D02 means package deployment cannot proceed because a running process is using resources that must be changed.
What it means in this context
Microsoft’s MSIX deployment troubleshooting table maps 0x80073D02 to ERROR_PACKAGES_IN_USE: the package is currently in use by a running process. The narrow fix is to close the relevant running app/process before updating or uninstalling the package.
What is known, and what is not proven yet
Keep observation, evidence and conclusion separate before making a higher-impact change.
MSIX/AppX deployment returned 0x80073D02.
Running process/package relationship plus ActivityId when available.
Package deployment blocked by resources in use.
Which process owns the package resource and whether closure/restart clears it.
Close the owning app/process and retry once.
App publisher/IT if package processes repeatedly remain locked after restart.
- Save work in the affected app and close it normally.
- Check Task Manager for remaining processes belonging to that app/package.
- Retry the deployment once after the app is fully closed.
- If an ActivityId was returned, preserve it and use Get-AppxLog if the code changes or the package still fails.
Close the owning process before changing the package
Low riskWhy: The documented condition is package resources currently in use.
- Close the app normally.
- End only clearly identified leftover processes for that app when necessary.
- Retry the install/update/uninstall.
- Restart Windows if package processes cannot be cleanly released.
When not to use this record
Do not terminate unrelated Windows processes or bulk re-register all AppX packages just to clear 0x80073D02.
If it persists
If the deployment then returns a different HRESULT, preserve the new ActivityId/code and follow that scoped package error.