Installation fails on 10.13.x, 10.14.x (rc=-1908)

[rahxephon]

here is the log requested

[socratis]

I'm afraid it's still the same issue:

May  1 16:29:18 Jose-C-MBP installd[437]: ./postflight: /Library/Application
	Support/VirtualBox/VBoxDrv.kext failed to load - (libkern/kext) system policy
	prevents loading; check the system/kernel logs for errors or try kextutil(8).

Please try once again to follow the instructions of the first post in this thread. Shut down the computer, not Restart. When you press the power button again, hold Cmd+Opt+P+R (those piano lessons are really going to pay off now). See if that solves it...

[Ben85]

Just curious whether the VirtualBox developers are planning to update the installer for MacOS? Obviously, the solution for allowing third-party kernel extensions to load is straight forward, but the installer still indicates installation failure. In reality, the installation itself was successful, but the kernel extension wasn't immediately loaded.

From the Apple Developer article referenced in the original post:

"Apps or installers that treat a KEXT load failure as a hard error will need to be changed to handle this new case."

Installers and applications that load kernel extensions may need to be revised to gracefully handle the kernel extension failing to load. Many products treat a KEXT loading failure as a hard failure. Some prompt the user to reinstall, some present a cryptic error message, and some simply don't function.

Starting with macOS High Sierra, installers and apps that load KEXTs should expect that KEXT loading will fail if the user hasn't approved their KEXT. Instead of treating this as an error, the user should be informed that they may need to approve the KEXT.

To determine if a KEXT has failed to load because it does not have user approval:
- If you are using kextutil or kextload, check for the exit code 27. In addition, kextutil will produce the error message System policy prevents loading the kernel extension.
- If you are using the KextManager APIs in IOKit/kext/KextManager.h, check for the result code kOSKextReturnSystemPolicy.

I understand there are likely more pressing issues for the developers to resolve. Due to this, if you can point me in the right direction, I'd be happy to take a look at resolving the issue.

As of VirtualBox 6.0.6 (r130049), the following still occurs (see attached screenshot, apologies about the scaling).

[ted_chou12]

Thank you for the previous posts.
I found the reason, seems like the newer Macbooks especially the Macbook 12inch and the Macbook Air doesn't have USB ports, so USB ports should be disabled in order not to cause software issues.

[Jack Wang]

Still see the problem on an old 15" Macbook Pro with USB ports. It runs macOS 10.14.5 and the problem occurs right after a software update.
Both Virtualbox version 6.0.6 and version 5.2.28 fail to install. Oracle isn't showing up in Security preferences as being blocked at all.
The main problem is that I lose access to all my existing VMs!

It turns out that adding editor Oracle in the list of security kext manually works well for me.

Refer to stackoverflow questions/55004803/install-virtualbox-6-on-mac-10-14-mojave-failed-with-kernel-install-error. quoted below.

Install Virtual box on mac OS +10.3 with security kernel can failed. After you have this message :

Kernel driver not installed (rc=-1908)

because you have to add editor Oracle in the list of security kext.

If you have chance, you can see the ask for authorisation in Preference -> "Security and Privacy".

But it was not my case. I want to share the solution, because it was a really pain for me: Add Oracle editor in this authorization list.

Restart your mac in Recovery mode (cmd + R)

Then open a Terminal and enter : spctl kext-consent add VB5E2TV963

Restart your mac.

VB5E2TV963 is the code for oracle.

It's ok for me with Mojave and Virtual Box 6.

[Sy]

Hello, Yesterday I downloaded VirtualBox 6 and tried to install on my iMAC which is running macOS Mojave 10.14.5, I've created a post on superuser, link below:

https://superuser.com/questions/1436347 ... nder-macos

Of the many posts I found online with how to solve this my Security & Privacy dialog does not give me the option to allow VirtualBox, how can I resolve this?

Thank you,

[spacebug]

I'm also using Virtualbox 6.0.6 on macOS 10.14.5

I followed the posst from Jack Wang and I got it to work. Thank you!

[Sy]

Sorry, I found the post and tried it...I got:

kext_consent: invalid API object reference

Also it would appear the instruction isn't quite correct either as I had to prefix add with --, so the line should read:

spctl kext_consent --add VB5E2TV963

Doh!

Its:

spctl kext-consent add VB5E2TV963

That is accepted...trying now.

Thank you, it works!!!

[Darius123]

so 6.0.8 fails to install on macOS 10.14.5

Screenshot 2019-05-15 at 07.49.36.jpg (35.72 KiB) Viewed 34202 times

maybe something to do with extensions notarization? (or rather lack of it)

https://developer.apple.com/documentati ... stribution

as per link above:

"Beginning in macOS 10.14.5, all new or updated kernel extensions and all software from developers new to distributing with Developer ID must be notarized in order to run. In a future version of macOS, notarization will be required by default for all software."

[Darius123]

Good news is that "spctl kext-consent add VB5E2TV963" in recovery mode saves the day.

It would be nice though if VBox devs solve this in the future.

[Amarok2]

Hello,

I just solved this problem by disabling SIP.

I run Mojave 10.14.5 (fresh update), and try to uninstall completly VirtualBox, then trying to reinstall it from the latest 6.0.8 version.
Failed to install .

So i reboot my mac on the recovery partition, [ CMD ] + [ R ] at startup, launch the Terminal from the Utilities Menu and type the following command :

Code: Select all

csrutil disable

.
Then reboot my mac normaly and the VirtualBox installer works fine (and the app too) !
After the installation, you should reactivate the SIP by redo the same action, and typing

Code: Select all

csrutil enable

Hopes it solved the problem for you.

[Darius123]

Hello,

I just solved this problem by disabling SIP.

IMHO "spctl kext-consent add VB5E2TV963" in recovery mode is more practical as should work with future VBox updates.

[Aegrotatio]

This is ridiculous how often the MacOS installation fails.

Why can't we sort this out once and for all?!

All my MacOS hosts are now dead due to the May 14 update.

[AlphaZero]

Hi everyone. I was having holy Hades with this 6.0.8 on OSX 10.14.5. I followed all tutorials and still never worked. I was finally able to uninstall it using the Unistall script and successfully loaded 6.0.4 without failing. This is the fix until a newer signed version of the KEXT comes out. Again, load 6.0.4 from prior builds.

I'm so dependent on VB for my work, this was a major stressful issue for me and I'm finally glad it works!!!!!!

[LotusSound]

Good news is that "spctl kext-consent add VB5E2TV963" in recovery mode saves the day.

Thanks