I've just run into an issue that I have not previously encountered in Workstation (been using it since v8).
I have a Windows 8.1 host system, Workstation 14.1.1 and a Windows 10 guest that is cloned (linked) to a snapshot in the "parent" VM.
The parent VM, in Snapshot manager, shows the snapshot, with the padlock icon and if I go to delete it, it correctly tells me that deleting this snapshot will break my cloned VM (so of course I don't delete it).
Yet, when I go to start the cloned VM, it tells me it cannot find the dependent snapshot *.vmdk file. I can browse for it, and it's definitely there, but it refuses to recognize the file (even though the name is correct and identical).
The snapshot was created (I am pretty sure) in Workstation 12.5.7, but I don't see why that would make a difference?The cloned VM was created in Workstation 14.1.1..
Looking like my clone is a write off? How can a cloned VM reject a linked *.vmdk that hasn't been modified since well before the linked clone was created from it?
