Wi-Fi drivers
Resolve dropped connections, slow speeds, and missing network adapters.
You might also need
Wi-Fi drivers we cover
What does a wi-fi driver do?
A Wi-Fi adapter driver binds the physical radio silicon to the Network Driver Interface Specification, the NDIS layer that Windows uses to move Ethernet-style frames to and from wireless hardware. Your wireless network interface card is usually an M.2 2230 module on the CInvNGFF key-A/E slot, or a radio soldered next to the chipset, and the driver exposes its transmit and receive queues to the operating system. Above NDIS sits the Native Wi-Fi (Wlansvc) service, which the driver feeds with scan lists, association state, and signal quality readings.
One of the driver's core jobs is band and channel management. It reports which channels the radio may use under your regulatory region, decides when to steer a session from a congested 2.4GHz channel to a cleaner 5GHz one, and on Wi-Fi 6E hardware it unlocks the 6GHz band where local rules permit. It also negotiates channel bonding, so two adjacent 20MHz channels combine into 40MHz, 80MHz, or 160MHz for higher throughput.
Why keeping it updated matters
A wireless radio lives in a hostile, shared environment, so its driver is patched far more often than most people expect. Router firmware changes, new WPA3 transition-mode quirks, and freshly certified access points all expose edge cases that a stale Wi-Fi adapter driver never anticipated, and the usual result is a link that associates then silently stops passing traffic.
Security is the blunter reason. Flaws such as the KRACK key-reinstallation weakness and the FragAttacks aggregation bugs were fixed in driver and supplicant updates, not in hardware, so an un-patched WNIC keeps a known hole open. Keeping the driver current is how those fixes actually reach the radio on your machine.
Common warning signs of wi-fi driver failure
- The wireless network interface card disappears from Device Manager and returns Code 43 after resume from sleep
- The adapter associates with the router but Windows reports 'No internet, secured' because DHCP never completes
- Link rate collapses to 802.11n speeds and 160MHz channel bonding is greyed out in the advanced properties tab
- Roaming between mesh access points drops the session instead of handing off, forcing a manual reconnect
- WPA3 networks reject the machine with repeated password prompts while WPA2 networks join without trouble
- The 5GHz and 6GHz SSIDs are invisible even though nearby phones list them, hinting at a regulatory-region mismatch
How to fix wi-fi driver problems
Restart the radio and clear the association state
In Device Manager, expand Network adapters, right-click the wireless network interface card and choose Disable device, wait ten seconds, then Enable device. This forces a fresh NDIS bind and clears a stuck association without a full reboot.
Reset the network stack that sits above the driver
Open an elevated command prompt and run netsh winsock reset and netsh int ip reset, then reboot. This rebuilds the Winsock catalogue and TCP/IP bindings that a flaky WPA handshake can leave in a bad state.
Reinstall the current driver cleanly
Right-click the adapter, choose Uninstall device, and tick 'Attempt to remove the driver for this device'. Reboot so Windows reinstalls a fresh copy, which strips corrupted registry keys tied to the old radio configuration.
Check Windows Update optional driver updates
In Settings, go to Windows Update, then Advanced options, then Optional updates, and expand Driver updates. If a newer wireless build is listed for your adapter, install it and reboot, then re-test roaming and link rate.
Error codes linked to this hardware
This device cannot start (Code 10)
A generic error indicating that the device driver failed to load or initialize properly, often due to power state issues or corrupted driver files.
This device is disabled (Code 22)
Windows can see the hardware, but the device is switched off in Device Manager by a user, an application, or a power-management action.
Helpful guides
Should You Use Driver Updater Software?
Driver updater tools promise one-click fixes but add risk. Here's what they really do, when they cause problems, and the safe way to check drivers yourself.
DCH vs Legacy Drivers in Windows 10/11
DCH drivers split hardware support from control-panel apps in Windows 10/11. Why the change happened and how to tell which type you have.
How to identify unknown devices with hardware IDs
A practical walkthrough for naming every mystery entry in Device Manager using hardware IDs, driver details, and Windows' built-in tools.
Frequently asked questions
Why does my wireless adapter throw Code 43 only after the laptop wakes from sleep?
Code 43 after resume usually means the radio failed its power-state re-initialisation, either because the driver mishandled the D0 to D3 transition or because a firmware calibration blob did not reload. Toggling Disable then Enable in Device Manager forces a clean re-init, and a driver build that matches your operating system fixes the underlying wake logic.
Why is my Wi-Fi 6 card connecting at 802.11n speeds instead of the full 1200 Mbps?
A link pinned to 802.11n rates almost always means channel bonding is disabled or the driver dropped the adapter to a legacy mode. Check that 160MHz or 80MHz bonding is enabled on the Advanced tab, confirm the router advertises a wide channel, and reinstall a current build if the wide-channel option is greyed out.
Why can't my wireless network interface card see any 5GHz or 6GHz networks?
Missing high-band SSIDs point to a regulatory-region mismatch or a driver that never enabled the band. Set the correct country in Windows and on the router, verify the adapter is a dual-band or tri-band part, and install the model-specific driver, since some Broadcom and Realtek radios need the OEM build to unlock 5GHz.