Network Adapter Missing on Windows? Best Way to Fix It

When network adapters go missing — WiFi, Ethernet, or both — the laptop is an island. No browsing for fixes, no downloading drivers, no looking up error codes. That isolation is what makes this problem feel so severe, but the repair sequence is well-established and works from the least disruptive step to the most.

The “best way” isn’t a single trick; it’s the order of operations. Reveal hidden devices, check BIOS, reset the stack, reinstall drivers cleanly, and only then consider hardware. Each step is quick, and most people find the adapter by step three or four.

Why this happens

• Driver corruption from Windows Update: Updates replacing working network drivers with broken versions is the leading cause.
• Adapters disabled in BIOS: WLAN/LAN toggles in BIOS hide the hardware from Windows completely.
• Network stack corruption: Damaged Winsock/TCP-IP components can suppress adapter enumeration.
• Fast Startup caching broken state: Hybrid shutdown preserves the missing-adapter state across reboots.
• Chipset driver failure: Both adapters hang off platform infrastructure that needs correct chipset drivers.
• Power management disabling adapters: Aggressive power saving can power-gate network hardware into invisibility.
• Third-party VPN/filter drivers: Network filter drivers from VPNs can break adapter enumeration when corrupted.
• Hardware failure: Dead WiFi module or Ethernet controller, though both failing simultaneously is rare.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Prepare your lifeline — get drivers on USB first

1. On another device, visit your laptop maker’s support page and download the wired (LAN) and wireless (WLAN) drivers for your exact model.
2. Copy them to a USB flash drive. You cannot download them after starting if the fix requires reboots without networking.
3. Alternatively, enable USB tethering on your phone — it gives the laptop internet through the phone, independent of its network adapters.
4. This preparation step saves you from being stranded mid-repair with no way to fetch drivers.

Fix 2: Reveal hidden and disabled adapters

1. Open Device Manager → View → Show hidden devices.
2. Expand Network adapters and look for grayed-out entries (right-click → Enable device) or warning-flagged ones.
3. Check Other devices for unknown network controllers — these are adapters Windows sees but can’t identify.
4. If adapters appear here, the hardware is fine and you’re dealing with driver or settings issues — continue to Fix 4.

Fix 3: Check BIOS for LAN/WLAN toggles

1. Restart into BIOS/UEFI (F2/Del during boot).
2. Under Advanced, Devices, or Security, find WLAN, Wireless, LAN, or Onboard LAN options.
3. Set all network devices to Enabled. If you recently updated BIOS, use Load Optimized Defaults first — updates sometimes disable devices.
4. Save and boot. BIOS-disabled adapters are invisible to every OS-level fix, so this check is mandatory.

Fix 4: Reset the network stack and disable Fast Startup

1. In an admin Terminal, run: netsh winsock reset, netsh int ip reset, ipconfig /flushdns.
2. Disable Fast Startup (Control Panel → Power Options → Choose what the power buttons do).
3. Shut down fully, unplug, hold power 30 seconds, then boot — forcing complete hardware re-enumeration.
4. Also run Settings → Network & internet → Advanced network settings → Network reset for good measure. This combination resolves the post-update disappearance variant in most cases.

Fix 5: Remove VPN and filter drivers

1. Uninstall VPN clients temporarily from Settings → Apps — corrupted filter drivers are a known enumeration-breaker.
2. In Device Manager → View → Show hidden devices, expand Network adapters and uninstall any WAN Miniport entries with warnings, plus any virtual/VPN adapters.
3. In an admin Terminal, run netcfg -d to remove all network devices and configurations (you’ll reinstall after).
4. Reboot and check whether the physical adapters reappear — if they do, reinstall the VPN fresh afterward.

Fix 6: Clean-reinstall chipset then network drivers

1. Install the chipset driver package from the OEM support page first — reboot.
2. Install the Ethernet driver, then the wireless driver, from your USB prepared in Fix 1 — reboot after each.
3. In Device Manager, verify both adapters appear without warnings and check driver versions match what you installed.
4. This bottom-up rebuild fixes cases where the platform infrastructure itself was broken — the same principle behind WiFi 6 driver repairs .

Fix 7: Test hardware isolation

1. Boot a Linux live USB and check whether network adapters appear there. Visible in Linux = Windows problem; invisible = hardware/BIOS problem.
2. Run the manufacturer’s built-in diagnostics (Dell F12, Lenovo F10) — most include network adapter tests.
3. If WiFi is missing but Ethernet works (or vice versa), the failed adapter is isolated — replace or work around just that one.
4. A $15 USB WiFi or USB Ethernet adapter is a perfectly respectable permanent workaround for a dead internal adapter.

Fix 8: Lock in the fix and document

1. Once working, set Device Installation Settings to No to stop Windows Update replacing your drivers.
2. Save the working driver installers from Fix 1 in a labeled folder — they’re your known-good set.
3. Create a restore point named “Network adapters working” for one-click recovery.
4. For Intel wireless specifically, the Intel driver detection tool offers a sanctioned update path that won’t break things the way Windows Update does.

Closing

A missing network adapter is a visibility problem with a best-practice sequence: prepare drivers offline, reveal hidden devices, check BIOS, reset the stack, reinstall bottom-up. Follow it and the adapters come back — isolated, diagnosed, and locked in against the next update. Save this sequence somewhere you can find it offline, because the cruel irony of network problems is that you need the network to look up the fix; a printed checklist or a phone bookmark turns the next outage from a crisis into a routine. Preparation is the whole game with network failures — the five minutes you spend now saves an hour of real panic later.

Frequently asked questions