VMware “Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.”

From time to time, I want to copy just the minimum files for a VMware virtual machine: the two .vmdk files and the .vmx file. After moving those files to a new location or deleting a snapshot file, attempting to boot the virtual machine returns the following error message:

Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.
Reason: The system cannot find the file specified.

I’ve found that following the steps below fixes the problem and allows me to boot the virtual machine as it existed at the time of creation. DO NOT USE these steps if you need to retain any changes to the machine:

Open the *.vmx file in a text editor and find the line that refers to the old snapshot file, which will look something like:
scsi0:0.fileName = “XXXXXX-000002.vmdk”
or
ide0:0.fileName = “XXXXXX-000002.vmdk”

Change the value to the filename of the ~1kb .vmdk file (which happens to be the same as the name of the VM). For example, if your virtual machine was named “Windows XP Professional”, the line would read:

scsi0:0.fileName = “Windows XP Professional.vmdk”

Power on the VM. It should boot normally, but because the snapshot file is missing, the machine will boot to an earlier state.

19 Responses to “VMware “Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.””

  1. colorzone says:

    WinMount provides an easiest way to mount VMDK as a virtual disk. You can read or write to the vmdk file without loading the virtual system.
    Here shows you how to do: http://www.winmount.com/mount_vmdk.html

  2. nick says:

    Thanks so much for posting this! You saved me a ton of time!

  3. KenPem says:

    If this happens as the result of a crash, rather than intentionally as a “boot-clean” restart, and you’re trying to recover, then a less-destructive thing to try first would be to delete any .LCK folders within the main VM folder. If this works, you should get your system back in an up-to-date state.

  4. Pietro says:

    I was checking your solution but everything was fine in my file. I ended up doing the same as KenPem. I have deleted the .lck files and it did the trick.

  5. tom says:

    Hello I am trying to recover from a crash of a Vmware 2.0 vmdk file… I’ve tried removing the lck files/folders but this didn’t work it. When the crash happened it recoved itself but reverted back to a snap shot taken 3 months ago… I need to get the files from the last thee months… I restored a backup of this VMDK taken just prior to the crash, but it won’t start in VMware – each time it errors and the Virtual Host service needs to be restarted. Attempting WinMount but it says… Winmount can not mount this file… Is it because it’s version 2.0? How can I reach in this 55GB file to recover some important work done this past month?

  6. Ed says:

    My host application crashed bringing down the guest VM machine. When i try to restart the VM machine it gave the ff. msg:
    “Cannot open the disk. ‘D:\Programs\Virtual Machine\*”
    Reason: Failed to lock the file.

    SOLUTION:
    Delete any .LCK folders within the main VM folder. If this works, you should get your system back in an up-to-date state. Just like the above thread suggested. This works fine for me…Hope this helps anyone out there ;)

  7. Yousef says:

    Delete .LCK folders works for me, Thanks a lot

  8. Mohammad says:

    Delete .LCK folders works for me, Thanks a lot Dude

  9. hari says:

    thanks for the trick ……

  10. Indu says:

    Yes, this worked for me. Thanks a lot.

  11. Paulo says:

    Valeu, ok.

  12. ums says:

    thanx a lot……………… :-)

  13. DaveC says:

    I wanted to thank you for this tip. You saved me hours of time. I know that this was posted years ago, but it still works today. Many thanks Oliver!

  14. Ashraf says:

    Delete .LCK folders works for me, Thanks a lot KenPem :-)

  15. Tintin says:

    where is this directory on Linux? “D:\Programs\Virtual Machine\*”

  16. Lins says:

    .lck folder trick did not work for me. after relaunching the application, the .lck folder reappear again

    The instructions on from the OP is not clear.
    I found all the files, what to do with them?
    is it to change scsi0:0.fileName = “Windows XP Professional.vmdk” to scsi0:0.fileName = “~1kb.vmdk”
    or what exactly.

  17. Riyaz says:

    Hi, I have 2 virtual machine on vmware 1.0.3 doing cluster in a box setup. for that i have created two scsi hdd’s on the first vm server from settings (one for cluster&one for quarom)the problem is that when i start first server its ok its starts with added scsi hdd’s, but when i start second server i get message {cannot open the disk”E:\virtual Servers\SAN\Storage1.vmdk” or one of the snapshot disks it depends on Reason:Failed to lock the file}. my virtual machines are in E:\virtual servers folder and storage goes to folder E:\virtual servers\SAN folder. is there any problem in the settings?.please help. also if i go settings on the virtual server i get (
    memory 384mb/hard disk scsi 0:0/hard disk scsi 1:0/hard disk scsi 2:0/cd rom ide 1:0/floppy/ethernet brigded/ethnernet host only/processors 1.
    is it possible to have scsi shared hdd facility on vmware 1.0.3?..your valuable response will be highly appreciated.

  18. Robin says:

    Big thanks to KemPem, deleting .LCK folders worked for me aswell.

  19. hiper says:

    I had the same problem, but I noticed that my harddisk had no space available, I did a cleaning and VMW is working again.

The comment form requires JavaScript. Please enable JavaScript to submit a comment.