Q. I'm having problems binding Hyper-V virtual networks. The error messages say the NIC is already bound to another virtual network. What's wrong?

A. I recently had this problem after I updated my NIC drivers—I couldn't map any NICs to a virtual network. In the end, the solution was to run the two commands below, which freed up all the NICs and allowed me to create new virtual switches and bind to the NICs.

netcfg -u vms_pp
netcfg -l c:windowswinsxsamd64_wvms_pp.inf_31bf3856ad364e35_6.1.7600.16385_none_beda85050b13680cwvms_pp.inf -c p -i vms_pp