VMWare to Hyper-V Conversion failing

[Lionel Der Boven]

Hi,

Problem is not there on the older version. So it is a bug in the new version. VM migrated just fine in the older version. Thanks for the solution!

Can you let us know when the bug is fixed on the new version?

Thanks in advance!

[yaroslav (staff)]

This problem was reported and is going to be fixed in new builds.

[pypwdl]

We downloaded the version (9.0.1.444) and it still appears that the issue is not repaired. Thanks.

[yaroslav (staff)]

Use the older version https://drive.google.com/file/d/1hDP4gl ... Ea_5p/view.

[JonathonFS]

For anyone curious, the 0x80070570 error is occurring for me in the latest version 9.0.1.509. Looking forward to this being fixed so we can use the new Hot Migration feature when converting to a pre-allocated vhdx.

Note sure if this is related, but every time I get the 0x80070570, the converted VHDX file is missing the last character in the file name. For example, when convert an ESXi disk named "Server2016-new_1.vmdk", the resulting Hyper-V disk is named "Server2016-new_.vhdx". If the VM has another disk named "Server2016-new_2.vmdk", the Hyper-V disk name will be "Server2016-new_(1).vhdx", because the app is smart enough to recognize that name is already taken. This definitely isn't causing the problem (because renaming a vhdx doesn't cause this error), but it could be a symptom of whatever the root problem is.

[yaroslav (staff)]

This is a known issue and the dev team is working on fixing it.
Please use the build above for now.

[spacklewoof]

Same here. I can't believe you are still passing out the old version.

[yaroslav (staff)]

The build was not released yet. Stay tuned.
You can try a different disk type for now.

[twclark]

Does anyone know if this is still an issue in build 554?

[yaroslav (staff)]

Hi,

Yes, it is still an issue.

[lostprey]

Good day!

Is there an approximate forecast for the release of a corrected version?

Thank you!

[yaroslav (staff)]

Sadly, the file above is the only workaround for now.

[JLee]

I have downloaded the latest release and still see the same issue is happening. I came to the forum and via this thread found the older version does not have the issue but the 2 links I have seen posted are both no longer valid.

Can we get a new share of the older version so I can try to do VMware to Hyper-V VM conversion please?

Thanks in Advance

[yaroslav (staff)]

https://drive.google.com/file/d/1hDP4gl ... sp=sharing is still valid.

[JLee]

The download worked. I was able to convert 2 VMs but both now give the blue screen of death - inaccessible boot device.

The source VMWare VM is scsi 0 - HD 0,0

HyperV VM is scsi 0 - HD 0,0

How do I prevent this during conversion?