The file specified is not a virtual disk.

[Slavec89]

Hello everyone. Nothing went wrong, just for no reason VM failed to start as usual showing "The file specified is not a virtual disk." error. No zero bytes files except vmware-vmx.dmp . What could happen?

[a_p_]

Does the vmware.log contain any related entries about the start/resume process?

André

[Slavec89]

Don't know how what to check. Attached that file.

[a_p_]

I don't see any related entries, but it also looks like the vmware.log has not been updated with the recent issue.

Anyway, what I see is that the file contains binary data, which is quite unusual, and could be caused by a file system issue on the host. What I'd suggest is that - after doing a backup - you run chkdsk d: /f to verify the file system, and to fix possible issues.

If this still doesn't solve the issue, extract the two scripts from the attached .zip archive to an empty directory, then drag&drop the VM's folder onto the .cmd file. The scripts will extract the metadata from each .vmdk file. Once done, compress/zip all the newly created Metadata-... files, and attach the .zip archive to your next reply, so that I can do a quick health check on them.

André

[Slavec89]

Checkdisk didn't help, but looks like it had some issues.

[a_p_]

The metadata seems to be ok.

What you may do is to reset the VM, i.e. not wake up from the suspended state.

To do this, delete

Windows 7 x64 new-aacaa6b5.vmem
Windows 7 x64 new-aacaa6b5.vmss

If VMware Workstation complaints about the missing files when you try to start the VM, you may need to remove them (the corresponding lines) from the VM's configuration (.vmx) file.

I assume that you already made a backup!

André

[Slavec89]

Did not help. Didn't complain on anything too. Only the same error.

Should I restore those files for new testings?

[a_p_]

Please compress/zip Windows 7 x64 new.vmdk and Windows 7 x64 new-000001.vmdk, and attach them to your next reply. Maybe there's something wrong with these two descriptor files.

André

[Slavec89]

That will take time, if there is any other options to try?

Maybe there is way to get files from this VM? That would be good solution too.

[a_p_]

>>> That will take time, if there is any other options to try?

Just to ensure we're talking about the same files. The 2 mentioned files are small text files, with each of them being only a few hundred bytes in size.

André

[Slavec89]

Yes my bad, didn't check carefully.

[a_p_]

Please find a recreated "Windows 7 x64 new-000001.vmdk" descriptor file, that you may use to replace the corrupted one.

André

[Slavec89]

Replaced it with file you attached, same error. Or you mean to create new VM and take those files from there?

[a_p_]

That's strange,  because it was a quite obvious issue.

Can you confirm that VMware Workstation Pro - or at least the VM's tab - was closed when you replaced the file? That's required for VMware Workstation to read the new file, rather than using cached content.

André