| Previous | Next |
| kOSKextReturnDisabled | kOSKextReturnValidation |
kOSKextReturnNotAKext
Bundle type is the first question
kOSKextReturnNotAKext is a classification result: the path identifies a bundle, but the legacy kext loader does not recognize it as a kernel extension. XNU distinguishes the KEXT package type from DEXT, which identifies a DriverKit driver extension. A DriverKit product is deployed through the system-extension model rather than loaded as in-kernel code.
This result is therefore earlier and more specific than a signing, dependency, or architecture failure. Changing boot-security settings or attempting to approve a bundle cannot turn an application bundle or a DriverKit extension into a legacy kext.
What to verify
- Identify the exact bundle passed to the loader, not a similarly named copy elsewhere on disk.
- Read its package metadata and bundle identifier, then establish whether the product is a legacy kext, a DriverKit extension, or an ordinary application bundle.
- Use the installation and activation path that belongs to that component type; DriverKit extensions use the system-extension workflow.
References
- XNU: OSKextLib.h
- Apple Platform Security: DriverKit security
- Apple Deployment: system extensions in macOS
Looking for a different code? Search another status or error code.