My company occasionally gets reports from users that they can install our driver but they can't get it to load in macOS 10.13.
What will typically happen from a user-facing perspective is they will run our installer, see the "System Extension Blocked" dialog that points them to the Security & Privacy system preferences, open Security & Privacy, click the "Allow" button at the button of the window that's supposed to allow our kext to load, and then nothing will happen. Specifically, the "Allow" button presses, but then does not go away and the kernel extension never loads.
Behind the scenes, what's going on is we're calling kextload to load our kernel extension and it always fails with status code 27, meaning that our kext doesn't yet have permission from the user to load. Calling kextload again doesn't in anyway change the problem. As near as we can tell, once a user's system gets into this state, it becomes impossible for our (or possibly anyone else's) kexts to load.
The only methods we've found to workaround this issue is to either:
a) boot into the recovery environment and disable kext user consent by executing `spctl kext-consent disable` in Terminal, or
b) reinstall macOS
Have any of you encountered this problem before? If so, is there any methods of dealing with it?
We suspect it's a bug in macOS but haven't been able to confirm it. Unfortunately, the only systems we've encountered that experience this issue are user's systems. We haven't managed to replicate it on our own systems, much less find any consistent way to trigger it.
- Brian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list (
Darwin-...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/darwin-drivers/darwin-drivers-garchive-96018%40googlegroups.com
This email sent to
darwin-drivers...@googlegroups.com