File not found error when attempting to start VM

[jamil_abuaqel]

Hello,

I am attempting to start my virtual machine but I got the following error:

"File not found: /****My Windows 10 x64.vmwarevm/Windows 10 x64.vmdk

This file is required to power on this virtual machine. If this file was moved, specify the new location."

I clicked on Browse and went to point out to the VMDK file for my virtual machine but then got the following error:

"VMware Fusion cannot find the virtual disk "/*****My Windows 10 x64.vmwarevm/Windows 10 x64.vmdk".

erify the path is valid and try again.

The system cannot find the file specified

Cannot open the disk '/Users/jamil_abuaqel/Virtual Machines.localized/My Windows 10 x64.vmwarevm/Windows 10 x64.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine"

I did some reading and tried a couple of things like removing the .lck files but nothing worked.

I am running this on a Mac running Catalina with Fusion 11.5.5.

Hope to get some advice on how to fix this.

[a_p_ · Accepted solution]

Welcome to the Community,

please check whether all files that make up the virtual disk are present in the VM's folder/bundle.

With default settings, each virtual disk (and/or snapshot) consists of a descriptor file (e.g. "Windows 10 x64.vmdk"), and several data files (e.g. "Windows 10 x64-s00x.vmdk"). The descriptor file contains the list of the required data files.

André

[jamil_abuaqel]

Thanks for the response Andre. I checked the package and found 239 files of those then check the VMDK file and found reference to those 239 files. Checked the file names and they match. Anything else you would recommend?

[jamil_abuaqel]

I took a deeper look at the VMware.log file and found that there was a message reporting a missing vmdk file that I missed seeing, e.g., Windows 10 x64-s083.vmdk. I saw that the files before it and after it (Windows 10 x64-s084 and Windows 10 x64-s082) have identical size and content so I just duplicated one of them then renamed it to the missing *-s083.vmdk. Afterwards, the log file showed another two or three missing files and I did the same for all. Once done, I started the VM and it successfully came up

Thank you Andre for the help, case closed.

[IndyBTechie]

Holy moly.  Thank goodness I found this thread even though its a few years old.  I am still running Fusion on my older Intel laptop and was using CC cleaner and accidentally deleted many of the vmdks.  If I hadn't found this thread and your solution of copying the missing vmdks in the bundle, I would have been totally lost.  Thank you so much for adding your solution.  Saved me a HUGE headache and $$$!