OK, copying the "RAW" VMDK content from the Datastore provided files that were much larger, but Starwind recognized them and allowed the conversion to continue. So, the export process seems to be the issue. Next I'll see if the resulting VHD file works with Hyper-V, I look forward getting ...

It seems that the issue where Starwind is unable to open exported vmdk files continues... Why was a solution or suggested work around never posted? I have stopped a pair of VMware* VMs, exported them via the standard VMware Infrastructure client export process and every time I get the "Error op...