Glad you were able to get it working. I know that your conversion command line was correct so figured something else was awry. I retrace my steps from time to time to make sure what I think should work actually continues to work (and that I haven't imagined something).
What I didn't realize is that if you make the mistake of keeping the .vhdx extension on both source and destination files (like my first example in the post script), the original source file is ruined in the process. You get no warning except that the conversion appears to go really, really quickly. Once you've ruined the original source, any further attempt to correct your mistake by re-converting the original vhdx to vmdk will appear to work. What you get, though, is garbage.
I added the post-script because I've seen a rash of pxe boot posts here lately when people were trying to install from a converted Insider Preview VHDX file. I wanted to see if I could figure out what was really happening.
- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
