Issue

Converting VMware vmdk disks to Hyper–V vhdx using Microsoft Virtual Machine Converter 3.0 PowerShell module (ConvertTo-MvmcVirtualHardDisk) fails with error:

ConvertTo-MvmcVirtualHardDisk : The entry 00000000-0000-0000-0000-000000000000 is not a supported disk database entry for the descriptor…

Resolution

the issue is caused by VMDK file descriptor entries that Microsoft Converter doesn’t recognise. To resolve the issue we need to remove these non-recognised entries:

1. Download and extract dsfok tool.
   dsfo (by Dariusz Stanislawek) can save a block of data of any size from any location within a file. We’ll use it to extract descriptor from VMDK file, and then save modified version back into the VMKD.
2. Extract VMDK descriptor by running:
   dsfo.exe “D:\PathToVMDK\disk1.vmdk” 512 1024 “D:\PathToVMDK\descriptor.txt”
3. Open descriptor.txt with Notepad++ or other text editor. It will look something like this:
   
4. Find the line that appeared in the error above and comment it out by adding # in front of the line. Save the file.
   The error above will only list the first offending entry, so you may need to repeat the process few times until you find and remove all problematic entries. In the example above I had to comment out following lines:
   • ddb.comment = “”
   • ddb.uuid.image = “024d091c-2902-42a3-93b2-17f8cd4c0947”
   • ddb.uuid.modification = “6ab801a7-316d-4562-b91a-0dd19e781153”
   • ddb.uuid.parent = “00000000-0000-0000-0000-000000000000”
   • ddb.uuid.parentmodification = “00000000-0000-0000-0000-000000000000”
5. Save VMDK descriptor back int VMDK file by running:
   dsfi.exe “D:\PathToVMDK\disk1.vmdk” 512 1024 “D:\PathToVMDK\descriptor.txt”
6. Try running ConvertTo-MvmcVirtualHardDisk again. If you get similar error with different entry, repeat the process from step 2.

September 2017
Microsoft Virtual Machine Converter 3.0