I've been renaming my VMDKs as I attach different disks with various adapter types to my VM. On one change, the specified VMDK file was not found, so Fusion offered to let me browse for an alternative VMDK.
Upon choosing the right VMDK, the VMX file does not updated and I'm left with the same error, where Fusion is offering to let me browse for a VMDK again, and again.
The issue with renamed disks isn't specific to Fusion; unfortunately it's like that in Workstation on other platforms.
Thanks for bringing this up. In the meantime, try moving the disks to other directories instead of renaming them.
>Thanks for bringing this up. In the meantime, try moving the disks to other directories instead of renaming them.
Thanks for the suggestion but that breaks my neatness of having all my VM files in one VM directory, e.g.
If I had snapshots where I could share base images from a common storage pool, then I would re-consider a using another directory.