30 people have viewed this post and not one answer?????
I have EXACTLY the same issue...I have no idea how to fix it either, but it is maddening. I am guessing I will have to go in via the command line and manually edit the VM definition to the right path.
VC 2.0.1 seems rather rife with bugs so far.
Have had more problems to list when upgrading VC, so where possible ive always done fresh install..
I had a similiar issue. I found that after registering my VM within VC I couldn't power it on. This was because it couldn't find the vmdk files although I could see them in the browse datastore window.
I ended up having to manually edit every one of the 57 VM vmx files and take out everything before the vmdk file name.
i.e. was -
scsi0:0.name = "hosts2:rhel3up6.vmdk"
changed to -
scsi0:0.name = "rhel3up6.vmdk"
As you can see I took out the 'hosts2:' from the name reference