A network adapter that Windows 11 can’t find — the Wi-Fi or Ethernet option missing from Settings entirely, no network adapters in Device Manager, or the adapter visible but showing a yellow warning — is genuinely disruptive because most fixes require internet access that you currently don’t have. This guide covers both the diagnostic and the offline fix paths. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Quick triage: open Device Manager (Win+X → Device Manager) → expand “Network adapters.” If your adapters are listed there but with yellow warning triangles: driver issue, fixable. If you see “Unknown device” or “Other devices” with yellow triangles: the hardware is detected but no driver is installed. If no network adapters appear at all: hidden or disabled, or hardware failure.
Show hidden adapters
Device Manager hides disabled and removed devices by default. View → Show hidden devices — this reveals adapters that were previously working but are currently disabled. If your adapter appears in the hidden list (slightly greyed out): right-click → Enable device. It should reinitialise and appear in the normal list.
Also check: Device Manager → Action menu → Scan for hardware changes. This forces Windows to re-enumerate all hardware, sometimes causing a previously-invisible adapter to appear. If it appears after scanning: the adapter was present but Windows hadn’t registered it, which sometimes happens after botched driver updates.
Run the network reset commands
Before touching drivers: the Windows networking stack can be corrupted independently of the adapter hardware. A network stack reset resolves this. Open Command Prompt as Administrator:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renewRestart Windows after running these. Winsock reset specifically re-registers the Windows socket interface that networking applications use — when corrupted, adapters can be present in Device Manager but still not function correctly. This is a common symptom after failed VPN installations or aggressive network tool uninstalls.
Driver reinstall — the main fix
If the adapter appears in Device Manager with a warning: right-click → Update driver → “Browse my computer for drivers” → “Let me pick from a list of available drivers on my computer” → select the adapter type → choose a driver from the list (Microsoft’s generic driver usually works as a starting point).
Or uninstall: right-click → Uninstall device → check “Delete the driver software for this device” → confirm → restart Windows. On reboot, Windows automatically reinstalls a basic driver for recognised hardware. For Intel Wi-Fi and most Ethernet adapters, this generic driver works immediately.
For the full manufacturer driver: this requires internet access on another device. Download the driver on a phone or different computer → transfer via USB drive → install offline. Intel Wireless adapters: intel.com/content/www/en/us/download-center → Wireless. Realtek Ethernet: your motherboard or laptop manufacturer’s support page (the specific-model driver, not Realtek’s generic package).
BIOS-level adapter disable
On some machines — especially business laptops — the Wi-Fi adapter can be disabled in BIOS. IT departments sometimes do this deliberately for security. Restart → enter BIOS (F2 or Delete at POST) → look in “Security” or “Advanced” or “Wireless” sections → find “WLAN” or “Wireless LAN” or similar → ensure it’s Enabled.
Also: BIOS has Ethernet on/off settings on some motherboards (“LAN Controller” in Advanced settings). If the BIOS shows it as disabled: enable it. This is rare on consumer hardware but happens on server-grade motherboards and corporate-deployed PCs.
Our guide on Wi-Fi not working troubleshooting covers the software-side connectivity issues after the adapter is detected, and our Ethernet troubleshooting covers the wired equivalent. For downloading drivers offline and transferring to a system without internet, Microsoft’s driver download infrastructure at Microsoft Update Catalog lets you search for specific driver versions by hardware ID for offline installation.
Hardware ID — finding the right driver without internet
When the adapter shows as “Unknown Device” in Device Manager, you can find its hardware identity and match it to the correct driver even without internet on that machine.
Right-click “Unknown Device” → Properties → Details tab → “Hardware Ids” in the dropdown. You’ll see values like PCIVEN_8086&DEV_02F0. The VEN number is the vendor ID (8086 = Intel), the DEV number is the device ID. Search these on another device at pci-ids.ucw.cz or on Google → you’ll find the exact chip. Now download the correct driver for that specific chip on the second device → transfer → install.
This approach works for any unrecognised hardware, not just network adapters. It’s the definitive way to identify mystery hardware.
Windows Update’s driver option
If you can get any internet connection (phone hotspot, different machine to download and transfer): Windows Update sometimes includes network adapter drivers not found through Device Manager’s automatic search.
Settings → Windows Update → Advanced options → Optional updates → Driver updates → see if a network adapter driver appears there. These are manufacturer-vetted drivers submitted to Microsoft’s certification system — reliable and specifically matched to your hardware.
VPN software removing virtual adapters
This is surprisingly common. VPN software (Cisco AnyConnect, GlobalProtect, NordVPN, and others) installs virtual network adapters alongside the physical ones. When they uninstall badly — after a crash, a forced uninstall, or a Windows Update conflict — they leave behind broken virtual adapter entries or, worse, corrupt the overall network adapter registry.
If the problem started after installing or uninstalling a VPN: use Microsoft’s “Fix it” tool for network problems, or reinstall the VPN software cleanly and then uninstall it properly. Sometimes reinstalling and doing a clean uninstall of a VPN resolves the damage the first bad uninstall caused.
Check: Device Manager → View → Show hidden devices → look for Cisco, GlobalProtect, NordVPN, or similar virtual adapters with yellow warnings. Right-click → Uninstall these specifically. Then run the winsock reset commands above. This sequence clears VPN detritus that blocks the real adapter from initialising.
Windows 11 roll-back affecting drivers
Windows 11 automatically installs driver updates via Windows Update. Occasionally a pushed driver update breaks the network adapter — a real regression from a good driver to a buggy one. Symptoms: worked fine until Windows Update ran overnight, now the adapter is missing or shows an error.
Roll back: Device Manager → Network adapters → find the adapter → right-click → Properties → Driver tab → “Roll Back Driver” (if greyed out: no previous driver saved). If Roll Back is available: click it → choose a reason → restart. If greyed out: download the manufacturer’s previous driver version and install it manually, forcing a downgrade.
Prevent Windows from pushing the broken driver again: after rolling back, temporarily hide the update. Settings → Windows Update → look for “Pause updates” to pause for a week or two while waiting for a fix.
Physical hardware checks
For desktops with PCIe Wi-Fi cards: ensure the card is firmly seated. PCIe cards sometimes work loose, especially in towers that get moved. Power off → open case → press firmly on the card. Reseat in a different PCIe slot if available.
For laptop Wi-Fi cards: these are small M.2 cards inside the laptop. Very occasionally they work loose from the slot after physical impact. Accessing them usually requires significant disassembly — check iFixit for your specific laptop model.
For USB Wi-Fi adapters: unplug → plug into a different port → if it appears in Device Manager: the original port had an issue (power, USB controller). Move to the new port permanently.
| Device Manager shows | Meaning | Fix |
| Adapter with yellow triangle | Driver error | Uninstall device → restart (auto-reinstall), or install manufacturer driver |
| “Unknown device” with triangle | No driver installed | Get Hardware ID → find correct driver → install |
| No network adapters at all | Disabled, hidden, or hardware fault | View → Show hidden devices; check BIOS; check physical connection |
| Adapter listed but not working | Network stack corruption | Netsh winsock reset + ip reset → restart |
| VPN-related adapter errors | VPN software detritus | Reinstall VPN → clean uninstall → winsock reset |
| Stopped after Windows Update | Driver regression | Roll back driver; pause updates |
The network stack reset (winsock and IP reset commands) resolves a wide variety of adapter issues that look hardware-related but are actually software corruption. It’s worth trying before doing anything else because it’s quick, safe, and handles a large category of problems. Driver reinstall handles everything else except genuine hardware failure.
Getting drivers offline using phone tethering
This situation — no network adapter, no internet access on the affected machine — is solved cleanly with USB tethering from a smartphone. Connect your phone via USB → on Android, Settings → Hotspot & tethering → USB tethering. iPhone: the Lightning/USB-C cable tethering also works. Windows usually installs the “Remote NDIS” or “RNDIS Ethernet Gadget” driver automatically, giving you temporary internet access through the phone.
Once USB-tethered: download the correct Wi-Fi or Ethernet driver → install → restart → the proper network adapter should appear. No external USB drive needed. This is by far the most convenient offline connectivity method when the main adapters are broken.
Safe Mode networking test
If the adapter works in Safe Mode with Networking (hold Shift → Restart → Troubleshoot → Advanced options → Startup settings → Restart → press 5) but not in normal Windows: a startup program, service, or driver is conflicting.
In Safe Mode with Networking, only core drivers load. The network adapter working there means the hardware and its driver are fine — something loaded during normal startup is the interference. Enable the adapter in Safe Mode → get online → download drivers for other components that might be conflicting (particularly VPN software, antivirus, and third-party network tools).
Identify the startup conflict: normal boot → Services.msc → disable non-Microsoft services one at a time → restart to test → repeat until the adapter returns. Once the conflicting service is found: update or uninstall that service’s parent software.
Windows system file corruption
System File Checker repairs corrupted Windows system files that might be affecting network adapter initialisation. Admin Command Prompt:
sfc /scannowRuns for 10-20 minutes. If it reports “Windows Resource Protection found corrupt files and repaired them”: system files were the issue. Restart and test the adapter. If SFC can’t repair (rare): follow up with DISM to restore the Windows component store: DISM /Online /Cleanup-Image /RestoreHealth → then run sfc /scannow again.
When it’s actually hardware failure
If the network adapter doesn’t appear in Device Manager even with hidden devices shown, BIOS shows it as present, and reinstalling drivers doesn’t help: the adapter itself may have failed. Hardware failure in Wi-Fi chips is uncommon but happens, especially after electrical events (nearby lightning, power surge) or physical damage.
For laptops with built-in Wi-Fi: the fastest workaround is a USB Wi-Fi adapter (£15-£25, plug and play with Windows’ built-in drivers for common chipsets). This gives you immediate connectivity without waiting for a repair. For desktops with built-in Ethernet: a USB-to-Ethernet adapter costs under £15 and bypasses the failed port completely. Both are practical and fast solutions while you decide on a longer-term repair strategy.
External USB adapters are also useful as diagnostic tools: if the USB adapter works but the internal adapter doesn’t: you’ve confirmed hardware failure in the internal adapter. You now know exactly what needs repair or replacement, without any ambiguity about whether it’s software or hardware.
Temporary workarounds while diagnosing
Being completely offline makes troubleshooting harder. Practical ways to get temporary internet access to aid the fix:
- USB tethering from a phone (described above) — most versatile
- USB Wi-Fi dongle on another machine → download drivers → transfer via USB flash drive
- Mobile hotspot from a phone → connect via a working USB Wi-Fi adapter
- Ethernet cable from the router directly if you have a working Ethernet port
Any internet connection — even slow, temporary, or from a different adapter — unlocks the ability to download the correct driver, which is usually the key to the whole fix. Once you have the right driver installed and network access restored: note the driver version. If Windows Update keeps pushing a broken driver: use Device Manager to block that specific update (right-click → Update driver → “Specify which device to update” → block the version that broke things) so it doesn’t regress again.
For most “network adapter not found” situations, the combination of showing hidden devices, running network stack resets, and reinstalling the driver resolves the issue. The hardware failure and BIOS-disable scenarios are less common but worth checking if the standard fixes don’t help — they present identically from the user’s perspective but need completely different approaches.
The tethering approach deserves special mention because it’s underused: it’s faster than USB flash drive driver transfers, requires no advance preparation, and turns a frustrating “no internet to download the fix” situation into a solvable problem within minutes of finding the right driver. Keep it in your troubleshooting toolkit for any future network adapter issues. You might also run into Windows 11 Network Adapter Keeps Disabling.
