Apple has a huge amount of leverage due to their total control over the platform. I didn't update to Sierra until May of this year and even then I got hit by a nasty bug that wasn't fixed until 10.12.6, two weeks later. I'm still running Sierra on my primary machine and I intend to continue doing that until June, 2018 at least. I'm not going to apologize for Apple or even recommend High Sierra. And it is free, because I only run Mac VMs. I was just blown away by how much faster it is. Then, Parallels released Parallels Desktop Lite in the Mac App Store, using the hypervisor instead of kernel extensions. That ran fine for a few years but Yosemite and later versions were virtually unusable in a VM. For example, when Parallels stopped working in 10.9.3 (I think), due to a kernel extension I think, I switched to VMWare. A kernel extension is really a modification of the operating system by someone who, in almost all cases, doesn't know how to do that properly. I don't necessarily disagree with (my interpretation of) Apple's approach. For one thing, Apple is expecting 3rd party kernel developers to properly handle a failure to load the kernel and then give the user some feedback. I'm getting all of this from Apple's own Tech Note: Supposedly, any extensions that were already installed before the upgrade will be automatically approved. If an app later tries to load the extension again, you will get another 30 minute window to approve, but no more alerts. Supposedly, you get an alert and then you have 30 minutes to approve the extension. What you are describing definitely sounds like a bug. This is part of Apple's effort to "discourage" kernel extensions and move macOS more towards iOS. User Approved Kernel Extension Loading… – Pike's Universum 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įor more information, see the following website: 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. Then reboot your Mac, and you should be good. Please restart for changes to take effect. You will see a "$" prompt in the terminal window. A window will open up that allows you to type text-based terminal commands. If you look at the top of the screen, where the Apple menu would ordinarily be, you will see a "Utilities" drop-down menu. On my machine, I had to hold command-R for quite a while, at least 60 seconds.Įventually you will see a screen that gives you a couple of options, including reinstalling or running Disk Utility. Basically, you can turn off the security feature requiring user approval of Kernel Extensions.įirst, boot into Recovery Mode by rebooting and pressing and holding command-R as soon as you see the Apple logo. It isn't a great workaround, security-wise, but it does get you back to the behavior of macOS 10.12.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |