VMWare Workstation error "Unable to open file: '. \x.vmdk": The system cannot find the file specified." (but file is there)

I recently did a full clone of a virtual machine on another computer and then transferred it to my other computer, but there are some problems. It says "Unable to open file: '. \x.vmdk": The system cannot find the file specified." even though the file is clearly there as shown in the screenshot. Extra details:

• Windows 10 (both computers)
• Settings have not changed when I moved cloned virtual machine to the second computer.
• I have access to the first computer where I cloned it.
• VMWare Workstation 14
• I did not run the cloned virtual machine on my first computer before copying it over to the new computer.

It might be the case the location on the new computer is different from the one you copied the file. Can you check the file .vmx opening it with notepad or other text editor and see if the location set for the file x.vmdk is pointing to the wrong folder?

@Ronaldo This is the vmx config file, but I don't know where the location is in the config. All I see is folder sync location and iso file name? i.imgur.com/OsKJeGz.png I don't think this is it either? scsi0:0.fileName = "Duelit-cl5.vmdk"

That's it. I was misled to think the whole path would be specified cause I was not in my computer when I asked you. Now that I am I noticed something about your vmdk file: It's a split disk. I created a VM and was able to reproduce the same error of yours by removing one of the "slices" of my disk. I removed my slice of disk Ubuntu 64-bit-s001.vmdk and instead of complaining about the missing Ubuntu 64-bit-s001.vmdk the error message would say it can't find the file Ubuntu 64-bit.vmdk without the -s001. You seem to be missing a Duelit-cl5-s001.vmdk. Do you have all the disk slices?

You did not run the cloned VM on the first machine before copying it. Have you tested running it there yet to be sure there was no problem on the original clone all along?

Then try copying it once again. Maybe there was some problem on the first time you copied it. And if it doesn't work, you could try cloning it straight to the second machine in order not to have the VM copied from one place to another. (Although it's not a problem since I've copied VMs from one place to another dozens of times and had no problem playing the them afterwards)

2 Answers 2

1st Option

The error in the screenshot could be related to a file corrupted during the copy of the VM to the second machine or a failed clone itself. To test if the clone is ok it would be a good ideia to play it on the first machine since it's still available. If it's ok, then try copying the cloned VM again to the second machine.

2nd Option

Alternatively you could use VMware vCenter Converter Standalone which is a free tool capable of converting P2V and V2V (the latter would be like cloning a VM from one place to another).

Now you just have to browse for the .vmx file of the VM you want to convert.

Chose the location in which the VM will be converted to (like a shared folder on the second machine).

Next you'll see the current specifications of the VM and you can change them if you want by editing each option.

Done. Click next and if you're ok with the summary, click finish to begin the convertion.

Once it finishes you can add the VM to the Workstation on the second machine and play it. VMware vCenter Converter Standalone is a very helpful tool and I suggest you check the other options, like converting P2V, since it might be useful some times.