Error converting XPMode vhd to vmdk

[pkrzyz]

Hi, I tried to search through the forum but could not find a solution.
Downloaded StarWind V2V converter. Trying to convert a XPMode vhd file, to a vmdk file.
I downloaded the XPMode.vhd file to a Win10 machine in a local folder 'C:\Temp\XPMode' and then installed the StarWind converter on the Win 10 machine.
When I got the error originally, I tried to rename the "Windows XP Mode.vhd" to "XPMODE.vhd". But the renaming did not help.

I get an error when trying to use the local file option to convert the xpmode file.


Here is the complete log I have.

The log file name: 'logs\V2V_Log-20221014-022521.log' (PID 12068)
10/14 2:25:21.158 724 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
10/14 2:25:21.158 724 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.268
10/14 2:25:21.158 724 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
10/14 2:25:21.158 724 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
10/14 2:25:21.174 724 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 18363
10/14 2:25:21.174 724 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 40990000
10/14 2:25:21.174 724 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 40990000
10/14 2:25:26.991 724 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputFile
10/14 2:25:44.321 724 Facility ???INFO: CPPInputFile::checkFile: Select file: C:\Temp\XPMode\XPMode.vhd
10/14 2:25:44.321 724 Facility ???ERROR: CVHDDifferencingExtent::Parse: File path not valid - C:.
10/14 2:25:44.321 724 Facility ???INFO: CPPInputFile::checkFile: ParseFile: 2

[pkrzyz]

I was able to get further by doing the following.

On the original source machine the XPMode.vhd file was located in C:\Users\Public, which I copied into "C:\Temp\XPMode".
There is evidently a parent portion of the XPMode hyper-v vm, that is part of the vhd file and it was located in "C:\Program Files\Windows XP Mode".
Therefore the XPMODE vm is made up of 2 parts, located in 2 different locations.

What alerted me to this was, when I tried to mount the XPMode VHD file in the Windows 10 machine.
The Disk Management tool failed to mount it, and indicated that there was a missing parent section for the vhd file.

Solution
"1) Copied the "C:\Program Files\Windows XP Mode" folder and its contents from the source machine, to the Windows 10 machine, to the same location.
"2) Copied the "C:\Users\Public\Windows XP Mode" folder from the source machine, to "C:\Temp\XPMode" on the Windows 10 machine
"3) Mounted the XP Mode.vhd file (located in the temp folder) using Disk Management on the Windows 10 machine
"4) Once it successfully mounted, I started the StarWind V2V converter.
"5) Selected: P2V option
"6) Selected: Physical Disk
"7) Selected: From the Select disk drop down option, I selected 'Virtual Disk'
"8) Checked off the Volume (in my case it was D:\), then selected Next.
"9) Selected Local file, to store the converted vmdk file on the Win 10 drive.
"10) Chose VMDK as the destination image format
"11) Chose Esxi Server Image
"12) Chose Esxi pre-allocated image, and checked off the checkbox 'Activate Windows Repair Mode'
"13) Chose the filename and location to store the image, then pressed 'Convert'

The conversion created the vmdk file and it associated -flat.vmdk file.

I am currently uploading the conversion to see if it worked.

[yaroslav (staff)]

Welcome to StarWind Forum.
You could do VMDK conversion as a local file instead of P2V conversion.
Also, according to the logs, the file cannot be accessed. Please make sure to run the converter as administrator.