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.

VMWare VM settings:

VMWare VM settings

enter image description here

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?
  • You can upload images and provide links to that image regardless of your reputation. You just can't inline the screenshot. Asking for reputation or upvotes is frowned upon. However, Windows 1809 - Box-000005-s015.vmdk is listed in the configuration file for the VM, but snapshots are incremental so if you attempt to rollback to a previous snapshot it will either work and you will be missing your changes or it simply won't work. If the .vmdk file is missing then you will be unable to boot the VM. (I can't tell if that is a snapshot or not).
    – Ramhound
    Jul 28, 2021 at 16:50
  • Alright. Sorry about that. I will upload a couple screenshots
    – Thumb
    Jul 28, 2021 at 16:52
  • Look in the folder for the machine and make sure you are starting from the VMX file which VMware uses to start and then from there loads the VMDK main file.
    – John
    Jul 28, 2021 at 17:27
  • @John It appears to be loading the VMX correctly. But whenever I try to resume the suspended virtual machine, I get the same error. I updated the original post with a picture of the error dialog.
    – Thumb
    Jul 28, 2021 at 19:36
  • One thing I have done is to create a new machine (so new VMX) file of the same kind as the non starting machine. This is in a new folder. COPY the VMDK file from its folder to the new folder and see if the machine starts now. Also follow this VMware article for recovering a machine with an uncombined snapshot: communities.vmware.com/t5/ESXi-Discussions/…
    – John
    Jul 28, 2021 at 19:46


You must log in to answer this question.

Browse other questions tagged .