| Previous | Next |
| kOSMetaClassNoKModSet | kOSMetaClassNoSuper |
kOSMetaClassNoInsKModSet
kOSMetaClassNoInsKModSet means that OSMetaClass could not record a class in the kext that owns it during registration. The result is narrower than a generic load failure: the class metadata may have reached the registration path, but the runtime could not complete the association between that class and the extension.
XNU's error mapping labels this as failure to record a class in a kext. The important diagnostic unit is the class-to-kext association, including the extension identifier and class name, rather than the higher-level service that may later fail to start.
What to collect
- The kext identifier, class name, and registration order.
- Earlier OSMetaClass messages about temporary storage, dictionaries, or duplicate classes.
- Evidence of whether the load was rolled back after the association failed.
- The kernel and kext build context; this is legacy kernel-loader behavior, not a user-space API contract.
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.