Summary:
Parallels Desktop as a virtualiser requires kernel extensions.
I had whitelisted them after upgrading to High Sierra.
The Parallels team has coded a dialogue that will appear when the kernel extensions cannot be loaded.
They then suppose the user has to unblock them in the System Preferences, Security section.
But in my case, this is not true – I have shown their code signature, copied their team ID (which is Parallels’ unique identifier in the Apple universe), whitelisted it in Recovery mode using ‘spctl kext-consent add 4C6364ACXT’, rebooted – same error in Parallels still. Then I again booted in recovery mode, this time disabling consent mode entirely ‘spctl kext-consent disable’, but after reboot Parallels still tells me that error.
So in fact it’s Parallels Desktop having incompatible kernel extensions that cannot be loaded in Developer Beta 4.
Steps to Reproduce:
Run macOS Sierra.
Install Parallels Desktop 12.2.1.
Upgrade to High Sierra Developer Beta 3.
When prompted, whitelist Parallels Desktop team ID in System Preferences.
Upgrade to High Sierra Developer Beta 4.
Start Parallels Desktop.
Expected Results:
Parallels Desktop should start.
Observed Results:
Parallels Desktop fails to load kexts and tells the user to unblock them, which has already been done.
Version:
macOS High Sierra 10.13 Developer Beta 4 (17A315i)
Notes:
Removing Parallels Desktop and reinstalling it does not resolve the issue.
Running 'spctl kext-consent add 4C6364ACXT' in Recovery Mode does not resolve the issue.
Running 'spcrl kext-consent disable' in Recovery Mode does not resolve the issue.
Description
Area: Something not on this list
Summary: Parallels Desktop as a virtualiser requires kernel extensions. I had whitelisted them after upgrading to High Sierra. The Parallels team has coded a dialogue that will appear when the kernel extensions cannot be loaded. They then suppose the user has to unblock them in the System Preferences, Security section. But in my case, this is not true – I have shown their code signature, copied their team ID (which is Parallels’ unique identifier in the Apple universe), whitelisted it in Recovery mode using ‘spctl kext-consent add 4C6364ACXT’, rebooted – same error in Parallels still. Then I again booted in recovery mode, this time disabling consent mode entirely ‘spctl kext-consent disable’, but after reboot Parallels still tells me that error. So in fact it’s Parallels Desktop having incompatible kernel extensions that cannot be loaded in Developer Beta 4.
Steps to Reproduce:
Expected Results: Parallels Desktop should start.
Observed Results: Parallels Desktop fails to load kexts and tells the user to unblock them, which has already been done.
Version: macOS High Sierra 10.13 Developer Beta 4 (17A315i)
Notes: Removing Parallels Desktop and reinstalling it does not resolve the issue. Running 'spctl kext-consent add 4C6364ACXT' in Recovery Mode does not resolve the issue. Running 'spcrl kext-consent disable' in Recovery Mode does not resolve the issue.
Configuration: Parallels Desktop 12.2.1 MacBook Pro (Retina, 15-inch, Mid 2014) APFS
- Product Version: 10.13 Beta (17A315i) Created: 2017-07-27T21:55:09.445780 Originated: 2017-07-27T00:00:00 Open Radar Link: http://www.openradar.me/33577298