Virtualbox Settings For Mac Os X Sierra

To use VMware Workstation 12 Player instead of VirtualBox, see how to Install MacOS Sierra 10.12 on VMware Player on Windows. First, you’ll want to download and install VirtualBox v5.x. Next, you’ll want to download the VMDK MacOS Sierra image (choose one of the options below).

MacOS High Sierra 10.13 introduces a new feature that requires user approval before loading newly-installed third-party kernel extensions (KEXTs). When a request is made to load a KEXT that the user has not yet approved, the load request is denied. Apps or installers that treat a KEXT load failure as a hard error will need to be changed to handle this new case. Approval is automatically granted to third-party KEXTs that were already present when upgrading to macOS High Sierra. This issue affects anyone installing VirtualBox for the first time on a fresh macOS High Sierra 10.13. This effectively breaks our fully automated installation process on macOS, since the user now has to perform a manual approval and then restart the installation (reboot and rerun the installation in some cases) References: • Originally posted with details in • Official note from Apple: • StackExchange: • Homebrew/Cask: • VirtualBox forums: • VirtualBox forums: covers the manual steps necessary to install VirtualBox successfully. How to update the driver for my graphics card on a boot camp mac running windows 7. Actually, it isn't just for the first time.

I've had VirtualBox installed for quite a while. It took a lot of steps to get to this Issue, but the short of it is this: I had VirtualBox installed. I upgraded to 10.13.4 I ran vagrant up on a new VM. It failed to launch. I attempted to reinstall vagrant. I attempted to install an update for VirtualBox (which kept failing to install properly.) I found this issue. I reinstalled the update, accepted the security exception, and now the rest is good.

TL;DR: This impacts existing installations as well. I resorted to disabling System Integrity Protection to get past this installation failure, but I later figured out what was causing my VirtualBox installation to repeatedly fail. TL;DR — remote access or ANY 3rd party mouse or keyboard software may trigger High Sierra to ignore your mouse click on the 'Allow' button.

The VirtualBox installation may repeatedly fail if clicking the 'Allow' button in System Preferences appears to have no effect. High Sierra seems very paranoid about only accepting mouse clicks from the local computer and will reject mouse clicks over VNC / Remote Desktop, and ALSO for locally attached mice/keyboards if any 3rd party mouse/keyboard/touchpad software is installed. In my case I believe the small keyboard app 'High Sierra Media Keys' (which has no mouse-related functionality) was causing OS X High Sierra to ignore my mouse clicks on the 'Allow' button. So the VirtualBox kext was never allowed and repeated installation attempts would never report success, even after rebooting. VirtualBox appeared to be installed but would fail when trying to boot a virtual machine, saying the kext was not loaded.

I was able to install VirtualBox after disabling SIP (restart from Recovery partition and run csrutil disable at the Terminal) and it remained functional after re-enabling SIP. However subsequently experiencing the same unresponsive 'Allow' button when trying to install a different kext made me realize this issue was not limited to VirtualBox. Following dansanduleac's advice in I was able to finally click the 'Allow' button using the keyboard. Other people have had success triggering the button click with AppleScript, but that did not work for me. If you can't get the 'Allow' button to register, you probably have some mouse/keyboard software that is causing High Sierra to ignore your click! High Sierra seems very paranoid about only accepting mouse clicks from the local computer and will reject mouse clicks over VNC / Remote Desktop, and ALSO for locally attached mice/keyboards if any 3rd party mouse/keyboard/touchpad software is installed. That's by design.

Apple enabled only local mouse clicks for High Sierra inside 10.13.4 which blocks out clicking via any remote interface. So the user in front of the machine has to accept what is happening. It's annoying as crap, but I guess it's their way of stopping malware, etc. Edit: I've also noticed that the remote block trigger sometimes gets prompted if you have some form of wacom driver installed, as I tried clicking with a wacom pen one day and it wouldn't. Switched to the mouse attached, and it went straight through. So clearly Apple still have issues with this function.

I had the same problem as PierBover but the solution from skhilko didn't work for me. So I remembered another similar method I used when I tried to install a blocked safari extension: • Open System Preferences/Keyboard/Shortcuts • Activate 'all controls' at the bottom • Now go back to Security/General and press tab until the allow button is highlighted (maybe you have to unlock all settings first) • Press Space to simulate a mouse click • The allow button now should have disappeared • Run brew cask reinstall virtualbox --force in Terminal or run the installation again. • Boot into recovery using command+R • Open terminal when in recovery • Run csrutil disable; reboot • Install VirtualBox again This drove me nuts for hours today. I tried to install, I was prompted in Security and Privacy to allow Oracle. I allowed it to install the KEXTS, but to no avail I couldn't get it running using any known method. So I thought this really might be a VirtualBox issue, and ended up buying Parallels Desktop for Mac. That didn't work to my surprise, and contacted their support team.