VirtualBox 5.1.18 quit unexpectedly - VB will not even start

[BetoGDL]

Hello...

This morning I started experiencing problems to start the VirtualBox application (the application - I have not even had the chance to start my existing VM ):
The program will crash without even initializing, and the OS pops up the following Problem Report:

Process: VirtualBox [1609]
Path: /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
Identifier: org.virtualbox.app.VirtualBox
Version: 5.1.18 (5.1.18)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: VirtualBox [1609]
User ID: 501

Date/Time: 2017-04-03 08:20:02.174 -0500
OS Version: Mac OS X 10.12.4 (16E195)
Report Version: 12
Anonymous UUID: E5136DC4-CC7E-FC8B-A526-A44FBB3F973A

Time Awake Since Boot: 5300 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [0]

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: Assertion failed: Block was expected to execute on queue [com.apple.main-thread]
crashed on child side of fork pre-exec

Host: macOS Sierra (v10.12.4, last update applied 2017/03/27)
VirtualBox had been updated to 5.1.18 since 2017/03/21, and I had been using regularly, and successfully after both VirtualBox and macOS updates. It just started failing today as described above, and I am not aware of any other alteration to this system.

I will deeply appreciate any guidance which could be provided to solve this problem.
Please, let me know if further information is required.

[socratis]

10.12.4 you say, right? Hmm, that came out the other day, and it has issues even getting installed as a guest VM, so it's not impossible that something changed in the OS, although highly unlikely in a such a small update.

• How was your update performed? Automatically? Manually from the AppStore? By using the 10.12.4 stand-alone updater?
• Please zip and attach the whole .crash file.
• Please post the output of the following command in the Terminal:

  • kextstat | grep -v com.apple

[BetoGDL]

Hello...

macOS was updated via APPstore

This is the kextstat output:

Code: Select all

kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  149    3 0xffffff7f83308000 0x61000    0x61000    org.virtualbox.kext.VBoxDrv (5.1.18) 9A14468B-0B16-3E51-B0D6-12EFA245CB19 <7 5 4 3 1>
  151    0 0xffffff7f83369000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.1.18) 1017E84D-BE4D-3718-86FC-1AF127974058 <150 149 41 7 5 4 3 1>
  152    0 0xffffff7f83371000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.1.18) 126732E2-A69F-3BB2-A666-DA94E875A105 <149 7 5 4 3 1>
  153    0 0xffffff7f83376000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.1.18) B7C44747-CB0A-3D1F-8943-A3DD0866E53F <149 5 4 1>

And this is the .crash report:

VirtualBox_2017-04-03-103024_BetoGDL-MacBook-Pro.crash.zip

".crash" report for reported problem

(16.14 KiB) Downloaded 10 times

Please, let me know if further info is needed.

Thanks, and regards!

[socratis]

I installed and launched VirtualBox on a 10.12.4 VM, with no problems, so we could rule out failure for a factory setup system. So, there must be something wrong with your system. As a first measure, mount the 5.1.18 DMG and uninstall VirtualBox. Reboot and re-install VirtualBox. See how that goes...

[BetoGDL]

As advised, I uninstalled VirtualBox, then rebooted, then reinstalled VirtualBox...
I am now able to start VirtualBox and available VMs with no oher noticeable problem.

Thanks a lot for your help!

[socratis]

Nice!
Because that was the one and only idea I had at this point