| Previous | Next |
| APPMODEL_ERROR_DYNAMIC_PROPERTY_INVALID | ERROR_STATE_LOAD_STORE_FAILED |
APPMODEL_ERROR_PACKAGE_NOT_AVAILABLE
Package content or its deployment volume cannot be used now
APPMODEL_ERROR_PACKAGE_NOT_AVAILABLE means AppModel knows the package identity but cannot make the package available to the caller. PackageStatus distinguishes unavailable, offline, data-offline, partially staged, servicing, and dependency conditions that can explain this state.
Refresh the Package object and inspect every status flag, the package volume, dependencies, and active deployment operations. A package on an offline or removed volume needs that volume restored; a partially staged or servicing package must complete deployment; a dependency issue requires the matching framework or resource package. Re-registering without resolving content availability can leave the same failure.
What to inspect
- Read a fresh PackageStatus instance and all flags.
- Check package volume and dependency availability.
- Wait for servicing or staging to complete before activation.
References
- Microsoft: package availability and offline flags
- Microsoft: Package status, dependencies, and locations
- Microsoft: package volumes and deployment operations
Looking for a different code? Search another status or error code.