Uninstalling a Mac kernel extension
Recovering after a Kernel Extension (.kext) bricks your Mac
Last night I had a pretty hair-raising experience with a custom USB Serial driver (theoretically meant to allow me to program a cheap Arduino Nano clone, running a CH431/CH431 USB-to-Serial chip) that turned my Mac into a very expensive brick.
After the kernel extension installation completed, the Mac rebooted. I have full disk encryption turned on via FileVault, so the Mac booted fairly quickly into the usual login screen. But the progress bar after login was incredibly slow, eventually ending in a black screen, and the Mac booting into its Recovery Partition. Eeeek.
The log displayed in the Recovery Partition interface was useless, and didn’t seem to mention my new kernel extension at all, but I knew that must have been the cause.
Here’s how I tracked down the extension file, and got my Mac booting again:
- Turn the Mac off.
- Safe Boot, by starting your Mac and immediately holding down the Shift key until you see the login screen.
- Pick a user and enter a password, as normal, at the FileVault login screen.
- Wait a long time for the Mac to boot into the Safe Mode Desktop.
Find out what was installed
You can either:
- Find the installer file that started this whole mess. (It ends with
.pkg… You kept it, right? 😉) And—even though this sounds crazy, trust me—open it again.
- When the first screen of the installer is showing, press
⌘–Ito show the list of files the installer creates.
- Quit the installer, without installing.
Or you can:
- Open Terminal (you might need to go find it in Applications > Utilities, because I don’t think Spotlight works in Safe Boot mode) and type
pkgutil --packagesto list all packages installed on the system, in roughly—I think—date order.
Look through the package names, and once you find the suspicious one, find out which files it installed by typing, eg:
pkgutil --files com.wch.ch34xinstall.mykextdir.pkg
Remove what was installed
In my case, I used the
⌘–I trick to get the file names, and I could see that the installer had created a
usbserial.kext file, and a load of files inside that, but it didn’t say where the kext file was.
Long story short: it turns out Kernel Extensions can be installed into one of two places on a Mac – either
In my case, the
usbserial.kext file was in
/Library/Extensions. Yours might be different, so take a look in both places. Once you’ve found it:
Open up Terminal again, and move the extension somewhere safe, like your Desktop. (I prefer to do this, rather than deleting it, just in case I need to move it back!) Eg:
sudo mv /Library/Extensions/usbserial.kext ~/Desktop/
/Library/Extensionsdirectory, so that the Mac knows that the list of extensions has changed. Eg:
sudo touch /Library/Extensions
In my case, because I was stressing out and wanted a belt-and-braces approach, I also forced the Mac to rebuild its cache of extensions, just in case it didn’t spot the earlier “touch”:
sudo kextcache -invalidate /
Shut down the Mac.
Reboot your Mac in normal mode, and check it works
- Start the Mac as normal.
- If you get logged into your normal Desktop, then hooray! You fixed it!
You can delete the kext file you stashed on your Desktop, eg:
sudo rm -rf ~/Desktop/usbserial.kext
And if you want, you can tell your Mac to forget that it ever ran that cursed installer, eg:
sudo pkgutil --forget com.wch.ch34xinstall.mykextdir.pkg
- However, if you get booted into the Recovery Partition again, then I’m afraid I can’t help you any further 😞