Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Guest: Ubuntu
Guest VM Name: WordpressThemeDevBox
Host: Windows 7 64-bit Ultimate
VirtualBox Version: 4.1.2 r73507

I shut off my guest and removed the Current State snapshot using the Restore Snapshot button.

After the process completed I returned to the Oracle VirtualBox Manager and the following error was displayed in the right hand panel:

The selected virtual machine is inaccessible. Please inspect the error message shown below and press the Refresh button if you want to repeat the accessibility check:

Could not find an open hard disk with UUID {73231db-6014-4c49-b092-eac75c33f31d}
Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Compoent: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

I checked in %USERPROFILE%\.VirtualBox\Machines\WordpressThemeDevBox\Snapshots\ and the vdi file {73231db-6014-4c49-b092-eac75c33f31d}.vdi is present in that directory.

I also found this thread over at the VirtualBox forums, but it's refering to version 4.0.4 and they keep talking about a .vbox file which I can't find in my 4.1.2 installation.

Additionally I found a bug pertaining to version 4.0.4 that appears similar to what I am experiencing.

Is there any way of fixing this using VBoxManage or editing one of the xml files like VirtualBox.xml or WordpressThemeDevBox.xml?

Additionally here is more information via paste-bin:

share|improve this question
up vote 0 down vote accepted

Okay figured this out. While I never did find out which vdi file I was using from the XML files, I did eventually find the correct vdi file. I used VBoxManage to clone the base vdi file, discarding the snapshots, and created a new vm.

share|improve this answer

My solution is similar to yours, except that I couldn't use the VBoxManage because the entry was already gone there. Also I haven't had any snapshots that might have interfered with my below solution path. I've a Mint 17 host and Win 8 guest and vBox 5.0.2.

I removed the VM from the VM-List (don't delete from Disk!) created a new VM and instead of creating a new VDI file during the creating of the new VM, I used the existing VDI file from the original VM.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.