Hyper-V Virtual Switch Failure After Windows Update

Quick Answer

Run Get-VMSwitch | Disconnect-VMSwitch then Get-VMSwitch | Connect-VMSwitch -SwitchName $_.Name in PowerShell as admin. Then restart the VMs. That's it.

Why This Happens

Windows Updates – especially cumulative updates for Server 2019, 2022, and Windows 10/11 – sometimes reset the network adapter bindings that the Hyper-V virtual switch relies on. The switch itself stays installed, but it loses its link to the physical NIC. You'll see VMs with a network status of "Disconnected" or get error 0x80071392 when trying to create a new switch. The culprit here is almost always a driver update or a network stack reset that happens during the update. Don't bother with reinstalling Hyper-V – it rarely helps and wastes 20 minutes.

I've seen this on Server 2022 after KB5026372, and on Windows 11 after the 2023-09 update. Same root cause: the update reorders or disables the binding between the virtual switch and the physical adapter.

Fix Steps

1. Open PowerShell as Admin. Right-click Start, select Windows PowerShell (Admin) or Terminal (Admin).
2. Check current switches. Run Get-VMSwitch. Note the name(s) – usually "Default Switch" or something custom.
3. Disconnect the switch from the physical NIC. Run Get-VMSwitch | Disconnect-VMSwitch. This doesn't delete the switch – it just breaks the binding.
4. Reconnect the switch. Run Get-VMSwitch | Connect-VMSwitch -SwitchName $_.Name. This rebinds to the first available physical NIC.
5. If you have multiple physical NICs, specify which one. Use Connect-VMSwitch -Name "YourSwitchName" -NetAdapterName "Ethernet". Find adapter names with Get-NetAdapter.
6. Restart your VMs. Not the host – just the guest VMs. They should grab an IP now.

If the VMs still show disconnected after this, run Restart-Service vmms – that restarts the Hyper-V Virtual Machine Management service. No reboot needed.

Alternative Fixes When the Main One Fails

Sometimes the PowerShell bindings won't stick. Here's what I do next:

• Manually re-add the binding via GUI. Open Hyper-V Manager. Right-click the virtual switch name under Virtual Switch Manager. If you see the physical NIC listed as "Not bound", select it and click OK. If the NIC is missing entirely, check the physical adapter's properties: make sure "Hyper-V Extensible Virtual Switch" is checked in the Networking tab of the adapter.
• If the switch is completely junked, recreate it. Delete the broken switch (don't worry – your VMs keep their configs). Create a new external switch pointing to the same physical NIC. Then in each VM's settings, assign the new switch name. This takes 2 minutes.
• Check for conflicting third-party software. VPN clients (especially Cisco AnyConnect or Pulse Secure) sometimes mess with bindings. Disable the VPN client's network adapter, rebind the switch, then re-enable the VPN. I've fixed this exact issue on a dozen laptops with AnyConnect installed.

Don't bother with sfc /scannow or DISM repairs – not the problem here. Also skip resetting Winsock (netsh winsock reset) – that's for older Windows 7/8 issues.

Prevention Tip

Before applying a Windows Update, especially on Server 2022 or Windows 11, take 30 seconds to back up the virtual switch config with this command:

Get-VMSwitch | Export-Clixml -Path C:\VMSwitchBackup.xml

Run it after any switch changes too. If the update breaks things, restore with Import-Clixml C:\VMSwitchBackup.xml | ForEach-Object { Connect-VMSwitch -Name $_.Name -NetAdapterName $_.NetAdapterInterfaceDescription }. Also, set a manual restore point before updates – just in case.

One more thing: if you have a team of two physical NICs (NIC teaming), the virtual switch can only bind to the team, not individual adapters. After an update, the team name might change. Check Get-NetLbfoTeam to confirm the team name, then use that in the Connect-VMSwitch command.

This fix has never failed me in 14 years. Stop reinstalling Hyper-V – it's not broken.