Hyper-V Network Adapter Not Working? 9 Fixes (2026)

Hyper-V network adapter not working fix is one of the most urgent searches for Windows 11 users running virtual machines that suddenly lose network connectivity. When your Hyper-V virtual machine cannot connect to the network, the issue can stem from corrupted virtual switches, outdated drivers, or Windows updates that break network adapter emulation. According to Microsoft Q&A, Windows updates can sometimes modify or corrupt low-level driver configurations, causing the existing virtual network adapter to become non‑functional. This comprehensive Hyper-V network adapter not working fix guide covers 9 proven methods to diagnose and resolve these issues.

When you search for a Hyper-V network adapter not working fix, you are likely dealing with a virtual machine that shows “Network cable is not connected,” a missing network adapter in Device Manager, or errors like Code 10 and Code 31. According to Microsoft Q&A, these problems can mean an inability to log in to the machine with a failure message indicating an inability to connect to the internet. This Hyper-V network adapter not working fix guide walks you through every step needed to restore connectivity. Following this Hyper-V network adapter not working fix guide will help you resolve even the most stubborn network issues.

1. Understanding Hyper‑V Network Adapter Issues

Hyper‑V network adapters can fail for multiple reasons. According to TheWindowsClub, if Hyper‑V encounters an error while configuring the network, it could be due to issues with your network adapter, an unsupported external adapter, incorrect security settings for virtualization, stopped Hyper‑V services, or not selecting the Default Switch. Finding a reliable Hyper-V network adapter not working fix requires understanding these root causes first.

Common causes of Hyper‑V network adapter failures include:

• Virtual switch corruption: Windows updates can break custom virtual switches. According to Microsoft Q&A, Windows 11 22H2 broke custom virtual switches, causing no internet connectivity from either switch.
• Driver issues: Outdated or incompatible network drivers can cause Code 10 or Code 31 errors.
• Broadcom NIC VMQ issues: Virtual Machine Queue (VMQ) on Broadcom adapters can cause random loss of network connectivity.
• Hyper‑V extensions: Extensions like the Microsoft Azure VFP Switch Filter Extension can block connectivity.
• Windows updates: Updates can modify low-level driver configurations, breaking virtual network adapters.

Understanding these root causes is the first step in any Hyper-V network adapter not working fix guide.

2. Hyper‑V Network Adapter Not Working Fix: Verify the Virtual Switch

The virtual switch is the bridge between your VM and the physical network. According to Microsoft Q&A, the first step is to verify that the VM is connected to the correct virtual switch. This is often the simplest Hyper-V network adapter not working fix you can try.

Step 1: Open Hyper‑V Manager (type "Hyper‑V Manager" in Start)
Step 2: Right-click the affected virtual machine and select Settings
Step 3: Click on the network adapter in the hardware list
Step 4: Verify the "Virtual switch" dropdown is set to the correct switch
Step 5: If not, select the correct switch from the dropdown
Step 6: Click Apply and OK
Step 7: Restart the virtual machine

According to TheWindowsClub, if you haven’t selected the Default Switch while configuring your virtual machine, you may encounter errors. This Hyper-V network adapter not working fix method resolves many basic connectivity problems.

Outcome: The VM is connected to the correct virtual switch, restoring network connectivity.

3. Remove and Recreate the Virtual Switch

Recreating the virtual switch often resolves Hyper-V network adapter not working issues caused by corruption. According to Microsoft Q&A, deleting the v‑switch that wasn’t working and recreating it solved the problem. This Hyper-V network adapter not working fix is highly effective for stubborn cases.

Step 1: Open Hyper‑V Manager
Step 2: Click "Virtual Switch Manager" in the Actions pane
Step 3: Select the problematic virtual switch
Step 4: Click "Remove" and confirm
Step 5: Click "New virtual network switch"
Step 6: Select "External" (or Internal/Private as needed)
Step 7: Click "Create Virtual Switch"
Step 8: Name the switch and select the correct physical network adapter
Step 9: Click "Apply" and OK
Step 10: Reconnect all VMs to the new switch

Alternative: According to Microsoft Q&A, you can create a new external virtual switch and then change the VM's virtual switch to the newly created one.

Outcome: A fresh virtual switch is created, bypassing corruption in the old configuration.

4. Disable VMQ (Virtual Machine Queue) on Broadcom NICs

Virtual Machine Queue (VMQ) on Broadcom network adapters can cause random network connectivity issues in Hyper‑V environments. According to ITFix, disabling VMQ on both the host and virtual machine levels resolves these issues. This is a crucial Hyper-V network adapter not working fix for Broadcom-based systems.

Step 1: Open Device Manager on the host
Step 2: Expand "Network adapters"
Step 3: Right-click your Broadcom NIC and select Properties
Step 4: Go to the "Advanced" tab
Step 5: Locate "Enable Virtual Machine Queue" or "VMQ"
Step 6: Set it to Disabled
Step 7: Click OK

Step 8: In Hyper‑V Manager, open the VM's Settings
Step 9: Click the network adapter
Step 10: Expand "Advanced Features"
Step 11: Uncheck "Enable Virtual Machine Queue"
Step 12: Click Apply and OK
Step 13: Restart the VM

According to ITFix, this process needs to be repeated for the virtual machine's network adapter settings as well.

Outcome: VMQ is disabled, resolving Broadcom NIC connectivity issues.

5. Remove Hyper‑V Extensions from the Virtual Switch

Hyper‑V extensions can interfere with network connectivity. According to Microsoft Q&A, removing the Microsoft Azure VFP Switch Filter Extension resolved the issue for one user. This Hyper-V network adapter not working fix is often overlooked but highly effective.

Step 1: Open Hyper‑V Manager
Step 2: Click "Virtual Switch Manager"
Step 3: Select the problematic virtual switch
Step 4: Expand the switch to see "Extensions"
Step 5: Look for enabled extensions like:
    - Microsoft Azure VFP Switch Filter Extension
    - Microsoft NDIS Capture
    - Microsoft Windows Filtering Platform
Step 6: Uncheck (disable) the extensions
Step 7: Click Apply and OK
Step 8: Restart the VM

According to a Microsoft Q&A user, disabling both enabled extensions made everything work again.

Outcome: Problematic Hyper‑V extensions are disabled, restoring connectivity.

6. Add a New Network Adapter and Remove the Old One

If the existing network adapter is corrupted, replacing it can resolve the issue. According to Microsoft Q&A, creating an additional network adapter on the VM and assigning it to the external virtual switch resolved the connection issue. This Hyper-V network adapter not working fix forces a fresh configuration.

Step 1: Open Hyper‑V Manager
Step 2: Right-click the VM and select Settings
Step 3: Click "Add Hardware" on the left side
Step 4: Select "Network Adapter" and click Add
Step 5: A new network adapter will be created
Step 6: Assign it to the External Virtual Switch
Step 7: Click Apply and OK
Step 8: Start the VM and verify network connectivity
Step 9: Go back to VM Settings
Step 10: Select the old, non‑functional network adapter
Step 11: Click Remove
Step 12: Click Apply and OK

According to Microsoft Q&A, this process forces the guest OS and Hyper‑V host to create a fresh, clean configuration for the network connection, bypassing whatever corrupted state the old adapter was in.

Outcome: A fresh network adapter replaces the corrupted one, restoring connectivity.

7. Fix Code 10 and Code 31 Errors in Device Manager

Code 10 (“Device cannot start”) and Code 31 (“Device driver loading failed”) errors can occur with Hyper‑V network adapters. According to a Server Fault discussion, the “Microsoft Hyper-V Network Adapter” can fail with Code 10 after 2‑3 months. This Hyper-V network adapter not working fix addresses these specific error codes.

Step 1: Open Device Manager on the host
Step 2: Click View → Show hidden devices
Step 3: Expand "Network adapters"
Step 4: Locate "Hyper-V Virtual Ethernet Adapter" or similar
Step 5: If it has a yellow exclamation mark, right-click and select Uninstall device
Step 6: Check "Delete the driver software for this device" if available
Step 7: Click Uninstall
Step 8: Restart your computer
Step 9: Open Hyper‑V Manager and restart the VM

Alternative: According to a PCOnline guide, if a yellow exclamation mark appears or the driver date is earlier than 2022, uninstall the device, check "Delete the driver software for this device," then click Action → Scan for hardware changes to trigger system reinstallation of the latest compatible driver.

Outcome: Code 10 and 31 errors are resolved by reinstalling the Hyper‑V network adapter driver.

8. Disable Hyper‑V and Re‑enable It

If all else fails, toggling Hyper‑V off and on can reset the entire virtualization stack. According to Microsoft Q&A, you may need to remove the Hyper‑V Virtual Network Adapter from Device Manager. This Hyper-V network adapter not working fix is a last resort but often works.

Step 1: Open the Start menu and search for "Turn Windows features on or off"
Step 2: Uncheck "Hyper-V" and click OK
Step 3: Restart your computer (required)
Step 4: Re-open "Turn Windows features on or off"
Step 5: Check "Hyper-V" and click OK
Step 6: Restart your computer again

Alternative: Remove Hyper-V Virtual Network Adapters
Step 1: Open Device Manager
Step 2: Click View → Show hidden devices
Step 3: Expand "Network adapters"
Step 4: Locate all Hyper‑V network adapters
Step 5: Right-click each one and select Uninstall device
Step 6: Restart your computer

According to Microsoft Q&A, removing the Hyper‑V Virtual Network Adapter fixed the issue for some users.

Outcome: Hyper‑V and its network adapters are reset, resolving persistent issues.

9. Perform a Network Reset

A network reset can resolve underlying networking issues affecting Hyper‑V. According to Microsoft Q&A, selecting Network reset under Settings > Network & Internet > Status > Reset now > Restart PC is a recommended step.

Step 1: Open Settings (Windows + I)
Step 2: Go to Network & Internet
Step 3: Click "Advanced network settings"
Step 4: Click "Network reset"
Step 5: Click "Reset now"
Step 6: Confirm and restart your computer

Alternative: Reset via Command Prompt
Step 1: Open Command Prompt as Administrator
Step 2: netsh winsock reset
Step 3: netsh int ip reset
Step 4: ipconfig /flushdns
Step 5: Restart your computer

According to Microsoft Q&A, this can help fix Ethernet and Hyper‑V problems following Windows updates.

Outcome: Network settings are reset, resolving configuration corruption.

10. Check BIOS/UEFI Settings

BIOS/UEFI settings can affect Hyper‑V functionality. According to TheWindowsClub, you may have enabled incorrect security settings for virtualization.

Step 1: Restart your computer
Step 2: Enter BIOS/UEFI (usually Del, F2, F10, or Esc)
Step 3: Look for virtualization settings:
    - Intel: "Intel VT-x" or "Intel Virtualization Technology"
    - AMD: "AMD SVM" or "AMD-V"
Step 4: Ensure virtualization is Enabled
Step 5: Look for "VT-d" or "AMD IOMMU" and enable it (if available)
Step 6: Look for "SR-IOV" and enable it (if needed for your setup)
Step 7: Save changes and exit

According to Microsoft Q&A, virtualization must be enabled in BIOS for Hyper‑V to work properly.

Outcome: BIOS virtualization settings are correctly configured for Hyper‑V.

11. Frequently Asked Questions

Why is my Hyper‑V network adapter not working?

Hyper‑V network adapter issues are typically caused by corrupted virtual switches, Windows updates that break network adapter emulation, outdated drivers, or Broadcom NIC VMQ issues. According to Microsoft Q&A, Windows updates can modify low-level driver configurations, causing the virtual network adapter to become non‑functional.

How do I fix a Hyper‑V network adapter that disappeared?

Open Hyper‑V Manager → right-click the VM → Settings → click Add Hardware → select Network Adapter → Add → assign it to the External Virtual Switch → Apply → OK. According to Microsoft Q&A, this forces the guest OS and host to create a fresh configuration.

What is Code 10 on a Hyper‑V network adapter?

Code 10 means “Device cannot start.” According to a Server Fault discussion, the “Microsoft Hyper-V Network Adapter” can fail with Code 10. Try uninstalling the adapter from Device Manager and restarting.

What is Code 31 on a Hyper‑V network adapter?

Code 31 means “Device driver loading failed.” According to a PCOnline guide, uninstall the device, check “Delete the driver software,” then click Action → Scan for hardware changes to trigger reinstallation of the latest compatible driver.

How do I fix Hyper‑V “Network cable is not connected”?

According to Microsoft Q&A, this often occurs after a Windows update. Try deleting the virtual switch, recreating it, and reconnecting VMs.

Does disabling VMQ fix Hyper‑V network issues?

Yes. According to ITFix, disabling Virtual Machine Queue (VMQ) on Broadcom NICs resolves random network connectivity issues.

Can Hyper‑V extensions block network connectivity?

Yes. According to Microsoft Q&A, removing the Microsoft Azure VFP Switch Filter Extension resolved connectivity issues.

How do I recreate a Hyper‑V virtual switch?

Open Hyper‑V Manager → Virtual Switch Manager → select the switch → Remove → New virtual network switch → External → Create → select the physical adapter → Apply → OK. Reconnect VMs to the new switch.

Does Windows 11 24H2/25H2 affect Hyper‑V networking?

Yes. According to Microsoft Q&A, Windows 11 25H2 introduced changes that affect virtual switch compatibility and network adapter emulation.

Where can I find more Windows 11 troubleshooting help?

Explore our Windows 11 Troubleshooting Hub and guides on Device Manager network adapter missing and network adapter driver updates.

12. Conclusion

Hyper-V network adapter not working fix is an essential skill for anyone running virtual machines on Windows 11. This guide has covered 9 proven methods—from verifying virtual switches and recreating them to disabling VMQ, removing Hyper‑V extensions, adding new network adapters, fixing Code 10/31 errors, and performing network resets. According to Microsoft Q&A, Windows updates can sometimes modify low-level driver configurations, causing the existing virtual network adapter to become non‑functional. By following this Hyper-V network adapter not working fix guide, you can restore connectivity to your virtual machines.

Start with the simplest fix — verifying the virtual switch connection — and escalate to recreating the switch or adding a new network adapter only if needed. This Hyper-V network adapter not working fix guide provides all the solutions you need.

For more Windows troubleshooting, explore our Windows 11 Troubleshooting Hub and guides on Device Manager network adapter missing and network adapter driver updates.

With the right approach from this Hyper-V network adapter not working fix guide, you can restore network connectivity to your virtual machines and keep your virtualized environment running smoothly.

For more Windows virtualization troubleshooting, explore our Windows 11 Troubleshooting Hub and guides on network performance optimization and packet loss optimization. With the right approach, you can resolve any Hyper‑V network issues and keep your virtual machines connected.