Trouble installing 5.1.22 on OS X 10.12.4

[Danger]

Like a number of other people on the forum, I have been having some trouble installing VirtualBox on my mac.

A bit of information about how I arrived here:
- I had VirtualBox installed a few days ago and it was working well.
- I encountered a problem with Vagrant and followed the advice to uninstall (using VirtualBox_Uninstall.tool) and reinstall VirtualBox
- The first time I tried to uninstall VirtualBox, I ran into an issue removing a kext and proceeded to remove it (using ktextunload, I believe)
- I am not unable to install VirtualBox following the following procedure: Run VirtualBox_Uninstall.tool twice, restart, run VirtualBox_Uninstall.tool again, install using VirtualBox.pkg.

I do not have automatic updates enabled on this host.

I am attaching the zipped logs

[Danger]

I definitely don't know my way around kernel extensions, but think that they may be the root of these troubles.
The install logs mentioned trouble with VBoxUSB.kext and another thread (t=80758) meant I looked into it a little:

Code: Select all

$ sudo kextutil -v /Library/Application\ Support/VirtualBox/VBoxUSB.kext
Password:
Defaulting to kernel file '/System/Library/Kernels/kernel'
/Library/Application Support/VirtualBox/VBoxUSB.kext - dependency 'org.virtualbox.kext.VBoxDrv' not found.
/Library/Application Support/VirtualBox/VBoxUSB.kext - dependency 'org.virtualbox.kext.VBoxDrv' not found.
/Library/Application Support/VirtualBox/VBoxUSB.kext - dependency 'org.virtualbox.kext.VBoxDrv' not found.
Diagnostics for /Library/Application Support/VirtualBox/VBoxUSB.kext:
Dependency Resolution Failures:
    No kexts found for these libraries:
        org.virtualbox.kext.VBoxDrv

In experimenting and trying to invalidate the cache using `sudo touch /System/Library/Extensions/`, I did not solve the problem, but I did manage to break sound and bluetooth support on the host. I eventually was able to fix the sound and bluetooth by running

Code: Select all

sudo kextcache -system-prelinked-kernel

I now wonder if the issue is that I need to do something like the system-prelinked-kernel, but specify a path to /Library/Application Support/VirtualBox and its kext files. Something like this, but I'm now a little scared to break more things.

Code: Select all

sudo kextcache -prelinked-kernel /Library/Application\ Support/VirtualBox/VBoxUSB.kext

Lastly, this obviously all relates to the state of the host after the failed installation attempt, but without running the uninstall tool as that removes all these files.

[socratis]

Until I completely evaluate the situation, please stop using 'sudo' like it's bread, learn the consequences, re-install OSX and log in as not-the-owner. Then we can talk about the failed systems' failure. Till then, not even Apple knows what you've done.