| Previous | Next |
| ERROR_STATE_CONTAINER_NAME_SIZE_LIMIT_EXCEEDED | STORE_ERROR_UNLICENSED |
ERROR_API_UNAVAILABLE
The requested API is not available
ERROR_API_UNAVAILABLE indicates that an API surface exists conceptually but cannot be used on the current system, edition, component configuration, or execution context. It is a capability result, not necessarily a temporary service outage.
Common scenarios
- The operating-system build predates the API.
- An optional Windows component is not installed.
- The API is unavailable to the current application model or container.
- A compatibility layer exposes the entry point but not the feature.
Developer response
Perform documented capability detection and provide a fallback when possible. Do not loop on retries. Log the OS build, package context, and feature detection result so support can distinguish unsupported systems from deployment faults.
Capability detection
Prefer the platform's documented contract, version, or feature checks over calling the API repeatedly and interpreting failure as detection. Cache the capability result for the process when it cannot change at runtime.
Compatibility behavior
A fallback should preserve correctness, even if it offers fewer features. If no safe fallback exists, disable the command with an explanation that includes the required Windows version or component.
References
Looking for a different code? Search another status or error code.