Invalid namespace

[yaroslav (staff)]

Could you kindly share the error messages you see? Did you try converting VHDX in repair mode?

[imhereforwifi]

I too am in the same 'boat' of 'invalid namespace' 0x8004100e.

I am trying to migrate a Hyper-v on Win Server 2008r2 Datacenter to WinServer 2025 Datacenter.

When running the converter, and after selecting Microsoft Hyper-V Server, and entering my server info (both FQDN or IP address) and entering my credentials or using the windows authentication I receive the error. Looking at the logs, the application seems to be looking for a non-existent or misplaced folder location of the following "\\Hyper-vHost\root\virtualization\v2"

Ran the same function on the Windows Server 2025 with Hyper-V and it had no issues finding the "root\virtualization\v2" folder.

WinServer 2008 R2, is Hyper-V 6.1.7601.17514, and 2025 is running 10.0.26100.7019.

Is there an older version of V2V that supports the older version of Hyper-V? I tried running the latest of 9.0.1.772 and version 9.0.1.Setup.268_735 both kicked back the same error.

Any insight would be most appreciated.

[yaroslav (staff)]

I think the issue relates to authentication levels between 2008r2 and 2025, not something on the StarWind V2V side.

[imhereforwifi]

I think the issue relates to authentication levels between 2008r2 and 2025, not something on the StarWind V2V side.

Ok. so, where do I need to look to resolve the issue? Both machines are on the same domain and my credentials work all around including logging into both machines.

[yaroslav (staff)]

Hi,

I am afraid I can't advice on that as the issue seems outsied of our product.
What you can try though is just shutting doen the VM, copy its disks with robocopy, and recreate the VM in place. I don't think migrations from 2016 or earlier are possible to 2025.
The limitation is somewhere on the hypervisor side.