Skip to main content

Wi-Fi drivers

802.11 radio interfaces, NDIS networking, wireless security protocols, and link capabilities.

Connectivity Windows 11, Windows 10 Reviewed Aug 18, 2026
M.2 2230 Wi-Fi card held at an angle shown with two tiny antenna leads clipped on

You might also need

Wi-Fi drivers we cover

Quick facts

Hardware family
Connectivity
Works with
Windows 11, Windows 10
Last reviewed
Aug 18, 2026

Reference scope

DriverUpdateMax documents driver purpose, architecture, terminology, and compatibility. It does not distribute driver packages or provide repair, installation, or technical-support services.

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.

Read the full wi-fi adapter driver explainer

The main parts managed by a wi-fi adapter driver and how they connect

Compatibility is model-specific

A driver is associated with hardware identifiers, an operating-system driver model, and a processor architecture. Devices in the same category can expose different controllers, firmware interfaces, and optional feature layers, so a category name alone does not establish package compatibility.

Wi-Fi adapter driver working with the hardware and peripherals it supports

Where this driver fits in Windows

The wi-fi adapter driver sits between Windows, the applications you use, and the physical hardware. This layered view shows where the driver translates operating-system requests into device actions.

The wi-fi adapter driver between applications, Windows, and the physical device

Observable wi-fi device states

These observations can involve hardware, firmware, operating-system services, applications, or a driver. They are descriptive rather than diagnostic.

  • 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