I am running Windows 10 using VMware Workstation 16 on my Window 10 Laptop. All was well until I put my VM into suspended mode and then put my computer to sleep for the night. Once I booted it up it gave me an error saying that it couldn't find the virtual disk (sorry I don't have the exact error message). So, I provided it a VMDK file from yesterday. Now I am getting this error.

The file specified is not a virtual disk

Cannot open the disk 'C:\Users\[user]\Documents\Virtual Machines\Windows 1809 - Box\Windows 1809 - Box-000005-s015.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine.

I must've given it the wrong vmdk file. But when I go to Settings, it is not letting change the file path to a different vmdk.

enter image description here

I have two questions:

  1. Why did the VM loose track of the VMDK disk when I put it into suspended mode?
  2. How can I give VMware the correct VMDK so that the VM will boot up again?

1 Answer 1


There may be a stale lock on that file.

Right click on the virtual machine, then go to Open VM directory. If you find any .lck file with the same name as your virtual machine, delete it and restart the VM.


Failing that, your vmdk may indeed be corrupted for some reason.

If this is the case, you may revert to a snapshot (if available).

If you don't have a snapshot, you can try to inspect the .vmdk file, or maybe a copy, with 7-zip (right click on the file -> Open archive), save the files you want to keep and then rebuilding the VM with the right image and settings. After you re-install the OS, copy the old files and you should be (relatively) fine.

  • I don't see any more .lck files in the directory.
    – Thumb
    Jul 28, 2021 at 16:21
  • There is only a cache dir, some log files, a bunch of vmdk files, a nvram, a vmsd, a vmx, a vmxf, a vmem, and a vmss in the directory.
    – Thumb
    Jul 28, 2021 at 16:23
  • @barley is there some .lck file in a subdirectory?
    – A. Darwin
    Jul 28, 2021 at 16:25
  • No, there aren't. It seems that the error that I put in my original post says that the vmdk file that I selected as my "Disk file" is incorrect...
    – Thumb
    Jul 28, 2021 at 16:26
  • 1
    @barley edited my answer. your vmdk file may indeed be corrupted, which means you would have to revert to snapshots or rebuild the VM.
    – A. Darwin
    Jul 28, 2021 at 16:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .