(got the machine on Thursday, had installer issues on that same day) The first times I ran the installer, auto-updates had already been enabled, but as far as I know, no updates arrived between the time I first ran the installers, and the time I disabled auto updates. I disabled all automatic updates, rebooted many times, and experienced the same failures during installer runs, with the same errors reported in install.log. When the system came to me automatic updates were enabled.
May 2017, 20:21Ģ) if your updates are on "Automatic", because there were problems with that before. I assume any usb access within my vms will be broken, but that is OK in my case.Ĭan anyone confirm seeing this issue? Is there a better workaround? Now I can happily run 5.1.22 on my 10.12.4 host. May 13 10:56:13 tnorris-macOS installd: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “VirtualBox.pkg”." UserInfo=.kext" May 13 10:56:13 tnorris-macOS installd: PackageKit: allow user idle system sleep May 13 10:56:13 tnorris-macOS installd: PackageKit: releasing backupd May 13 10:56:12 tnorris-macOS install_monitor: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr postflight: /Library/Application Support/VirtualBox/VBoxUSB.kext failed to load - (libkern/kext) not loadable (reason unspecified) check the system/kernel logs for errors or try kextutil(8). Installing (either version, using the dmg downloads) always ends with a failure, install.log always contains the failure message on loading VBoxUSB.kext:Ĭode: Select all Expand view Collapse view May 13 10:56:12 tnorris-macOS installd: PackageKit: Executing script "./postflight" in /private/tmp/PKInstallSandbox.Xn8SB0/Scripts/.CoySf2
I've resolved it, but wanted to share my experience, since it's been a bit painful to debug. I've had a horrible time time installing either 5.1.22 or 5.0.38 on a new macbook pro.
0 kommentar(er)
