Reply to thread

Message

<blockquote data-quote="simmerskool" data-source="post: 1117543" data-attributes="member: 61091">running VMware Workstation 17.6.2_build 24409262: was running win10_Guest8, all good. I stepped away for awhile, and VMware app had crashed and it appeared that the Host win10 had auto-updated and rebooted itself. Unexpected but ok... I rebooted the Host again, started VMware, then went to power on the VM Guest that had been running, and it failed to power on with a message: The specified virtual disk needs repaircannot open the disk (correct ssd designation .vmdk) or one of the snapshot disks it depends on. Module &#039;Disk&#039; power on failed.&nbsp; I opened the directory from the Host and the .vmdk file is there. I think I did delete an older snapshot after I had updated Guest8 VM and created its new snapshot. First thought is the VM crash caused by Host unintended reboot, is the cause. How best to repair or determine whether it is the designated .vmdk or a missing (deleted) snapshot? Perhaps I should simply try booting a different snapshot instead of the current state? I delayed going back to the Guest while I updated and tested the other VM Guests, and so far they are all running ok. Guest8 is one of my fav VM, so I hope it can be saved. Help please.</blockquote>

[QUOTE="simmerskool, post: 1117543, member: 61091"] running VMware Workstation 17.6.2_build 24409262: was running win10_Guest8, all good. I stepped away for awhile, and VMware app had crashed and it appeared that the Host win10 had auto-updated and rebooted itself. Unexpected but ok... I rebooted the Host again, started VMware, then went to power on the VM Guest that had been running, and it failed to power on with a message: The specified virtual disk needs repair cannot open the disk (correct ssd designation .vmdk) or one of the snapshot disks it depends on. Module 'Disk' power on failed. I opened the directory from the Host and the .vmdk file is there. I think I did delete an older snapshot after I had updated Guest8 VM and created its new snapshot. First thought is the VM crash caused by Host unintended reboot, is the cause. How best to repair or determine whether it is the designated .vmdk or a missing (deleted) snapshot? Perhaps I should simply try booting a different snapshot instead of the current state? I delayed going back to the Guest while I updated and tested the other VM Guests, and so far they are all running ok. Guest8 is one of my fav VM, so I hope it can be saved. Help please. [/QUOTE]

Verification