| Previous | Next |
| STATUS_NDIS_BAD_CHARACTERISTICS | STATUS_NDIS_OPEN_FAILED |
STATUS_NDIS_ADAPTER_NOT_FOUND
The requested adapter identity cannot be resolved into a usable binding target
STATUS_NDIS_ADAPTER_NOT_FOUND is raised before a protocol or management operation obtains a usable adapter target. The identity can be stale, the adapter can still be initializing, or the expected component can no longer expose the interface that the caller selected.
It differs from media disconnection: an unplugged cable still leaves an adapter object. Start with the adapter identity and the driver-stack composition, then inspect initialization and PnP state rather than treating the result as a routing problem.
Evidence that narrows it
- Capture the interface GUID, LUID or binding identity used to select the adapter, together with the current device instance state.
- Compare device arrival and miniport initialization timing with the first failing request.
- Separate a missing adapter target from a present adapter that later returns
STATUS_NDIS_ADAPTER_NOT_READYorSTATUS_NDIS_MEDIA_DISCONNECTED.
References
- Microsoft: NDIS driver stack
- Microsoft: Miniport adapter states and operations
- Microsoft: Stopping a driver stack
Looking for a different code? Search another status or error code.