Troubleshoot Hyper-V virtual switches that leave Windows guests or hosts with an Unidentified Network.
Start with Check the virtual switch and work through the six diagnostic checks in order.
Record results before changing configuration and validate the original symptom after each controlled change.
Quick checks
Start with the basic checks in this runbook before moving to deeper troubleshooting.
- Confirm the affected service or component is available.
- Check recent configuration or connectivity changes.
- Run the relevant commands and compare the result with the expected state.
Check the virtual switch
Confirm the VM is connected to the intended external, internal or private Hyper-V virtual switch.
Check host adapters
Review physical and virtual Ethernet adapter state and confirm the expected uplink is available.
Check VLAN configuration
Verify the VM VLAN mode and VLAN ID match the network design.
Check SET configuration
If Switch Embedded Teaming is used, confirm the switch and physical NIC members are configured correctly.
Test guest networking
Check the guest IP address, gateway and DNS settings and test gateway reachability.
Check the physical switch
Confirm upstream access or trunk configuration and allowed VLANs match the Hyper-V design.
Useful commands
Run these checks from an appropriate administrative session and replace example values with your environment.
Adapters
Get-NetAdapterVirtual switches
Get-VMSwitchQuick troubleshooting path
Use this sequence to isolate the failing dependency before changing production configuration.
- Check the virtual switch → Confirm the VM is connected to the intended external, internal or private Hyper-V virtual switch.
- Check host adapters → Review physical and virtual Ethernet adapter state and confirm the expected uplink is available.
- Check VLAN configuration → Verify the VM VLAN mode and VLAN ID match the network design.
- Check SET configuration → If Switch Embedded Teaming is used, confirm the switch and physical NIC members are configured correctly.
- Test guest networking → Check the guest IP address, gateway and DNS settings and test gateway reachability.
- Check the physical switch → Confirm upstream access or trunk configuration and allowed VLANs match the Hyper-V design.
What good troubleshooting looks like
Good infrastructure troubleshooting is evidence-driven. Capture the original state, test the dependency that can prove or disprove your hypothesis, make the smallest safe change and repeat the original test.
Symptom → hypothesis → direct test → result → controlled change → validation → documentation