Can no longer install VirtualBox

Hi,


I've been using VirtualBox 6.1.12 up to a few days ago, on my Mac Pro 2013 with High Sierra 10.13.6. After trying to install VB 6.1.14, I received an error message leading to kernel protection.


I tried everything to make it work, with no success. The Allow button didn't appear in the Safety control panel. I manually allowed it via Terminal with the "kext-consent" command (Oracle was allowed, but still VB didn't start). I cleaned all the caches, went to Recovery mode to clean the kext cache and the StagedExtension folder. Nothing.


I tried to downgrade to VB 6.1.12, but this one could no longer be installed, still for kernel protection reasons. When I copied the VB 6.1.12 kexts from a TB backup (booting from an external drive), the Mac removed them when booting again from the main drive.


This issue is ongoing, but there is no solution offered in the VirtualBox forum. Maybe someone can help letting me understand if there is some trick on the Mac, to have those kexts be allowed?


Thank you!


Paolo


Mac Pro

Posted on Sep 26, 2020 9:20 AM

Reply

Similar questions

17 replies

Sep 26, 2020 4:04 PM in response to PaoloT.

What does a Get Info on the boot drive report for free space?


What does Disk First Aid report for the drive?


Is anything locked in this path?


/private/var/db/KernelExtensionManagement/Staging/tmp.oXkkJq


Let’s see if there’s a locked file interfering.

Open Terminal & paste this command in & prefs enter, it’ll ask for an admin password & not echo what you type, wait for it to finish which will be an empty prompt unless it prints out some locked files, or Operation not permitted…

cd /;sudo find . -type f -flags +uchg

Sep 26, 2020 5:16 PM in response to BDAqua

BDAqua, thank you very much for your support!


Get Info says that I still have 1.35 TB in the boot drive.


Disk Utility (run in Safe mode) says that the drive is Ok. Only, it find a series of files with bad flag, and gives a warning (not an error).


I don't have a "tmp.oXkkJq" directory. Inside /private/var/db/KernelExtensionManagement/Staging/ there is nothing. The "Staging" folder itself is not locked.


I cleaned the kext cache with the "sudo kextcache --clear-staging". Maybe this emptied this folder? And is it a good or bad thing?


Paolo

Sep 26, 2020 10:51 AM in response to BDAqua

BDAqua, very good idea! I think these are the relevant lines when the installation fails:


------------------


error 19:43:09.294317 +0200 kernel Sandbox: kextd(58) System Policy: deny(1) file-write-create /private/var/db/KernelExtensionManagement/Staging/tmp.8sNiNp

default 19:43:09.294384 +0200 kextd Error making temporary directory: 1

default 19:43:09.294436 +0200 kextd Memory allocation failure.

default 19:43:09.294476 +0200 kextd Unable to stage kext (/Library/Extensions/NIUSBAudioDriver.kext) to secure location.

error 19:43:09.295440 +0200 kernel Sandbox: kextd(58) System Policy: deny(1) file-write-create /private/var/db/KernelExtensionManagement/Staging/tmp.oXkkJq

default 19:43:09.295488 +0200 kextd Error making temporary directory: 1

default 19:43:09.295545 +0200 kextd Memory allocation failure.

default 19:43:09.295588 +0200 kextd Unable to stage kext (/Library/Application Support/VirtualBox/VBoxDrv.kext) to secure location.

error 19:43:09.324577 +0200 kernel Sandbox: kextd(58) System Policy: deny(1) file-write-create /private/var/db/KernelExtensionManagement/Staging/tmp.0nEHPJ

default 19:43:09.324655 +0200 kextd Error making temporary directory: 1

default 19:43:09.324729 +0200 kextd Memory allocation failure.

default 19:43:09.324785 +0200 kextd Unable to stage kext (/Library/Application Support/VirtualBox/VBoxDrv.kext) to secure location.

default 19:43:09.324819 +0200 kextd org.virtualbox.kext.VBoxDrv was unable to stage properly; failing.

default 19:43:09.420411 +0200 deleted <private>: Successful Request

default 19:43:09.420511 +0200 deleted <private> servicePurgeable returned

default 19:43:09.420547 +0200 deleted dequeuePurge <private> [0x7fc8e4f030d0] no purges queued


default 19:43:10.407402 +0200 trustd cert[2]: AnchorTrusted =(leaf)[force]> 0

default 19:43:10.410071 +0200 authd MacOS error: -67050

default 19:43:10.421602 +0200 trustd cert[0]: ExtendedKeyUsage =(leaf)[]> 0

default 19:43:10.426897 +0200 trustd cert[1]: IntermediateEKU =(path)[]> 0

default 19:43:10.427293 +0200 Installer Trust evaluate failure: [leaf ExtendedKeyUsage] [ca1 IntermediateEKU]

default 19:43:10.450403 +0200 trustd cert[0]: ExtendedKeyUsage =(leaf)[]> 0

default 19:43:10.455483 +0200 trustd cert[1]: IntermediateEKU =(path)[]> 0

default 19:43:10.455843 +0200 Installer Trust evaluate failure: [leaf ExtendedKeyUsage] [ca1 IntermediateEKU]

default 19:43:10.478528 +0200 trustd cert[0]: ExtendedKeyUsage =(leaf)[]> 0

default 19:43:10.483704 +0200 trustd cert[1]: IntermediateEKU =(path)[]> 0

default 19:43:10.484084 +0200 Installer Trust evaluate failure: [leaf ExtendedKeyUsage] [ca1 IntermediateEKU]

default 19:43:10.506614 +0200 trustd cert[0]: ExtendedKeyUsage =(leaf)[]> 0

default 19:43:10.511575 +0200 trustd cert[1]: IntermediateEKU =(path)[]> 0

default 19:43:10.511946 +0200 Installer Trust evaluate failure: [leaf ExtendedKeyUsage] [ca1 IntermediateEKU]

default 19:43:10.562989 +0200 Installer The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.

default 19:43:10.725110 +0200 coreauthd -[LAAuthenticationHintsProvider connectionInvalidated] on <private>

default 19:43:10.725229 +0200 coreauthd -[LAAuthenticationHintsProvider _deactivateWithReply:reply:] on <private>

default 19:43:10.728398 +0200 CommCenter #I handleLSNotitifcation_sync: Application exited: <private>

default 19:43:11.324544 +0200 filecoordinationd Presenter 6E66F2E3-7C34-4305-A0A9-307756515D15 detected non-coordinated event


------------------


All I can understand is that there was a problem with the Sandbox while trying to install the kexts. There is nothing more that can help me to remove the issue, apart for "contacting the software manufacturer". Meh.


Paolo


Sep 26, 2020 3:53 PM in response to BDAqua

What I can say is that I have 2TB of SSD drive, and 64GB or RAM. Disk Utility says the drive is ok, apart for some bad flags in files apparently generated by MS Office. The internal hardware test of the Mac reports that the hardware is fine. EtreCheckPro also reports the computer is fine, and the only major issue is that some kexts (including the ones of VB) cannot be loaded.


So, the numbers seem right, and apparently the hardware shouldn't have serious issues. Unless this is a sign of hidden problems that cannot be found by the normal tests. Is this a possibility?


Paolo


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.

Can no longer install VirtualBox

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