| Previous | Next |
| kIOReturnIsoTooNew | kIOUSBCRCErr |
kIOReturnNotFound
Not a universal “file not found” result
kIOReturnNotFound means that data was not found. In IOKit, the missing item can be an object, property, table entry, capability, registration result, or another lookup target defined by the specific API. The common code does not mean that a filesystem pathname is missing, and it is distinct from kIOReturnNoDevice, where the target device or service is unavailable.
The key diagnostic information is the lookup scope: which service, registry object, interface, configuration, or request result was searched. Creating a replacement object before establishing that scope can hide an incorrect identifier, stale service instance, or incomplete configuration.
How to investigate
- Record the queried key, identifier, selector, service instance, and active configuration.
- Verify discovery and matching results before performing a follow-up lookup on a cached object.
- Check device removal or re-enumeration events that can invalidate a prior registry or interface reference.
- Compare the exact lookup scope with a successful case instead of assuming all IOKit families expose the same objects.
References
Looking for a different code? Search another status or error code.