If your virtual machine (VM) has lost its network connection after updating Windows 11, or if the adapter simply won’t connect, this guide will walk you through the most common fixes. You’ll learn how to reset the virtual switch, reinstall the virtual network adapter, and adjust Windows 11 settings that often block VM traffic.
What You’ll Need
- Administrator access to the Windows 11 host machine
- The name of your virtual machine and the virtualization software you use (Hyper-V, VirtualBox, VMware Workstation, or Parallels)
- A basic understanding of your VM’s network mode (NAT, Bridged, or Host-Only)
Step-by-Step
- Identify the virtual network adapter type. Open your virtualization software and go to the VM’s settings. Look for the Network section. Note whether it’s set to NAT, Bridged, or Host-Only. This matters because each mode uses a different virtual switch.
- Check the VM’s network adapter in Device Manager (inside the VM). Start the VM, log in to the guest OS (Windows, Linux, etc.), and open Device Manager. Expand “Network adapters.” If you see a yellow exclamation mark next to the adapter, right-click it and select “Uninstall device.” Check “Delete the driver software for this device” if offered, then restart the VM. Windows will reinstall the driver automatically.
- Reset the virtual switch on the host. In Hyper-V, open Hyper-V Manager, right-click the host name, and select “Virtual Switch Manager.” For each virtual switch, click “Remove” and then recreate it with the same name and type. In VirtualBox, go to File > Host Network Manager and remove any host-only adapters, then recreate them. In VMware, open Virtual Network Editor and click “Restore Defaults.”
- Re-add the network adapter to the VM. Shut down the VM completely (not just save state). In the VM settings, remove the current network adapter, then add a new one with the same type (e.g., Intel PRO/1000 MT Desktop). Save and start the VM.
- Toggle the adapter in the guest OS. Inside the VM, open Control Panel > Network and Sharing Center > Change adapter settings. Right-click the active adapter and select “Disable,” then right-click again and select “Enable.” This forces a renegotiation with the virtual switch.
- Check Windows 11 firewall settings on the host. Open Windows Security > Firewall & network protection. Click “Allow an app through firewall.” Ensure your virtualization software (e.g., VirtualBox, VMware, Hyper-V) is allowed on both Private and Public networks. If not, click “Change settings,” then “Allow another app,” and browse to the .exe file.
- Reinstall the virtualization software’s network drivers. For VirtualBox, go to the installation folder and run the driver installer (e.g., VBoxNetLwf.inf or VBoxNetAdp6.inf) as administrator. For VMware, run the “VMware Network Editor” and click “Change Settings” to repair the virtual network adapters.
- Use Windows 11’s network reset as a last resort. On the host, go to Settings > Network & internet > Advanced network settings > Network reset. This reinstalls all network adapters and resets network components. You’ll need to reconfigure your VM switches afterward.
Common Mistakes
- Not shutting down the VM before changing adapter settings. Many changes only apply when the VM is fully powered off, not saved or paused.
- Mixing up NAT and Bridged modes. If you need the VM to get an IP from your router, use Bridged. If you only need internet access, NAT is fine. Using the wrong mode can cause connection failures.
- Forgetting to allow the VM software through the Windows firewall. Windows 11 updates often reset firewall rules, blocking VM traffic.
- Deleting the default virtual switch in Hyper-V. The “Default Switch” is used for NAT. Removing it without creating a new NAT switch will break internet access for all VMs.
- Ignoring the guest OS’s own network settings. Sometimes the VM adapter is fine, but the guest OS has a static IP that no longer matches the virtual subnet.
Tips
- Use a static IP inside the VM for predictable connectivity. If you use NAT, the default gateway is usually 10.0.2.2 (VirtualBox) or 192.168.137.1 (Hyper-V). Set the VM’s IP to something like 10.0.2.15 for VirtualBox.
- Keep your virtualization software updated. Windows 11 updates can break compatibility; a new version of VirtualBox or VMware often fixes network issues.
- Use the “Bridged” mode for LAN access. If you need to access the VM from other devices on your network, Bridged mode is more reliable than NAT.
- Export and import the VM as a backup. Before making drastic changes, export the VM so you can restore it if something goes wrong.
Troubleshooting
If the steps above don’t work, try these additional checks:
- Check the virtual switch status. In Hyper-V Manager, under Virtual Switch Manager, ensure the switch is set to “External” and the correct physical NIC is selected. If you have multiple NICs, the wrong one might be chosen.
- Disable IPv6 on the virtual adapter. Sometimes IPv6 conflicts cause issues. In the guest OS, go to adapter properties and uncheck “Internet Protocol Version 6 (TCP/IPv6).”
- Run network diagnostics inside the guest OS. Open Command Prompt as admin and run
ipconfig /releasethenipconfig /renew. If you get an APIPA address (169.254.x.x), the VM isn’t getting a DHCP lease. - Check the host’s physical network connection. If the host itself has no internet, the VM won’t either. Test with another device.
- Temporarily disable the firewall on the host. If the VM connects after disabling the firewall, you know the firewall is the issue. Re-enable it and add the correct rules.
- Look for conflicting third-party VPN software. Some VPNs install virtual adapters that interfere with VM networking. Disable or uninstall them temporarily.
Frequently Asked Questions
Why does my VM show “No internet access” but the host is fine?
This usually means the VM’s network adapter is configured incorrectly, or the virtual switch is not properly connected to the host’s physical NIC. Check the adapter mode (NAT vs Bridged) and reinstall the virtual switch.
Can I fix the network adapter without reinstalling the VM?
Yes, most fixes don’t require reinstalling the VM. You can reset the virtual switch, re-add the adapter, or reinstall drivers without losing any VM data.
Why does my VM lose network after a Windows 11 feature update?
Windows updates can reset firewall rules, change network adapter bindings, or update drivers that conflict with virtualization software. Re-allow the software through the firewall and reinstall the virtual network drivers.
Is it better to use NAT or Bridged mode for my VM?
Use NAT if you only need the VM to access the internet and the host. Use Bridged if you want the VM to appear as a separate device on your local network, so you can SSH or RDP into it from other devices.
What does “Virtual network adapter not found” mean?
It means the host’s virtualization software cannot detect the virtual switch or the adapter driver is missing. Reinstall the virtualization software’s network components, or run the repair installer.
Can I use a USB Wi-Fi adapter on the host to improve VM networking?
Yes, but you’ll need to configure the virtual switch to bind to that specific adapter. In Hyper-V, create an external switch and select the USB Wi-Fi adapter as the physical NIC.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Show User Library in macOS High Sierra & Sierra
- Device Manager Shortcut: Windows 10 Desktop
- How to Remove Forgotten Passcode from iPhone
- Fix Slow Wi-Fi Problem iPhone X: 9 Steps
- How to Listen to Deleted Voicemails on iPhone
- How to Check if a Candidate Accepts Crypto Donations