StarWind Software

I installed V2V with the intention of moving a few VMs from VMWare to Hyper-V. Post installation I noticed an error in the event logs:
The vstor2-mntapi20-shared service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

The driver is part of the installation. I uninstalled and tried again with the same results. Hoping this wasn't required, I went ahead and tried to move a Linux test VM. The process started fine, but throws a few more errors.

12/4 10:41:18.950 1b80 Facility ???WARNING: HyperVDisk::CreateOutputImage: Error create directory 53 - \\10.2.2.11\E$\PROXY-01-v6\Virtual Hard Disks. The network path was not found.
12/4 10:41:29.645 1b80 Facility ???INFO: WrapperHyperV::waitJob: JobState 7
12/4 10:41:56.267 1b80 Facility ???ERROR: CVHDFile::ParseFile: Error opening file \\10.2.2.11\E$\PROXY-01-v6\Virtual Hard Disks\PROXY-01.vhd - 53. The network path was not found.
12/4 10:41:56.440 1b80 Facility ???ERROR: CPPConverting::Convert: FAILED

The errors don't make sense, since the VM gets created in Hyper-V and the files are present in Hyper-V. When I power it up I get a fast flashing cursor and the VM will not boot.

First is the failing driver listed in the event log required, second is there a repair or additional step I need to run to get the VM to boot?

May I learn the VM properties? Knowing guest OS and the host OS might be helpful.
This can be an issue with the drives.
Please try conversion of a disk alone with Repair mode enabled. Make sure to have the VM shut down during conversion.

Host OS is VMWare 5.5
Guest OS is Centos 6

I'm trying to move the VM to Windows 2019 Hyper-V. I'm pretty sure the issue revolves around the driver error.

Try copying the file to the destination server and converting it there as a local file.

Which file should I copy, if you're referring to the vmware vm, how?

I tried another strategy that failed as well. I installed a backup solution and attempted to pull backups, but apparently the free version of vmware blocks the API for any type of migration or movement of vm's. Could this be the issue I'm experiencing with V2V? Can you run the tool against the free version of vmware 5.5?

Yes, it can be an issue. Thanks for your update.
Could you please copy the VMDK to the destination server (i.e., Hyper-V server) and convert it locally? File copy should do it.

I thought I had a working solution. I successfully copied Centos 6 VM to a staging computer, ran the local file move to hyper-v successfully. This morning I attempted to move the production boxes running Centos 7. V2V ran successfully, created the Gen 2 VM, set vhdx storage to expand, smooth as silk. The files are there, the boot order is set to hard drive then network. When I boot the VM it eventually gets a Hyper-V error stating no OS found.

Could this be UEFI or some other secure boot feature causing the issue? I tried to disable secure boot, but get the same result.

Greetings,
This can be helpful https://www.youtube.com/watch?v=dQtUb91 ... ithPassion https://communities.vmware.com/t5/VMwar ... d-p/453875.

Different host and guest OS, but maybe I can use some of it for troubleshooting.

Yes, you are right. Approach should be similar though.