VirtualBox error "Failed to open a session for the virtual machine"

Question

I have a virtual machine with Windows XP with a clean installation. I set it as immutable to create a differential machine, so I create a new virtual machine, select the immutable hard disk and create a new snapshot in the new virtual machine folder.

However, when I try to start the virtual machine I get this error:

"failed to open a session for the virtual machine".  Código Resultado:  VBOX_E_INVALID_OBJECT_STATE (0x80BB0007) Componente:  ProgressProxy Interfaz:  IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913} 

What is the problem? until now I can use differential virtual machines without problems. I have installed the last version or VirtualBox v4.3.4 and the problem persists.

If I set the hard driver as normal and I create a new virtual machine and select this hard drive I don't have any problem.

EDIT: I use the same virtual disk and do the same steps in another computer and it works fine. I think that the problem is the VirtualBox of my computer with the problem, but I try to uninstall the program and reinstall it and the problem persists, so I don't know how to solve the problem.

EDIT 2: if I set the virtual harddrive as multiattached instead of immutable, then it works fine. In my case is enough, but I know that it would be work as immutable because it was work until now and it works in another computer.

I try to create a new user in windows to try if the problem if with the configuration of my account, but the problem persists. So I think that some general configuration of VirtualBox has been corrupted and I am not be able to repair it.

I would like to know if there is any solution to use a immutable hard drive, because I would like to solve the problem with VirtualBox, although by the moment the multiattached hard disk is enough.

Answer 1

I had the same issue, I tried editing the VM but it wasn't letting me save it. So I tried the following:

1. Tried editing the VM to change RAM/CPU etc, but it wasn't letting me save it
2. Deleted the vm (not the data) and tried adding it again, didn't fix it
3. Tried moving the vbox file to another directory and import it, but it didn't let me move the vbox file so I realized there's a virtualbox process running that's holding a lock on it. So I killed that process and started it again and my VM booted