StarWind Software

I have a physical machine with server 2012 that I am trying to convert to a Hyper-V 2022 server and I am getting the Access is Denied 0x80070005 error.

Using local administrator credentials for both machines.

On the Hyper-V 2022 target, credssp is enabled.

On the source Physical machine I ran this command: Enable-WSManCredSSP -Role Client -DelegateComputer "target.domain.local"

Ran v2v converter as administrator on source physical machine.

Disabled firewall on both machines.

This is all i get in logs:

11/10 13:24:40.792 f94c Facility ???ERROR: VMConverter::HyperVConverter::Connection: connect fail - 0x80070005
11/10 13:24:41.623 f94c Facility ???WARNING: CPPHYPERVConnectionTo::onNext: connect Access is denied.
(0x80070005)
11/10 13:28:51.414 94c4 Facility ???INFO: WrapperHyperV::connect: Host - \\target\root\virtualization\v2
11/10 13:28:51.434 94c4 Facility ???ERROR: WrapperHyperV::connect: pLoc->ConnectServer \\target\root\virtualization\v2 - 0x80070005
11/10 13:28:51.434 94c4 Facility ???ERROR: WrapperHyperV::failResultToStr: Last Error - Access is denied.
(0x80070005)
11/10 13:28:51.434 94c4 Facility ???ERROR: VMConverter::HyperVConverter::Connection: connect fail - 0x80070005

Halp!

Welcome to StarWind Forum. I don't think this one relates to the V2V converter.
Try using the local credentials, not the domain ones, for the destination. Also, it could be something on the compatibility side between 2012 and 2022 (e.g., VM comptatibility version or so). Please try converting an individual disk to 2022.

yaroslav (staff) wrote: ↑

Mon Nov 10, 2025 7:22 pm

Welcome to StarWind Forum. I don't think this one relates to the V2V converter.
Try using the local credentials, not the domain ones, for the destination. Also, it could be something on the compatibility side between 2012 and 2022 (e.g., VM comptatibility version or so). Please try converting an individual disk to 2022.

I mentioned that I am using LOCAL admin credentials for both machines.

As you suggested:

When converting one disk from physical to a local drive, v2v proceeds normally.

When converting one disk from physical to Hyper-V Server (target), fails with Access Denied.

Firewalls are off on both machine.

Credentials are verified to be correct and working.

I guess there's something between WS 2012 and 2022 hypervisor versions. I know that you cannot migrate the VMs from 2012R2 to 2022, guess same applies for p2v.
Could be helpful https://learn.microsoft.com/en-us/windo ... ows-server.

yaroslav (staff) wrote: ↑

Mon Nov 10, 2025 7:39 pm

I guess there's something between WS 2012 and 2022 hypervisor versions. I know that you cannot migrate the VMs from 2012R2 to 2022, guess same applies for p2v.
Could be helpful https://learn.microsoft.com/en-us/windo ... ows-server grow a garden.

Thank you for sharing

You are welcome.