I have the result from running "dd count=155232256 if="Windows-cl1.vmdk" of="Metadata-cl1.bin" bs=1"
exact file size of Windows-cl1.vmdk is 155232256
But it is 60MB after compressing and I cannot attach it here.
The mentioned dd command i.e. the count would result in a .bin file which contains user data, so that's not what you want I guess.
Although this file seems to be severely damaged, I would like to take look at it.
As a first step - to find out the file's metadata size - please run:
dd if="Windows-cl1.vmdk" of="Metadata-cl1.bin" bs=1536 count=1
The provided .bin files shows that the first 25,728 sectors are used for metadata, so please run the below command, and attach the resulting .bin file to your next reply.
dd if="Windows-cl1.vmdk" of="Metadata-cl1.bin" bs=512 count=25728
Another quick question before I take a closer look into the ~4,500 metadata errors.
You mentioned the "exact file size of Windows-cl1.vmdk is 155232256", but that's most likely what the finder shows. Please run ls -l from the command line to get the file's exact size in Bytes.
There's too much damage in the file that I will be able to fix I'm afraid.
However, other users with badly damaged virtual disk files reported that they had success with the free Starwind V2V converter, and were able to access the virtual disk again to backup important data.