| Previous | Next |
| NAP_E_NOT_PENDING | NAP_E_MAXSIZE_TOO_SMALL |
NAP_E_ID_NOT_FOUND
The NAP component ID cannot be found
NAP_E_ID_NOT_FOUND is HRESULT 0x8027000A (signed decimal -2144927734, unsigned decimal 2150039562). AllStat, using winerror.h, describes it as “The NAP component's id was not found.” The value has failure severity, facility 0x27, and code field 0x000A.
This is a legacy Network Access Protection result: Microsoft states that NAP is unavailable starting with Windows 10 and that current Windows Server releases do not include the former NAP, HRA, and HCAP roles; use the code for supported legacy systems, archived telemetry, compatibility components, or migrations rather than assuming a modern machine should expose the old platform.
A management lookup addressed an absent component
The public error table defines this value broadly and does not assign it to one exclusive method. It can therefore appear when management, binding, status, or configuration code looks up a NAP component by ID and no record matches. The exact owner must be established from the API and component category; the numeric ID alone does not reveal whether the missing object is an SHA, SHV, or enforcement client.
Reasons the lookup misses
- The caller uses an ID from another NAP component namespace or from a different deployment environment.
- The component was unregistered but stale policy, cache, or automation still references it.
- A decimal/hex conversion, signed cast, or configuration parser changed the 32-bit identifier.
- An upgrade assigned a new stable ID but did not migrate all server and client references.
- A delete or query operation is replayed after the target record has already been removed.
Lookup evidence
- Capture the raw 32-bit ID in hexadecimal and decimal, the API name, machine role, and component category.
- Enumerate current registrations and compare IDs rather than matching only friendly names.
- Record the source of the ID—manifest, registry, policy, packet attribute, command line, or management database.
- Correlate recent registration changes, image restore, policy deployment, and uninstall events.
Locating the stale reference
- Verify the intended component is installed and registered on the machine where the lookup executes.
- Trace the ID back to its authoritative configuration and compare it with the running component’s registration.
- For an idempotent delete, decide explicitly whether “already absent” is acceptable rather than treating every miss as fatal.
- For an operational query or bind, repair the missing registration before retrying.
Difference from nearby NAP results
NAP_E_NOT_REGISTERED is normally returned when a component attempts an operation that requires its own prior registration. NAP_E_ID_NOT_FOUND is the broader lookup result and may be returned to an external management caller. NAP_E_CONFLICTING_ID says the record exists but belongs to an already registered entity.
Retry and recovery
Retry only after the authoritative ID or registration set changes. Creating a placeholder component merely to satisfy the lookup can route health traffic incorrectly. If the operation is cleanup and absence is an allowed final state, record that interpretation at the call site instead of globally converting the HRESULT to success.
Practical scenario
A management script carries an SHV ID from a retired test environment into production and attempts to update it. Production has no matching registration, so NAP_E_ID_NOT_FOUND is returned. Replacing the stale identifier with the production SHV’s registered ID corrects the operation.
References
- Microsoft: NAP error constants
- Microsoft: NAP interfaces
- Microsoft: SHV registration module
- Microsoft: SHA registration example
Looking for a different code? Search another status or error code.