So, you’ve screwed up your Hyper-V virtual switches and now you’re getting the infamous “Cannot bind .. because it is already bound to another virtual network” error? No problem, you say, all I need to do to fix this is unbind the “Microsoft Virtual Network Switch Protocol” from the NIC, right? So I’ll go to the adapter settings, right-click … wait ... oops – Server Core (!?).
nvspbind.exe to the rescue! Before you proceed though, if you’re on a production box remember what you’re doing. Messing around with network settings of the wrong adaptor might make clients, colleagues and/or bosses a bit grumpy if things go sideways, so make sure you have the important stuff backed up first.
nvspbind.exe was written by a member of the Hyper-V team and will reset the bindings on the adaptor specified to the default settings – which in turn will allow you to access the NIC in the Hyper-V Network manager again.
After downloading, first execute nvspbind.exe -n to get a list of the adaptors and their Guids. Make sure you identify the right adaptor. Like in my case (a Dell 2950) many multi-port NICs have the same name except for some additional moniker of some sort (like “#2”).
In my case the culprit was the first NIC in the list identified as “Local Area Connection 4”
Next, execute nvspbind –u {GuidOfAdaptor}. This will unbind the Virtual Network Switch Protocol from the card and rebind all the default protocols and services.
Should this not work, the same Hyper-V team member has also posted a script that will essentially reset all settings and delete all virtual networking configuration (nvspscrup.js). Execute using the command line scripting host (i.e. “cscript”).
Addendum: just ran across ENIAC’s posting from September of last year. He also has some additional info on how you can use registry settings and netcfg to solve this issue.
af4c4d75-1254-4131-8f18-9e46ddf06fbb|1|4.0