| Previous | Next |
| kOSMetaClassDuplicateClass | kOSKextReturnInternalError |
kOSMetaClassNoKext
kOSMetaClassNoKext means the OSMetaClass runtime could not find the kernel extension that should own a metaclass during registration. The problem is an ownership association in the legacy kext loader, not an indication that a device node or user client disappeared.
XNU's OSMetaClass error logger maps this code to “Kext not found for metaclass.” The evidence that matters is the extension identity, class name, dependency graph, and current load transaction. A later failure to publish a service can be a consequence, but it is not the primary meaning of this result.
How to investigate it
- Record the metaclass and the kext identifier expected to own it.
- Review dependencies and loader order for the extension that supplies the class.
- Check for earlier registration or rollback errors that interrupted ownership setup.
- Keep legacy-kext limitations in mind when evaluating a problem on current macOS releases.
References
- Apple XNU: OSReturn.h
- Apple XNU: OSMetaClass.cpp
- Apple: deprecated kernel extensions and alternatives
Looking for a different code? Search another status or error code.