OSX (Yosemite, El Capitan) crashes and restarts every time I try to:

1) start a machine VirtualBox (5.0.6) and BlueStacks concurrently (no matter which is started first)

2) run BlueStacks, close BlueStacks, start any virtual machine in VirtualBox

VirtualBox machines run normally only if BlueStacks had not been started after last reboot. And BlueStacks starts if VirtualBox was closed before. So direct reason for system crash seems to be VirtualBox, while the cause seems to be BlueStacks (I understand that BlueStacks uses VirtualBox components)

I don't necessarily need to run them concurrently, but would be happy if the VirtualBox did not cause system to crash.

Can I (and how) close BlueStacks so that no "leftovers" remain?

1 Answer 1


I found this reply from VirtualBox users:


xactly. And we can do absolutely nothing about it. BlueStacks uses VirtualBox code without any attempt to coordinate with Oracle (which they certainly are allowed to do under the terms of the GPL). It is unfortunate that they mess up existing VirtualBox installs.

It is generally not possible to have two different VirtualBox versions installed on a system, unfortunately that is what BlueStacks effectively does. If this is a problem for you, please contact BlueStacks as Oracle has no relationship with them.

  • First: it is a response to my question. Second: it does not provide an answer to the question: how to deal with the problem (clean up after BlueStacks). Altogether it should be a comment.
    – techraf
    May 31, 2016 at 22:17
  • You are right, I'm sorry!
    – Admdebian
    Jun 2, 2016 at 10:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .