• TwitterFacebookGoogle PlusLinkedInRSS FeedEmail

Virtualbox Error Not Registered

04.08.2019 
Virtualbox Error Not Registered 8,5/10 9300 reviews

I have tried to install VirtualBox 5.1.28 to macOS high sierra but it fails every time with the following screen:

After some looking around I found this thread and I did indeed see that it was blocking VirtualBox from installing.

Virtualbox Error Windows 10

After clicking allow and then trying to run the VirtualBox installer again it just fails again with the same generic error message and the same Security warning reappears in the 'Security and Privacy' settings.

I tried to also run the pkg install from the terminal to see if I could get more information about why its failing but it doesnt help.

I'm running Arch with 3.6.10 kernel, When vboxpci module is loaded, it tells me vboxpci: IOMMU not found (not registered), But I checked my kernel config, I have the INTELIOMMU set already (I u. Try to check your VirtualBox Logs probably they will have some helpful information for you. For me - though the answers above saying that windows updates are causing the problem with VirtualBox- I only had to install windows updates to get the problem solved. And I believe that windows updates were the cause for the issue for me too.

The VirtualBox application does appear to install and it can be launched however nothing functions.

Does anyone have any ideas how to solve this?

BradErzwhBradErzwh
1,9263 gold badges4 silver badges7 bronze badges

6 Answers

Managed to solve it.

  • Eject the VirtualBox image from: Finder > Devices

  • Now allow the exception in: System Preferences > Security & Privacy

  • Finally but not least click Allow button so that way the developer with the name 'Oracle America, Inc' will be accepted and the installer using that certificate will run just fine (basically this installer is signed using 'Oracle America, Inc' certificate so we are required to enable it use on our machine first)

  • Then try to install from the .dmg again so that it remounts the device.

Now its working fine for me.

BradErzwhBradErzwh
1,9263 gold badges4 silver badges7 bronze badges

The answer at the following link worked for me. It required running the script provided by dstroot, approving the kext in Security & Privacy and then installing with brew cask reinstall --force virtualbox --verbose --debug. https://github.com/caskroom/homebrew-cask/issues/39369

running-codebaserunning-codebase

For those still struggling with this issue:

IF YOU ARE CONNECTING VIA REMOTE DESKTOP OR SCREEN SHARING or have any other mouse emulation running: It is not possible to actually click the Allow button in this mode!!

So do the following:

  1. Run the installer until the location prompt
  2. open System Preferences
  3. Take a screenshot (CMD+SHIFT+3)
  4. Open the screenshot with Preview, and select from top left to the button, and note down the coordinates
  5. Then open Script Editor, and run the following line of code:tell application 'System Events' to click at {890, 460}Use the coordinates from step 4. and make sure you don't move the Preferences window, and that no other window is overlaying the button. (It could be you need to give Script Editor Accessibility permission, but it will prompt you)

Now the button is actually clicked, and you can allow 'Oracle America, Inc.' to install. You might be prompted for a reboot. Then run the installer again and everything should work as expected!

RoelFRoelF

If the GUI solution does not work, reboot in Recovery mode and enter spctl kext-consent add VB5E2TV963, then reboot in normal mode and install should be ok.

Liviu IonescuLiviu Ionescu

For some reason when I clicked 'allow' it felt as if the button 'did nothing' but then when I tried it a third time the button 'took' (after which point it always worked). Weird.

More ideas:

reboot into safe mode, try the allow button there

command line: sudo spctl --master-disable

This is a community wiki feel free to add some more ideas here.

rogerdpackrogerdpack

I saw a quick note in one of the messages here or in another thread and it was the critical piece I was missing.

When I had the Security & Privacy dialog open, the Apply button visible and clicking on the button and there was no apparent action. The prompt still remained. I needed to WAIT longer before trying the Apply. I found I waited 20 minutes until the button actually worked (the prompt went away).

Virtualbox Error Not Registered
Kevin BuchsKevin Buchs

You must log in to answer this question.

Virtualbox Error Not Registered Name

protected by CommunityMar 30 '18 at 3:43

Virtualbox error not registered to open

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged macossecurityvirtualboxhigh-sierrakernel-extensions .