Hyper-V Error Adding Virtual Switch - Ethernet Port Bind Failed

[Neutralizer]

Hi All,

Getting a strange error with Hyper-V on Windows 8 Pro x64.

When I try and add a virtual switch I get:

Error Applying Virtual Switch Properties Changes
Failed while adding virtual Ethernet switch connections.
Ethernet port '{a bunch of stuff}' bind failed: The data is invalid.
(0x8007000D).

There doesn't seem to be much on google that relates to this (in particular the bind failed: the data is invalid part).

Anyone have a clue what the cause might be?

Cheers

 

[area 66]

can be many thing, in 3 or 4 years that I'm using Hyper-V I never encounter it, you need some networking knowledge to play with virtual switch, but usually 0x8007000D error are due to files corruption or permissions, try to run hyper-v management as admin.

 

[Neutralizer]

Hi There,

Yep tried running the manager as admin a few times, but no change.
I also tried removing and reinstalling the Hyper-V features from Windows, but no change.
I've uninstalled the Ethernet drivers on the host and reinstalled them, again no change.

I'm at a bit of a loss, I'm guessing it might be a driver conflict with my Marvell Yukon 88E8056 Ethernet controllers (11.45.4.3) and Windows 8...

If anyone else has any suggestions then please let me know.

Cheers

 

[area 66]

Yes the Marvell can be a problem; peoples who use ESXI ( Wmware ) and build their own server are using mainly only Intel NIC as they are the one who are more compatible Marvell and Realtek don't work with ESXI, knowing that I purchase only motherboard with Intel nic , so your best option will be to install a pci-e or pci Intel nic , anyway it's always good to have a separate nic for the VM. I have good success with this one :

[h=1]Intel EXPI9301CTBLK[/h]

 

[Neutralizer]

I will eventually get a separate NIC, in the meantime I got it working through my wifi adapter surprisingly.

 

[Kebero]

I will eventually get a separate NIC, in the meantime I got it working through my wifi adapter surprisingly.

Binding a vNIC to WiFi is a new feature in Hyper-V 3.0. Basically, it sets up a bridge for you. What I do is run ncpa.cpl, delete the bridge (this leaves the vNIC in place), then create a new bridge with the vNIC WiFi and Ethernet adapters. That way you get automatic switching of interfaces.

 

[Neutralizer]

Thanks for the hint mate, should make it a bit quicker in future :thumb:

 

[Kebero]

Let me know how that works out for you!