This issue is resolved in vSphere 6.5 Update 3 available at
VMware DownloadWorkaround:
Workaround: 1 In the migration page select "Change both compute resource and storage"
Workaround: 2 From the vSphere Web Client select an affected Virtual Machine and click Launch Remote console. Once it is loaded, close the session
- Run the migration again.
Note: This work around may need to be ran again as it does not permanently resolve the issue.