VMware “Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.”
Update: According to many of the comments, a number of people are finding this post when searching for help with a VM that will not power on. This post was written for a specific scenario related to missing snapshot files, but if you are merely trying to power on a VM that was working recently, you may be able to resolve the problem by simply delete any folders containing .LCK in the name from your virtual machine’s folder, which would preserve any snapshot data.
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 made to the virtual machine since the last snapshot:
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”
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.