The VM Session was Closed Before Any Attempt to Power it on, VirtualBox 3.2 Error

For some reasons, if the Oracle VirtualBox is giving this error while powering on a virtual machine, this simple trick going to be useful. Today I had an issue when powered on one of the VM with the following message;  “The VM session was closed before any attempt to power it on“, then closed by itself. It is a strange behavior. Finally, I managed to fix with the following method. Now VMs are fine.

I tried the following methods, but failed.

1) Tried several snapshots which gave me the same error.

2) Restarted Host computer.

3) Stopped all VirtualBox services and restarted.

All failed, finally, Google helped me to find out this thread in VirtualBox.

If you get The VM session was closed before any attempt to power it on message and Virtual Machines cannot be started, don’t panic. Don’t do anything. Just take a snapshot.

The working Method

Go to Storage option of VM; remove hard disks and CD drives.

Remove Storage

Start Virtual machine now. At least now you could see Oracle VirtualBox screen, but as expected boot medium error you will get. Shut down VM and add storage disks as it was earlier.

Now switch on the virtual machine, which will start normally.

I didn’t try much to find out the cause. VirtualBox may come up with some fixes for this issue.  But, I can confirm this method worked for me. This method can work on any host such as Windows or Mac.

31 thoughts on “The VM Session was Closed Before Any Attempt to Power it on, VirtualBox 3.2 Error”

  1. Had the same error after upgrading. CD was still pointing to the Virtual Box Guest Additions CD (from the previous version). I changed it to empty and it booted. So little bit faster than removing and re-adding all the drives – maybe it will work for you!

  2. Hi there, I clicked change and then changed the sort order of the boot-steps and have set the HD first. Then it worked as well.

  3. It did not fix ANYTHING!!!!! I removed ALL storage devices in the VM, tried to boot, and I got the message again. The only workaround is to create a NEW VM and reinstall everything! What is the point of giving false information? This is getting me extremely MAD! I cannot rely on anything on the Internet, because EVERYTHING is FALSE and OUTDATED!!!! Before I got stuck with this, the VM was extremely slow. I took ages just to install something in the virtual Ubuntu, which was periodically hanging. I know that Ubuntu itself is a possible cause for the problem, but now, that is VirtualBox that refuses to start the VM with my Ubuntu, so I would have to restart the installation again. It’s been almost TWO HOURS I am trying to install the Ubuntu guest, and now I would have to start again.
    What can I do to install a virtual machine if VirtualBox does NOT work at ALL?

  4. Hi, I encountered the same error. I tried the solution but the error still comes up.
    Just rebooting the host PC, starting VB solved the problem…

  5. Thanks for the tip. What worked for me and is worth trying first, if you have a saved machine state, is just discarding it — Machine – Discard.

Comments are closed.