You have installed a virtual machine (VM) on VMware Workstation, VirtualBox or Hyper-V, but it stubbornly doesn't detect the Wi-Fi adapter? This problem is familiar to many, especially when testing network applications, connecting to corporate VPNs, or simply accessing the internet from a guest OS. In 80% of cases, the cause is not hardware failure, but incorrect virtualization settings, driver conflicts, or host system limitations.
In this article we will look at all possible reasons, for which a virtual machine can ignore your Wi-Fi adapter - from a simple lack of rights to complex conflicts between virtual network interfaces. You will receive step-by-step instructions For Windows 10/11, Linux (Ubuntu, Debian) and macOS, and you'll also learn how to bypass the limitations of popular hypervisors. We'll pay special attention to USB forwarding of Wi-Fi adapters - This is the most reliable connection method, but it requires proper configuration.
It doesn't matter whether you use the laptop's built-in Wi-Fi module or an external USB adapter (for example, TP-Link TL-WN725N or ASUS USB-AC56>) — the solutions in this article will help restore network connectivity in your virtual machine. Let's start with diagnostics!
1. Checking the basic conditions: what should be running before setting up the VM
Before messing with the virtual machine settings, make sure the problem isn't with the host system or the adapter itself. Follow this checklist:
Make sure the Wi-Fi adapter works in the main OS (check the network connection)
Disable VPN, proxy or firewalls (eg. Kaspersky, Avast)
Update your adapter drivers via device Manager (Windows) or lspci (Linux)
Check if the adapter is disabled in BIOS/UEFI (relevant for built-in modules)
Connect the adapter to another USB port (for external devices)-->
If Wi-Fi is working reliably on the host system, but the adapter isn't detected in the virtual machine, proceed to the next section. If the adapter isn't visible in the host OS either, the problem lies in:
- 🔌 Physical connection — check the cables (for USB adapters) or the M.2 slot contacts (for built-in modules).
- 🖥️ Drivers - download the latest version from the manufacturer's website (for example, for Intel AX200 or Realtek RTL8821CE).
- ⚙️ BIOS settings - some laptops (for example, Dell Latitude or Lenovo ThinkPad) block Wi-Fi when turned on
Secure Boot.
On macOS An additional complication is that the system may block uncertified USB adapters. If you use an external Wi-Fi module (for example, Alfa AWUS036ACH), check its compatibility with your version of macOS using the utility System Information → USB.
netsh wlan show drivers
Look for the line Hosted Network Support - if there "No", the driver is not working correctly.-->
2. Configuring a Network Adapter in a Virtual Machine: NAT vs. Bridge vs. USB
By default, virtual machines don't have direct access to the host's physical network devices. Instead, they use virtual interfaces, which can operate in several modes:
| Network mode | Description | Is it suitable for Wi-Fi? | Does it require host configuration? |
|---|---|---|---|
| NAT | The VM shares the host's IP address and accesses the Internet through its gateway. | ❌ No (uses a virtual adapter) | ❌ No |
| Bridge | The VM receives its own IP on the local network, just like a physical device. | ⚠️ Partially (depending on host drivers) | ✅ Yes (configuration in the hypervisor) |
| Host-Only | The network is only between the host and the VM, without internet access. | ❌ No | ❌ No |
| USB forwarding | Direct connection of a physical Wi-Fi adapter to the VM. | ✅ Yes (best option for Wi-Fi) | ✅ Yes (installing drivers in VM) |
If you need full Wi-Fi in a virtual machine (for example, for testing Wireshark or connections to hidden networks), USB forwarding — the only reliable way. In modes NAT or Bridge The VM will use the host's network stack, which limits functionality (e.g. it cannot connect to a different network than the host).
How to set up USB forwarding in VirtualBox:
- Connect the Wi-Fi adapter to the USB port.
- Start the VM and go to the menu
Devices → USB. - Select your adapter (eg. Realtek 802.11n WLAN Adapter).
- Install the driver in the guest OS (download from the manufacturer's website).
What should I do if my USB adapter is not listed in VirtualBox?
If your Wi-Fi adapter is not visible in the menu Devices → USB, check:
1. USB filters — in the VM settings (Settings → USB) add a new filter for your device.
2. VirtualBox version — Older versions (before 6.1) had a problem with USB 3.0. Update to the latest version.
3. Host drivers - install on Windows Oracle VM VirtualBox Extension Pack (download from the official website).
4. Conflicts with RNDIS - some adapters (for example, on a chip Ralink RT5370) require disabling the option Devices → USB → Enable USB 2.0 Controller (EHCI).
3. Driver conflicts: why the VM "doesn't see" the adapter even after forwarding
Let's say you've successfully forwarded a USB adapter to a virtual machine, but it still isn't working. In 90% of cases, the culprit is guest OS driversLet's consider typical scenarios:
- 🖥️ Windows in VM: The system may automatically install the wrong driver (for example, for Realtek RTL8188EU instead of RTL8188ETV). Check in
Device Manager— If there is a yellow triangle next to the adapter, remove the driver and install the correct one manually. - 🐧 Linux in VM: The kernel may not have a module for your chip. For example, for TP-Link TL-WN722N (chip AR9271) I need a package
firmware-atheros. Install it via:sudo apt install firmware-atheros - 🍎 macOS in VMApple blocks many USB adapters at the kernel level. The solution is to patch the cache (kext) or use special VM builds (for example, macOS-Unlocker for VMware).
To diagnose in Linux, run the following commands:
lsusb
- a line with your adapter should be displayed (for example, ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS). If it's not there, the problem is at the USB forwarding level.
dmesg | grep -i wifi
— will show kernel module loading errors.
On Windows in VM also check driver version:
- Open
device Manager(Win + X → Device Manager). - Find your adapter in the section
Network adapters. - Right click →
Properties → Driver. - If the version is older than 2021, download the latest version from the manufacturer's website.
VirtualBox|VMware Workstation|Hyper-V|Parallels Desktop|Other-->
4. VMware Workstation Features: Why Wi-Fi Doesn't Work in Bridge Mode
VMware Workstation (and its free analogue VMware Player) often encounters problems with network adapters due to the peculiarities of virtual network interfaces. If you selected the mode Bridge, but the VM does not see the network, check:
- 🌉 Virtual Switch Settings: Go to
Edit → Virtual Network Editor(Administrator rights required) Make sure your adapter is bound toVMnet0(bridge mode). - 🔄 Conflict with Hyper-V: On Windows 10/11 Hyper-V may block VMware network adapters. Disable it via:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All - 🔒 Windows Firewall: Sometimes it blocks bridge traffic. Add an exception for
vmware-vmx.exe.
If you use USB forwarding In VMware, make sure that:
- The option is enabled in the VM settings
USB Controller → USB 3.0(for modern adapters). - Installed VMware Tools (or open-vm-tools for Linux).
- On the menu
VM → Removable DevicesYour adapter is checked.
For macOS VMware has a separate issue: the system may not see USB devices due to lack of support xhci. The solution is to add to the VM configuration file (.vmx) line:
usb_xhci.present = "TRUE"
-->sudo modprobe -r vmw_vmci vmw_vsock vmxnet3 vmxnet vmwgfx
sudo modprobe vmw_vmci vmw_vsock vmxnet3 vmxnet vmwgfx
5. VirtualBox: How to make a virtual machine see a Wi-Fi adapter
Oracle VirtualBox — the most popular free hypervisor, but its USB and network settings often cause problems. If your Wi-Fi adapter isn't visible in the VM, follow these steps:
- Check the version of VirtualBox and Extension Pack:
- Download the latest version from official website.
- Install Oracle VM VirtualBox Extension Pack (supports USB 2.0/3.0).
- Configure the USB controller:
- In the VM settings (
Settings → USB) selectUSB 3.0 (xHCI). - Add a filter for your adapter (button
+on the right).
- In the VM settings (
- Start the VM and connect the adapter to the USB port.
- In the VM menu, select
Devices → USB → [Your adapter]. - Install the driver in the guest OS (see section 3).
If the adapter is still not visible, check:
- 🔌 Conflict with RNDIS: Some adapters (eg. Edimax EW-7811Un) require disabling the option
Devices → USB → Enable USB 2.0 Controller (EHCI). - 🛠️ USB Compatibility Mode: In the VM settings (
Settings → USB) try changing the controller version from3.0on2.0or vice versa. - 🔄 Conflict with antivirus software: Kaspersky, Avast or Bitdefender may block USB forwarding. Add an exception for
VirtualBoxVM.exe.
How to check if VirtualBox sees your USB adapter?
Start VirtualBox with USB device log:
VBoxManage list usbhost
If your adapter is listed but isn't forwarded to the VM, the problem lies with the filters or drivers in the guest OS.
6. Hyper-V and Windows Sandbox: Why Wi-Fi Almost Never Works Here
Hyper-V (embedded Windows hypervisor) and Windows Sandbox have strict restrictions on access to physical devices. By default, they do not support USB passthrough, so connecting a Wi-Fi adapter directly is impossible. However, there are workarounds:
- 🌉 Use an external bridge:
- Create
External virtual switchVHyper-V Manager. - Link it to your Wi-Fi adapter (in
Control Panel → Network Connectionsa new device will appear). - Configure the VM to use this switch.
- Create
⚠️ Attention: This method only works if your Wi-Fi adapter supports the mode Promiscuous Mode (most home adapters do not support it).
- On the host, enable Wi-Fi distribution via
Mobile hotspot(Settings → Network & Internet). - In the VM, configure the network adapter in the mode
NATorDefault Switch. - 🖥️ Install a second OS with virtualization support:
If you critically need direct access to Wi-Fi, install Windows 10/11 Pro in dual boot mode and use VirtualBox or VMware instead of Hyper-V.
Cons: The VM will use the same network as the host and will not be able to connect to other Wi-Fi networks.
For Windows Sandbox The situation is even worse: this sandbox is isolated from the host system and has no access to either USB or physical network adapters. The only way to access the internet is through NAT host.
7. macOS Problems: Why Hackintosh and VMs Don't See Wi-Fi
Virtual machines with macOS (especially DIY "Hackintosh") face unique challenges due to Apple's policies. The main reasons Wi-Fi isn't working are:
- 🍎 Lack of drivers for non-native adapters:
macOS only supports a limited list of Wi-Fi chips (mostly Broadcom). Adapters on Realtek, Atheros or Mediatek will not work without patches.
Solution: Use chip adapters Broadcom BCM43xx (For example, Fenvi T919) or install patched caches (
kext) through OpenCore. - 🔒 Blocking USB in VMware/Parallels:
Apple prohibits virtualization of macOS on non-Apple hardware. To bypass this, special patches are required (for example, macOS-Unlocker for VMware).
- 🖥️ Conflict with VirtualSMC:
If you use VirtualSMC to emulate the SMC chip, it can block network devices. Try replacing it with FakeSMC.
To diagnose macOS VM, run:
system_profiler SPUSBDataType
- Check if the adapter is visible in the list of USB devices.
networksetup -listallhardwareports
- will show all network interfaces (look for Wi-Fi or AirPort).
If the adapter is not detected, try:
- Add it
Device IDin the config OpenCore (chapterNVRAM → Add → 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 → UIScale). - Install the patched one
IO80211Family.kext(for example, from a repository acidanthera on GitHub). - Disable
Secure Bootin BIOS (for Hackintosh on real hardware).
8. Alternative solutions: if nothing helps
If all the above methods do not work, consider alternative approaches:
- 🔄 Use Ethernet over USB:
Connect the host to the router via cable, and configure it in the VM
BridgeorNATThis will provide a stable connection, even if not via Wi-Fi. - 📡 Sharing Wi-Fi from your phone:
Turn on the access point on your smartphone and connect the VM to it via
NATorUSB-tethering. - 🖥️ Dual Boot:
If virtualization is critical for Wi-Fi operations (for example, for network testing), install the second OS on a separate disk partition.
- ☁️ Cloud VMs:
Services like AWS, Google Cloud or Azure Provide virtual machines with network access. The downside is traffic fees.
If you need Wi-Fi in VM for specific tasks (for example, testing Kali Linux for pentesting), consider:
- 🛠️ Specialized distributions: Tails OS or Parrot Security have built-in support for many Wi-Fi adapters.
- 🔧 USB-paste: Devices like Yubico or SoloKey can emulate network interfaces.
- Use built-in Wi-Fi module in mode
Bridge(if the hypervisor supports it). - Connect via Bluetooth-tethering (for example, share the Internet from your phone).
- Use USB-C hub with USB-A port for external adapter.
- 🔄 Virtualization service: Open
services.mscand make sure thatHyper-V Virtual Machine Managementlaunched. - 🛠️ Virtual adapter drivers: IN
Device Managerupdate drivers forVirtualBox Host-Only NetworkorVMware Virtual Ethernet Adapter. - 🔒 Firewall: Reset rules for
vmware-authd.exeorVBoxSVC.exe. - 🔍 Forward a USB adapter in VM (see section 3).
- 📡 Connect manually:
- On Windows in VM:
Control Panel → Network and Internet → Manage wireless networks → Add. - On Linux in VM:
nmcli dev wifi connect "SSID" password "password" hidden yes
- On Windows in VM:
FAQ: Frequently asked questions about Wi-Fi in virtual machines
Is it possible to connect a Wi-Fi adapter to a VM on a laptop without USB ports?
Yes, but with restrictions:
On MacBook with a chip Apple M1/M2 Forwarding USB Wi-Fi adapters to VMs is practically impossible due to limitations Rosetta 2.
Why did Wi-Fi stop working in a VM after updating Windows 11?
Windows updates often reset virtual network settings. Check:
If the problem appears after a major update (for example, Windows 11 23H2), try rolling back to a previous version or wait for a patch from Oracle/VMware.
How to connect a VM to a hidden Wi-Fi network?
If the network is hidden (does not broadcast SSID), you will need:
⚠️ Attention: In modeNATorBridgeThe VM will not be able to connect to a hidden network other than the host. You must use USB forwarding.
Is it possible to use Wi-Fi Direct in a virtual machine?
Technically possible, but with serious limitations:
- ✅ USB forwarding: If your adapter supports Wi-Fi Direct (For example, Intel Wireless-AC 9260), forward it to the VM and install the driver.
- ❌ NAT/Bridge: In these modes, Wi-Fi Direct does not work because the VM uses a virtual network interface.
- ⚠️ macOS VM: Wi-Fi Direct requires a patch
IO80211Family.kextand is often unstable.
For testing Miracast or AirPlay It is better to use a real device or a cloud VM with a GPU.
How to speed up Wi-Fi in a virtual machine?
Wi-Fi speed in a VM is typically 30-50% slower than on the host. To optimize:
- 🔌 Use USB 3.0: In the VM settings, select
USB 3.0 (xHCI)instead ofUSB 2.0. - 📶 Disable adapter power saving:
- On Windows host:
Device Manager → Network Adapters → [Your adapter] → Properties → Power Management → Uncheck "Allow the computer to turn off...". - On Linux host:
iwconfig wlan0 power off.
- On Windows host:
- 🖥️ Allocate more VM resources: Increase the number of CPU cores and RAM (at least 2 GB for stable network operation).
- 🔄 Use a wired connection: If possible, connect the host to the router via cable, and configure it in the VM
Bridge.
To test the speed in VM use iperf3 or Speedtest CLI:
speedtest-cli --simple