Hello Peeps,
I have the same issues, removing lck folder did not help.
I got this error :
The file specified is not a virtual disk
Cannot open the disk 'C:\Users\benso\VM\Win7_Pro_Prod\Win7_Pro-0-s001.vmdk' or one of the snapshot disks it depends on.
Module 'Disk' power on failed.
Failed to start the virtual machine.
Directory listing;
Please help!
Moderator edit by wila: detached from thread: https://communities.vmware.com/t5/VMware-Workstation-Pro/module-disk-power-on-failed/m-p/2314133#M13...
> Cannot open the disk 'C:\Users\benso\VM\Win7_Pro_Prod\Win7_Pro-0-s001.vmdk' or one of the snapshot disks it depends on.
That is expected. Name-s001.vmdk is NOT A VIRTUAL DISK:
A file with that name is the first part of the vmdk called Name.vmdk.
The fact that you get a message like this simply means that you or somebody else misconfigured the vmx-file so that it points to Win7_Pro-0-s001.vmdk instead of Win7_Pro-0.vmdk
Ulli
I'm having almost same error:
The parent of this virtual disk could not be opened
Cannot open the disk 'C:\Users\...\Windows Server 2019-000003.vmdk' or one of the snapshot disks it depends on.
Module 'Disk' power on failed.
Failed to start the virtual machine.
Open vmware.log in a texteditor and look up which file exactly fails.
Then compare that with the files you actually have.
Ulli
2022-06-03T14:41:03.623Z In(05) vmx DISK: OPEN nvme0:0 'C:\Users\VB\Windows Server 2019-000002.vmdk' persistent R[]
2022-06-03T14:41:03.729Z In(05) vmx DISKLIB-SPARSE: "C:\Users\VB\Windows Server 2019-s018.vmdk" : failed to open (15): Failed to load header.
2022-06-03T14:41:03.730Z In(05) vmx DISKLIB-LINK : "C:\Users\VB\Windows Server 2019.vmdk" : failed to open (The file specified is not a virtual disk).
2022-06-03T14:41:03.730Z Er(02) vmx DISKLIB-CHAIN : DiskChainOpen: "C:\Users\VB\Windows Server 2019-000002.vmdk": Failed to open parent "C:\Users\VB\Windows Server 2019.vmdk": The file specified is not a virtual disk
2022-06-03T14:41:03.730Z Er(02) vmx DISKLIB-CHAIN : DiskChainOpen: "C:\Users\VB\Windows Server 2019.vmdk": failed to open: The parent of this virtual disk could not be opened.
2022-06-03T14:41:03.734Z In(05) vmx DISKLIB-LIB : Failed to open 'C:\Users\VB\Windows Server 2019-000002.vmdk' with flags 0xa The parent of this virtual disk could not be opened (23).
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z In(05) vmx DISKLIB-LIB_MISC : DiskLib_GetStorageBlockSizes: Failed to get storage block sizes, The virtual disk requires a feature not supported by this program.
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
Do you have "C:\Users\VB\Windows Server 2019-s018.vmdk" ?
Read the file "C:\Users\VB\Windows Server 2019.vmdk" and check if all referenced files exist and have a non-zero size.
Check your quarantine location of your Antivirus-tool. Consider setting a rule to ignore vmdk-files - otherwise this will happen again and again.
Ulli
YES to all.
NO Antivirus because I'm able to run any other VMs
Whats the size of s018.vmdk ?
Do all the s00*.vmdks exist and have a non zero size ?