Other World Computing (OWC) has released Dock Ejector 2.1, a free utility for Mac and PC that adds one-click safe ejection of connected data volumes and, on Mac, high-power USB port enablement. The kernel extension utility is now distributed through the Apple App Store as well as directly from OWC. But the most interesting change is not on the feature list: it is what the software no longer needs to do to your Mac.
The update itself is modest — a version bump to a free helper app — but the engineering behind it touches one of the quieter, more consequential changes in modern macOS. For most of the Mac’s history, third-party hardware and security software extended the operating system by loading code into the kernel. Apple has spent the better part of a decade replacing that model, and Dock Ejector 2.1 is a small, concrete example of the transition. The previous version installed a kernel extension — a kext — to enable high-power operation on OWC’s dock USB ports.
On an Apple silicon Mac, loading a kext means lowering the machine’s startup security policy from Full Security to Reduced Security, entering an administrator password and restarting. Version 2.1 rebuilds the driver on Apple’s DriverKit framework, which runs in user space, so it installs without touching the security policy. “Version 2.1 switched to Apple’s DriverKit, so it can be installed without ‘Reduced Security’ mode,” said Chris Kooistra, OWC’s vice president of marketing, in written answers.
From kext to DriverKit
To understand why that matters, it helps to know what a kext is. A kernel extension is code that runs inside the macOS kernel, with the same privileges as the operating system itself. That power has a cost: a bug in a kext can panic the whole machine, and a vulnerable one can compromise the entire system. Apple began deprecating kexts with macOS Catalina in 2019, stopped loading deprecated ones by default from Big Sur, and now states plainly in its platform-security guide that “kexts are no longer recommended for macOS.”
The replacement is System Extensions and, for device drivers, DriverKit. A DriverKit driver — a “dext” — ships inside a normal app bundle, runs as a user-space process, and receives only the privileges it declares. If it crashes, the driver process dies and the rest of the system keeps running, rather than the kernel taking the whole machine down with it. The distinction is not cosmetic.
A kext runs with the same privileges as the kernel, so it can reach any part of the system; that is why a faulty kext has historically been a leading cause of kernel panics, and why a vulnerable one is a serious security risk. A dext runs in user space, sandboxed, with a deliberately narrow API. The trade is speed for safety: calls between the driver and the kernel cross a process boundary, which costs a little performance, but a crash stays contained to the driver. The system removes the extension automatically when the user moves the app to the Trash, and installs no longer need the recovery-mode ritual.
That is the change OWC made. “Our development team rebuilt the driver using Apple’s DriverKit framework to make the install process easier for users,” Kooistra said.
Why Apple silicon made it matter
The kext-to-DriverKit question is not academic on a modern Mac. Because kexts run with kernel privileges, Apple silicon treats them as a security downgrade: a kext cannot load on demand, the system merges it into an auxiliary kernel collection, and the user cannot enable it without first changing the startup security policy to Reduced Security. Apple’s support documentation walks users through holding the power button at startup, entering recovery, opening Startup Security Utility and downgrading the policy — a flow one technical analysis described as “hostile by design,” deliberately awkward so that malware cannot trigger it without a human at the keyboard.
For ordinary Mac users, the practical effect is that installing a dock utility no longer means weakening the machine. Apple’s security model on Apple silicon is built around a signed system volume, and kexts are treated as an exception that requires an explicit downgrade. Removing that requirement is the kind of change an IT administrator notices immediately, because the recovery-mode, password-and-restart flow is hard to automate and harder to explain to a non-technical user.
A dock utility forcing that flow is a poor trade for most users. OWC’s Dock Ejector 2.1 does the same job without it, which is the kind of quiet improvement that matters more to system administrators than to feature lists. It also aligns OWC with the direction Apple has set: the company has said Catalina was the last macOS release to fully support kexts without compromises, and that it will keep adding device families to DriverKit while deprecating the equivalent kexts.
The end of the Mac kext
Seen that way, Dock Ejector 2.1 is less a product story than a small window onto a long migration. The kext was a fixture of the Mac for decades — the standard way third-party hardware and security software extended the system — and Apple is retiring it in favour of user-space extensions. Apple’s intent is clear in its own words. Its platform-security guide advises users to “select solutions that don’t require extending the kernel,” and its developer documentation describes kexts as a risk to the integrity and reliability of the operating system. The company has been adding device families to DriverKit — USB, PCI, audio, HID, SCSI, serial — while deprecating the equivalent kexts, which is why the migration now reaches consumer accessories like docks rather than only enterprise hardware.
Many familiar drivers, from USB serial adapters to audio interfaces to USB-to-Ethernet dongles, now ship as dexts; users who have clicked “Allow” in System Settings for a “system extension” have been running DriverKit drivers without necessarily knowing it.
The trade-offs are real. A dext pays an inter-process communication cost on every call to the kernel and carries a few megabytes of memory per device, and its API surface is deliberately narrower than a kext’s. Independent analysis notes that the crash isolation is worth it: the class of failure where a third-party driver panics the whole Mac is becoming rare. For OWC, the practical result is a utility that installs the way modern Mac software should — from the App Store, with automatic updates, and without asking the user to weaken their machine’s security.
Scale is Worth Keeping
The scale, though, is worth keeping in perspective. OWC says about 60,000 compatible docks have been in the field since January 2024, and the utility drew 23,000 downloads in the last 90 days across Mac and PC. That is a real audience, but a niche one: this is a specialist tool for people who use OWC docks, not a mass-market product. Its significance comes from what it demonstrates about the platform, not from how many people use it.
It also reflects a wider pattern in Mac software: as Apple narrows what third-party code can do inside the kernel, the vendors that adapt first tend to have the smoothest install experiences, and the ones that lag face user friction at exactly the moment a customer is setting up new hardware.
What to watch
Three things will show whether the kernel extension migration story develops. First, whether OWC’s other software titles follow Dock Ejector onto DriverKit, which would confirm a deliberate strategy rather than a one-off fix. Second, whether Apple accelerates the kext retirement — for instance by narrowing where kexts still load — which would push more vendors down the same path. Third, whether the reduced friction shows up in adoption, since an easier install is the kind of change that quietly lifts downloads.
A fourth signal is how Apple treats the kexts that remain. Some device classes — notably those that need privileged hardware access — still rely on kernel code, and Apple’s guidance for them has been to keep the road map toward user-space APIs rather than assume the old model survives. Where Apple draws that line will shape how quickly vendors like OWC finish the move.
What the update does and doesn’t establish
It establishes a GA utility with one-click safe ejection, Mac high-power USB port enablement, a DriverKit-based driver that no longer requires Reduced Security, and App Store distribution. It does not establish independent performance data, any named enterprise customer, or that the feature set is materially different from competing eject utilities.
The honest summary: OWC Dock Ejector 2.1 is a free utility, and on its own it is a modest one. What makes it worth a look is the plumbing underneath — a concrete example of Apple’s long, deliberate retirement of the kernel extension, and of the awkward security dance that kexts force on Apple silicon users. OWC is following the platform’s direction rather than setting it, but it is a clear illustration of where Mac software has been heading for years: out of the kernel, into user space, and away from the settings that make a Mac less secure.
Editor’s Note: This article draws on the OWC release and written answers supplied by OWC, plus Apple’s developer and platform-security documentation, Apple’s WWDC sessions on System Extensions and DriverKit, and independent technical analysis by Mac Internals. The kernel extension feature set and the DriverKit rebuild are as described by OWC; the installed-base and download figures are company-reported, and Apple’s kext-deprecation behaviour is verified against Apple’s own documentation. No interview beyond the written Q&A by TechRecast.