Wi-Fi adapter driver

What this driver does

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. Security handshakes run through the driver as well. When you join a protected network it drives the four-way WPA2 handshake or the Simultaneous Authentication of Equals exchange that WPA3 uses, passing pairwise and group keys to the hardware crypto engine so frames are encrypted before they leave the antenna. If the driver mishandles this key material you see repeated authentication prompts or a connection that reports limited connectivity. Modern adapters also lean on the driver for power and performance features. It controls U-APSD power save so the radio can nap between beacons to save battery, manages multiple-input multiple-output antenna streams, and applies transmit beamforming to focus signal energy toward the router. On 802.11ax hardware it coordinates OFDMA sub-carrier scheduling and target wake time, both of which need an in-date driver to behave correctly on your model.

Why updating 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. Performance regressions are common too. A driver mismatch frequently pins an 802.11ax card to legacy 802.11n rates, so a link that should show 1200 Mbps negotiates at 144 Mbps instead, and roaming between mesh nodes stutters because the driver mis-times its background scans. Refreshed builds also correct thermal throttling logic that otherwise slows the radio once the laptop palm-rest warms up. Finally, Windows feature updates change the NDIS contract. When Windows 11 revises how it schedules Wi-Fi power states or hands off to the WLAN AutoConfig service, a driver written against the older behaviour can bug-check the machine or leave the adapter stuck in a scanning loop. Matching the driver to the current operating system keeps that contract intact.

How it fits into the OS stack

Drivers operate in the background, serving as translators. Here is where the Wi-Fi adapter driver sits between your apps and the hardware.

Distribution comparison

Before you start

1Open Device Manager by right-clicking the Start button.

2Expand the relevant device category for your hardware.

3Right-click the specific component to open Properties.

4Check the current driver version in the Driver tab.

"Only install drivers from your operating system's update tool or the manufacturer's official support page."

Where this driver comes from

Drivers for Wi-Fi adapter driver typically reach your PC through one of three routes: shipped natively with the Windows operating system, delivered dynamically through system updates, or published directly by the hardware manufacturer for your specific model.

To ensure system stability, always allow your OS to handle baseline generic drivers. If you are experiencing performance issues or require advanced control panels, identify the exact model of your hardware and consult the device manufacturer's dedicated support resources.

Fixing installation problems

How to uninstall or rollback

1Click the Driver tab in the properties window.

2Select "Roll Back Driver" to revert to the previous version.

3If greyed out, use "Uninstall Device" instead.

How the wireless stack fits together

The Wi-Fi adapter driver sits in the middle of a layered stack. At the bottom is the radio silicon on your wireless network interface card, which handles the analogue work of modulating and demodulating 802.11 frames across the antennas. The driver programs that silicon over the PCIe bus, sets channel and power, and moves frames in and out of the hardware's transmit and receive rings. Directly above the driver is NDIS, the Network Driver Interface Specification, which presents the wireless card to Windows as if it were an Ethernet miniport. This abstraction is why the TCP/IP stack does not care whether packets arrive by cable or by radio. Above NDIS the WLAN AutoConfig service, Wlansvc, drives scanning, profile matching, and the association state machine, all fed by data the driver reports upward. When you click an SSID, Wlansvc asks the driver to scan, ranks the results, then instructs the driver to associate and run the security handshake. Once keys are installed in the hardware crypto engine, encrypted frames flow and DHCP obtains an address. Understanding this chain makes troubleshooting logical: a Code 43 is a driver-and-hardware problem, whereas 'No internet, secured' is a layer above the working radio link.

Bands, channels, and channel bonding explained

Wi-Fi operates in the 2.4GHz, 5GHz, and, on Wi-Fi 6E hardware, 6GHz bands, and the driver decides which the radio may use. The 2.4GHz band reaches further and passes through walls better but is crowded and offers only three non-overlapping 20MHz channels. The 5GHz band is faster and cleaner, and 6GHz is cleaner still, though its shorter range demands a nearer access point. Channel bonding is how modern Wi-Fi reaches high throughput. The driver combines adjacent 20MHz channels into 40MHz, 80MHz, or 160MHz blocks, and each doubling roughly doubles the peak rate. A 160MHz bond on an 802.11ax card is what makes 1200 Mbps and beyond possible, but it needs a lot of clean spectrum, which is exactly what a busy 5GHz environment lacks. Some 5GHz channels are shared with weather and military radar, so the driver must run Dynamic Frequency Selection. If it detects a radar pattern it must vacate the channel within seconds, which is why a 160MHz link on a DFS channel can hiccup unpredictably. If your throughput is inconsistent, narrowing the channel width in the driver's advanced properties often trades a little peak speed for far steadier performance.

Security handshakes and why the driver matters

Every protected join begins with a handshake the driver executes. On WPA2 this is the four-way handshake that derives the pairwise transient key from the pre-shared key and two random nonces, then installs it in hardware so frames are encrypted with AES-CCMP. If the driver reinstalls a key at the wrong moment, the KRACK attack could reset the encryption counter, which is why the fix arrived as a driver and supplicant update rather than new hardware. WPA3 replaces the four-way handshake with Simultaneous Authentication of Equals, a password-authenticated exchange that resists offline guessing even on weak passphrases. It also adds forward secrecy, so capturing today's traffic does not decrypt it later even if the password leaks. Drivers that predate WPA3, or that implement it incompletely, fail SAE and fall back or reject the network outright. Enterprise networks add WPA2/WPA3-Enterprise with 802.1X, where the driver relays EAP frames to a RADIUS server via the supplicant. Certificate handling and the exact EAP method live above the driver, but the radio must carry those frames reliably, so a flaky driver shows up as authentication that times out rather than fails cleanly. Keeping the driver current is the single most effective way to keep these handshakes healthy.

Where this driver comes from

A Wi-Fi adapter driver reaches your PC by one of three routes, and knowing which you are running makes troubleshooting far clearer. The first route is the driver shipped with Windows itself. Microsoft bundles inbox class drivers for common radios so a fresh install has working, if basic, wireless out of the box. These inbox builds are conservative: they connect reliably but often omit the vendor control panel and lag behind on new bands. The second route is delivery through system updates. Windows Update ships signed wireless drivers as part of quality updates and through the Optional updates, Driver updates list. These have passed Microsoft's hardware certification, so they are safe to trust, and they are how most laptops quietly stay current without anyone visiting a website. The trade-off is that they arrive later than the newest fixes and are sometimes the generic build rather than the fully featured OEM one. The third route is the driver published by the hardware maker for a specific model. Your laptop's manufacturer tunes a wireless build to that machine's antenna layout, thermal limits, and regulatory tables, and posts it on the support page for that exact model. This is the build to prefer when a concrete symptom points at the radio, because a generic driver may hide a band or misjudge power. All three routes deliver a legitimate driver; the difference is how current, how specific, and how fully featured each one is.

Diagnosing throughput and stability problems

When Wi-Fi misbehaves, separate radio-link problems from problems above the link. Start with the negotiated link rate: right-click the network in Settings or run a status query and read the receive and transmit rates. A rate stuck near 144 Mbps on an 802.11ax card means the driver dropped to legacy mode or bonding is off, which is a driver or channel-width issue rather than a router fault. Next, look at where the connection fails. If the adapter never appears, or shows Code 10 or Code 43, the problem is the driver-hardware boundary and the fix is a clean reinstall or a build that matches your Windows version. If it associates but shows 'No internet, secured', the radio link is fine and the fault is DHCP or the TCP/IP stack above it, addressed by resetting Winsock and IP. For intermittent drops, watch for a pattern. Drops that track roaming between access points point at roaming aggressiveness and fast-roaming settings. Drops that appear only under sustained load and warmth point at thermal throttling. Drops confined to one band suggest a channel-width or DFS-radar issue on 5GHz. Matching the symptom to the layer, then changing one setting at a time, turns a vague 'Wi-Fi is bad' complaint into a specific, fixable cause.

Frequently asked questions