| Previous | Next |
| STATUS_APISET_NOT_HOSTED | STATUS_DEVICE_HARDWARE_ERROR |
STATUS_APISET_NOT_PRESENT
Distinguish an absent API-set contract from a contract that exists but has no usable host
STATUS_APISET_NOT_PRESENT indicates an API-set contract is not present. Windows API sets form a versioned contract namespace used by the loader to redirect virtual API-set names to implementation DLLs. This is a different diagnostic question from a missing ordinary DLL file because the contract name is resolved through the API-set schema.
Compare the exact contract name with the API-set naming and versioning rules. A typo, unsupported contract version, or binary built for a different Windows platform can request a contract the target system does not expose. Do not strip the version suffix or redirect the import manually to a guessed host DLL; host mappings are an operating-system property and can differ by device.
For optional features, test API-set availability before calling the dependent path. For mandatory dependencies, verify the application's minimum Windows requirement and the toolchain/import libraries used to build it. The import table and API-set contract name are more useful than a directory search for a physical DLL that may never exist under the contract's name.
What to inspect
- The complete API-set contract including version suffix and the image import that references it.
- Target Windows build/device family and whether the contract is reported as implemented or present for that platform.
- SDK, import library, and minimum-platform settings used to build the failing binary.
References
- Microsoft: Windows API sets
- Microsoft: API set loader operation
- Microsoft: Detect API set availability
- Microsoft: PE/COFF image format
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.