Windows Server / Hyper-V & Failover Clustering
Check a Hyper-V virtual switch's actual uplink
A VM can lose external connectivity when attached to an internal switch or a changed physical uplink. Inspect switch configuration first.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-VMSwitch | Select-Object Name, SwitchType, NetAdapterInterfaceDescriptionRead the result
The query identifies switch types and associated uplink description where applicable. Guest addressing and upstream VLAN configuration remain separate checks.
Resolve and verify
Compare the VM's intended network with its switch and physical NIC. Repair the approved attachment or uplink and retest the original guest flow.
Before changing production
Do not recreate a switch carrying host management traffic without an alternate access path.