It 'worked' in the sense that I got a VM put on a cluster, but somehow the conversion process made it unusable.

It may work 100% OK for other people, but unfortunately, it hasn't for me.

I finally got the VM on the cluster, but on the face of it, something strange happened during the conversion process. The first thing is that when the VM is powered up, there is no mouse available. This makes navigation pretty impossible. I thought the solution would be to install VMware Tools into ...

OK, some progress.... In the failed attempt, when selecting the destination, I chose a folder (call it TestVM) that was already on the datastore, and when prompted to supply the name, I chose TestVM. The converter didn't seem to like that and created a new folder called TestVM_1 before it then fell ...

The text I just posted was the complete contents of the lone log file in that directory.

Tle log file that I found doesn't provide much further info - The log file name: 'logs\V2V_Log-20250813-093443.log' (PID 1812) 8/13 9:34:43.720 4cb0 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib 8/13 9:34:43.720 4cb0...

Thanks for that. It got slightly further with the older version but then failed with no useful info as to why. Are there any logs I can look at that might show me a clue? It started the conversion then reported "Creating virtual machine.....Error create (sic) virtual machine...Conversion failed...

I just downloaded this software today in order to do some P2V testing. I want to convert a Windows 10 PC to VM on a VMware 7.x cluster. I get as far as selecting the required disks from the PC and getting to the dialog for logging into the cluster. I give it the IP address of the vCentre VM, user na...