Few information are provided, just that an error occurred preventing the installation to complete and that's it ! No error code, no detail.
#VIRTUALBOX FOR MAC OS SIERRA MAC#
Once the mac was "clean of Virtualbox", I tried again re installing it, but I'm still facing the same error at the end of installation. but unfortunately, that failed ! Thus, I tried a clean deinstallation (using the provided script in the DMG, removing the app and clearing the trash bin) with a restart.
#VIRTUALBOX FOR MAC OS SIERRA INSTALL#
So, since still blocked now, I tried to re install VB as you advised. In my case however, I upgraded from High Sierra public betas to High Sierra GM and then to latest beta (10.13.1), without reinstalling Virtual box, since, for me, it kept working until that latest beta (I'm not sure it did on the GM, I had no time to test it on the GM.). I understood that chances to get Dileep's method working was more or less random but it was worth giving it a try. Anyway, I got a better one for now and fixed the issue.ĭileep Pattayath bcassid Posts: 17 Joined: 29. Sep 2017, 09:15ĭpattayath wrote:Yeah, talking to Apple sounds like a promising solution. I know this may not be a clean solution but interim and will definitely get you going till Oracle adds the ability to handle "User Approved Firmware extension" with a graceful approval prompt or something like that.ĭileep Pattayath dpattayath Posts: 2 Joined: 26. Rebooted my machine and hurray!! its working. Copied the "Contents" folder from "Show package Contents" of VirtualBox to the above directory.ģ.
Created a kext entry under /Library/Extensions with the name "VirtualBox.kext" (Please note this is a directory).Ģ. So this is what I did to get around this:ġ. Still said "installation failed" at the end of the process without any specific message and while trying to load a Vm, showed the message "Kernel extension not loaded.". Thanks for thatĮven after giving approval (as per the above document says), It didn't work. The document mentioned in his reply explains, why its not working and lead to possible solution. Anyway, I got a better one for now and fixed the issue. Yeah, talking to Apple sounds like a promising solution.
0 kommentar(er)
