Hyper-V Virtual Switch and SET Troubleshooting Guide

Map the network design

Document the physical NICs, management VLAN, VM VLANs, switch type and whether the design uses SET. Confirm the physical switch configuration before changing the Hyper-V host.

Check adapter state and bindings

Use Get-NetAdapter and Get-NetAdapterBinding to confirm the physical adapters are up and the expected Hyper-V virtual switch protocol bindings exist.

Check the virtual switch

Use Get-VMSwitch and Get-VMNetworkAdapter. Verify that the VM is connected to the intended switch and that the adapter is not disabled.

Validate VLAN configuration

Compare the VM VLAN mode and ID with the physical switch configuration. A mismatch between access and trunk expectations can produce symptoms where one VLAN works while another does not.

Investigate SET issues

If a switch creation or modification fails, inspect the Microsoft Virtual Network Switch Protocol binding. Microsoft documents cases where an incorrect vms_pp binding prevents virtual switch creation.

Test from both directions

Test host-to-VM, VM-to-host, VM-to-gateway and VM-to-VM paths. Do not conclude that the VLAN is correct simply because the host can ping its gateway.

Useful commands

Get-NetAdapter
Get-NetAdapterBinding -ComponentID vms_pp
Get-VMSwitch
Get-VMNetworkAdapter -VMName <VMName>
Get-VMNetworkAdapterVlan -VMName <VMName>

Production checklist: capture the original state, test one dependency at a time, make the smallest controlled change and validate the original symptom before closing the incident.

What good troubleshooting looks like

Use evidence before configuration changes. Record the symptom, test result, change made and validation result so another engineer can repeat the procedure.

Workflow
Symptom → hypothesis → direct test → controlled change → validation → documentation

Frequently asked questions

What should I check first?

Start with the exact failed path or dependency and test it directly before changing configuration.

Should I change production configuration immediately?

No. Capture the current state first and make one controlled change at a time.

How should I document the fix?

Record the symptom, commands, result, configuration change and validation result.

Related TechRunbook guides

Primary reference

This guide was independently written for TechRunbook. Technical details were checked against current Microsoft documentation. Microsoft Learn reference →

Need more infrastructure runbooks?

Explore the TechRunbook article library for Windows Server, VMware, Hyper-V, Azure, PowerShell and MABS troubleshooting.

Browse all articles →