System Extension Blocked - but can't allow extension

I installed macOS 10.13 High Sierra yesterday. This morning, when trying to boot up my VMWare for the first time since the install, I got the following error message:


"System Extension Blocked

A program tried to load new system extension(s) signed by "VMWare". If you want to enable these extensions, open Security & Privacy System Preferences"


The problem is that when I go to Security & Privacy, there is no option to 'Allow' the extension. I have read that this was a known bug in the beta versions of High Sierra, but surely this was fixed before release!?


I am also now getting exactly the same problem with my Symantec anti-virus. Same error message and still no option option to 'Allow' the extension.


I would be grateful to anyone that has been able to resolve this.

MacBook Pro with Retina display, macOS High Sierra (10.13)

Posted on Sep 27, 2017 1:24 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 13, 2017 10:17 AM

There is a workaround for this. It isn't a great workaround, security-wise, but it does get you back to the behavior of macOS 10.12. Basically, you can turn off the security feature requiring user approval of Kernel Extensions.


First, boot into Recovery Mode by rebooting and pressing and holding command-R as soon as you see the Apple logo. On my machine, I had to hold command-R for quite a while, at least 60 seconds.


Eventually you will see a screen that gives you a couple of options, including reinstalling or running Disk Utility. If you look at the top of the screen, where the Apple menu would ordinarily be, you will see a "Utilities" drop-down menu. Click on that and select Terminal. A window will open up that allows you to type text-based terminal commands.


You will see a "$" prompt in the terminal window. Type the following:


spctl kext-consent disable


then press Return. You should see:


Kernel Extension User Consent: DISABLED

Please restart for changes to take effect.


Then reboot your Mac, and you should be good. You will no longer see the notification panes telling you a Kernel Extension was blocked; they will all be automatically allowed, just as they were in macOS 10.12.


I would recommend waiting until 10.13.1 or 10.13.2 to see if the issue gets fixed, and then undoing this fix by repeating the same steps, but typing


spctl kext-consent enable


instead.


For more information, see the following website:


User Approved Kernel Extension Loading… – Pike's Universum

113 replies

Sep 3, 2018 5:56 AM in response to robGTR

I have experienced with some of our users the same problems clicking on the allow button even in front of the Mac. What does seem to work a lot more reliably but is not suitable for many people is using an MDM system and pushing out a profile to 'whitelist' either individual Kernel Extensions or particular manufacturers team ids. See Prepare your institution for macOS High Sierra 10.13.4 - Apple Support


I therefore whitelist all the most likely manufacturers i.e. VMware, Parallels, VirtualBox aka Oracle, Sophos, Sonnet Tech, Highpoint, ATTO, Tunnelblick and so on.


This article discusses how to find the team ids and bundle ids. See - User Approved Kernel Extension Loading… – Pike's Universum


What I regard as incredibly stupid on Apple's part is that macOS as standard includes Kernel Extensions for Sonnet Tech, ATTO and Highpoint and yet these also are not trusted even though they are built-in to macOS.

Oct 8, 2017 11:40 PM in response to RoelVeldhuyzen

Thank you for your thorough update. I wLund up starting from scratch and doing a clean install and it solved my problems. I had to do a lot manually after that since I did not have a proper back up to restore from (I had a clone of my drive but since it was on beta 10.13.1 and my main machine which was on 10.13, they couldn’t properly talk to each other in order to do a restore). I think I like having a clean system anyway, and I was able to eliminate all the crud that built up over the years. I lost Photoshop CS5 in the process, but I don’t think I’ll miss it too much. I still have to work on getting my photos organized and back up on my main machine, but overall I’m very happy where I am now. In all my years and all my updates, this is the first time I ever needed to do a clean install and now I know firsthand the advantages. Best of luck to everyone!

Dec 13, 2017 3:16 PM in response to mpdharley

I have been having an issue installing an Antivirus package. The Allow button was showing but clicking on it wouldnt work. To fix the problem I created a new administrators user account and have now been able to "allow" the application in Security & Privacy from within that account. I am no expert but am wondering if the existing profile now has some conflict since upgrading to High Sierra.

Oct 3, 2017 11:55 PM in response to robGTR

Okay, little update on my situation for your benefit and time savings 😝

So, my Time Machine back-ups haven't worked since I installed High Sierra, so I made a new 1TB back-up on a USB disk, that took a good 10 hours but worked fine. Then I restored my iMac from that same back-up. I wasn't expecting this to solve my problem, but the Apple Tech suggested it for if I had the time and was curious what there results would be, so why not?

The iMac restored overnight and I just woke up to an iMac that was exactly the same as it was yesterday, still not able to allow system extensions in 'Privacy and Security'. So that was a waste of time. But hey, new datapoint.


My Time Capsule has back-ups going back a few years, with the most recent being about an hour before installing High Sierra. So at the moment I'm restoring that back-up. If my research is correct, restoring this should give me back Sierra on the machine, not High Sierra. So this should basically (temporarily) solve the issue. When This back-up is restored (estimate is 33 hours to go :/ ), I can reinstall High Sierra and see what happens. If that solves it, yay. If I get the same issues again, the only option left is the nuclear one. Clean install and pluck all my files from the new Time Machine Back-up I made yesterday.


So my findings so far:

- A clean install on a separate drive has no issues

- Restoring a Time Machine back-up from after the issue arose does not solve the issue


Next options:

- Restore a Time Machine Back-up from before High Sierra was installed and update it to High Sierra

- Clean install and copy all my files from the most recent Time Machine Back-up.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

System Extension Blocked - but can't allow extension

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.