| Previous | Next |
| kOSKextReturnNotLoadable | kOSKextReturnDependencyLoadError |
kOSKextReturnLoadedVersionDiffers
The conflict is with the active in-memory extension
kOSKextReturnLoadedVersionDiffers does not merely say that another file exists on disk. XNU defines it as a case in which a different version, executable UUID, or executable checksum of the requested kext is already loaded. The relevant comparison is therefore between the requested build and the code active in the running kernel.
This distinction matters after an installer copies a newer bundle. Replacing a disk copy does not by itself replace a kext already active in memory. On newer macOS systems, third-party kernel extensions are incorporated through an Auxiliary Kernel Collection and a change may require the appropriate approval and a restart before the newly selected collection is used.
What to record
- Compare bundle identifier, version, executable UUID, and executable checksum for the requested and active builds.
- Record the origin and install time of both copies; duplicate identifiers from different products are especially important.
- Confirm whether a restart and collection rebuild are part of the documented deployment path before treating the on-disk copy as active.
- Do not force a replacement in a running kernel merely to remove the status; resolve the package-version conflict first.
References
- XNU: OSKextLib.h
- Apple Platform Security: securely extending the kernel
- Apple Deployment: system extensions in macOS
Looking for a different code? Search another status or error code.