I have a Windows 7 Professional 64-bit virtual machine running on a Ubuntu 14.04LTS. I deleted an old snapshot of this VM. It took over 30 minutes to delete and exactly at the end of the process the laptop unexpectedly shut down. After restarting the laptop, I tried to start the virtual machine and got the error:

Failed to open a session for the virtual machine Main.
Could not open the medium '/home/user/VirtualBox VMs/Main/Snapshots/{eeeeeeeee-ffff-4144-b555-bbbbbb}.vmdk'.
VD: error VERR_FILE_NOT_FOUND opening image file '/home/user/VirtualBox VMs/Main/Snapshots/{eeeeeeeee-ffff-4144-b555-bbbbbb}.vmdk' (VERR_FILE_NOT_FOUND).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: Medium
Interface: IMedium {555bbb-a3a6-4b9b9-4949-acacacac}

Any idea on how to recover it?


2 Answers 2


Problem is that once a snapshot file is missing, Virtualbox will not allow you to delete the snapshot from the GUI. To "force-delete" the snapshot you will have to let Virtualbox believe the file is not missing. So just copy an existing one and rename it to the missing file's name. Then u need to set for each new file its correct UUID and its parent UUID. For example:

VBoxManage.exe internalcommands sethduuid "path\{c87e9357-5d1a-4d00-84d8-7b43293ab92e}.vmdk" c87e9357-5d1a-4d00-84d8-7b43293ab92e
VBoxManage.exe internalcommands sethdparentuuid "path\{c87e9357-5d1a-4d00-84d8-7b43293ab92e}.vmdk" c9e9b5a8-fb3f-42f8-aeb7-4458bf92f625

All the missing filenames and their UUIDs you can find in the Virtual Media Manager.

  • This fixed it for me, thanks. I think this is just BS that you need to jump through the command line to fix this.
    – Allison
    Aug 20, 2015 at 19:57
  • This worked for me as well
    – Jim Factor
    Aug 21, 2018 at 1:03
  • How do you find the “correct” UUID and parent ID? Sep 13, 2019 at 18:17
  • @WhiskerBiscuit File -> Virtual Media Manager. You can also examine the error message or .vbox file. Sep 13, 2019 at 19:11

Ok, I found a solution!

I cloned the corrupted virtual machine with virtualbox manager and the clone started without problems, after it, one of the disks was unreadable, and running a chkdisk /f corrected it.

  • 1
    I tried to clone it, but got the same error as when I tried to open it. Oct 13, 2016 at 7:37

You must log in to answer this question.

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