We've just updated Vmdk2Vhd to deal with this issue. Grab a copy of the latest version and the VMDK's from VMWare Converter will now convert properly.

Did not work with "ordinary" vmdk files placed on directory-mounted NTFS partitition (C:\Data\....) either. I had to copy them somewhere to C:\ drive, that solved the problem. I downloded the converter today.

I had an 11.5GB virtual machine that was broken into 7 pieces (not by me! I didn't know VMware did this). The VMDK to VHD Converter kept coming up with the same "Invalid VMDK image....." error message. I tried it with all of the VMDK pieces but none worked.

 I tried moving the virtual machine, but that didn't make a difference.

In the end, I used the VMware Converter to create a one-piece copy of the VM. The VMDK to VHD tool was able to convert that. This is not an ideal solution, especially for multiple VMs and large VMs, but it worked.

butinen:

I had an 11.5GB virtual machine that was broken into 7 pieces (not by me! I didn't know VMware did this). The VMDK to VHD Converter kept coming up with the same "Invalid VMDK image....." error message. I tried it with all of the VMDK pieces but none worked.

I tried moving the virtual machine, but that didn't make a difference.

In the end, I used the VMware Converter to create a one-piece copy of the VM. The VMDK to VHD tool was able to convert that. This is not an ideal solution, especially for multiple VMs and large VMs, but it worked.

Vmdk2Vhd supports split VMDK's, however the split files ending in -s001, -s002, and so on are not meant to be opened in Vmdk2Vhd. These split files are not valid VMDK's themselves and you will only be able to open the base VMDK file that is associated with these split file. The base file is the one without the -s00x in the filename. For example, if you see a series of files that look like "VM-Foo-s00x.vmdk" the file that you need to open in Vmdk2Vhd will be called "VM-Foo.vmdk". Hope that explains it.

I am using VMWare Server 1.0.1... and the converter is unable to convert...

 What can i do to make it work?

 

Thanks!!
 

Same problem here....when I try to convert the vmdk file (one segment), it gives me the:

I have the same issue - used vmware converter 3.0.0. build 39557 to create the vmdk, but the vmdk2vhd utility version 1.0.13 gives : "Invalid VMDK file, select another.." 

I should note I did run the VMDK with vmware 'player' first (relatively old version) -  before trying to convert it -so perhaps that has some impact..  also it was part of a "2 drive" conversion where there was both a D (boot) and E drive created from a physical machine with the vmware converter

UPDATE:  I am now converting one of my images which did not work prevously (gave invalid vmdk , please select another..)

 I think it did not work before because it was an NTFS Compressed file  (on a USB connected drive?) - when I copied it to my C:\temp (and thus it uncompressed it, then I seem to be able to convert - as long as I do not specify my ntfs compressed drive as the destination - if I do I get an exception (invalid memory overwrite or similar..) )

 If you are having trouble, try moving the file to an uncompressed file (or uncheck NTFS compression on it.., and make sure the destination is not on a compressed drive..)

I think it is likely the issue (since I saw another thread regarding a problem with ntfs compression with the resize tool..

 

Successfully used VM Converter version 39557 to convert from Physical to Virtual into ESX version 3.

 Attempted to use the VMDK to VHD file converter version 1.0.13 to convert from VMDK to VHD.

 VMDK flat file is slightly under 20 GB.

 I assume this tool doesn't work with ESX version 3, only version 2 of ESX?