Persistent "The application 'VirtualBox' can't be opened" error

[spark89]

Hello there,

Overnight my VirtualBox seemed to have stopped working. Some relevant information:

MacBook Pro (13-in 2017 model)
macOS Sierra v10.12.6 (latest version)
Genymotion v2.11.0 (latest version)
VirtualBox v5.2.7 (latest version)

The issue:

I've been trying to startup a virtual machine through Genymotion but I kept getting the incompatible state error message. I was suggested to open VirtualBox to shut off the virtual machine, but each time I try, VirtualBox fails to startup and throws me an error: The application "VirtualBox" can't be opened.

I've tried to shut down the virtual machine through the terminal via

Code: Select all

VBoxManage controlvm "device name" poweroff

but then I get an error stating that the virtual machine is not currently running.

Naturally, I try starting the virtual machine via

Code: Select all

VBoxManage startvm "device name"

but then I get a

Code: Select all

NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

.


Attempts to solve:

I've deleted the virtual machine through Genymotion and recreated a new one, and the issue persists.
I've restarted my computer and the issue persists.
I've uninstalled VirtualBox through the uninstall tool in the dmg and also uninstalled Genymotion and reinstalled both of them and the issue persists.


Can someone please help me with this issue? It would be greatly appreciated, thank you!

[socratis]

You have two options:

1. Ask Genymotion.
2. Remove Genymotion, clean up your system (not the VMs), install purely/solely VirtualBox.

[spark89]

Hi socratis,

Thanks for the reply. I've uninstalled Genymotion and the issue persists. I've uninstalled VirtualBox and reinstalled it without installing Genymotion and the issue persists. I don't think this issue has anything to do with Genymotion so I'm doubtful that contacting them would yield any fruit.

[socratis]

OK, glad we can focus on VirtualBox alone. Post the output of your installation log. If you don't have one, re-install VirtualBox and grab one:

1. Reboot.
2. Download the latest release, or the latest test build (https://www.virtualbox.org/wiki/Testbuilds), if you don't already have them.
3. Mount the DMG from the previous step. Run "VirtualBox_Uninstall.tool". Make sure there are no error messages. If there are, please post them, exactly as they appear.
4. Reboot.
5. Mount the DMG from the previous steps. Double-click the "VirtualBox.pkg". As soon as you start the installation, press Cmd+L to show the log. Select "Show All Logs" from the drop-down menu. Before the last step of the installation (Done), click the "Save" in the log window. ZIP and attach that file.
6. Start VirtualBox. If it crashes, open Console.app and look at "~/Library/Logs". Is there a VirtualBox related log with the current date/time? ZIP and attach that file as well.

And I'd like the output of the command:

• kextstat | grep -v com.apple

[spark89]

Hi socratis,

I followed your steps.

3. No error messages
5. See attached

installerlog.zip

Installation log

(3.35 KiB) Downloaded 15 times

6. The app crashed, and there were no logs related to VirtualBox in ~/Library/Logs. There is, however, a crash log from when I was first trying to troubleshoot this issue earlier today. Crash logs no longer generate. See attached

crashlog.zip

Crash log

(16.2 KiB) Downloaded 10 times

kextstat output - see attached

terminaloutput.zip

Terminal output

(1.29 KiB) Downloaded 11 times

Thanks for your time looking into this matter, I really appreciate it.

[spark89]

Bump - any suggestions?

[socratis]

com.confer.sensor.kext (3.0.1fc20)
com.bit9.cbsystemproxy (1712.22.61fc3)
com.carbonblack.CbOsxSensorProcmon (1712.22.61fc3)

Try without these extensions/install apps. For example: https://apple.stackexchange.com/questio ... confer-app