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.