Network drivers, adapters, and how your PC reaches the internet

What a network driver does

A network driver is the software that lets your computer's network adapter — the Wi-Fi radio or the Ethernet port — communicate with Windows. On the receive side it hands incoming data up to the operating system's networking stack; on the transmit side it takes outgoing data and instructs the hardware to send it.

Wireless drivers do extra work: they manage connecting to access points, negotiating security, and adapting the data rate as signal quality changes. That is why a wireless connection can feel fast in one room and slow in another even though nothing about the driver has changed.

The networking stack, one layer at a time

It helps to picture networking as a stack of layers, each depending on the one below. At the bottom is the physical link — the cable or the radio signal. Above that sits the driver, then an IP address that identifies your device on the network, and finally services like DNS that make the internet usable by name.

Almost every connection problem lives in exactly one of these layers. A dead cable is physical; a missing adapter is the driver; 'no internet' is usually IP or DNS. Diagnosing which layer is involved is far more productive than changing everything at once.

• Physical: the cable or wireless signal itself.
• Driver: software that lets Windows use the adapter.
• IP address: your device's identity on the local network.
• DNS: turns website names into addresses.

Why 'Connected, no internet' happens

This message means your device has a working local connection to the router but cannot reach the broader internet. The link layer is fine; something above it is not. Common culprits are an IP address that was not assigned correctly or a DNS service that cannot translate website names into addresses.

Because these are separate layers, the fix is usually specific: renewing the IP address, checking DNS, or looking at the router — not reinstalling the adapter driver. Knowing which layer is involved saves a lot of guesswork.

Wired vs wireless

Wired Ethernet connections are generally more stable because they are not affected by distance, walls, or interference. Wireless connections trade some of that stability for convenience, and the wireless driver is constantly balancing speed against reliability.

When troubleshooting, temporarily using a wired connection is a useful way to tell whether an issue is with the wireless link specifically or with the network as a whole. If wired works and wireless doesn't, the problem is in the wireless layer, not the internet connection itself.

What affects real-world speed

The speed you actually experience is rarely the number on your plan. Distance from the router, walls and interference, the Wi-Fi band you connect to, and how many devices share the network all pull real throughput down. The wireless driver adapts continuously to keep the link stable, sometimes trading speed for reliability.

This is why moving closer to the router, or using a less crowded band, can noticeably change performance without anything being 'fixed'. Understanding these factors sets realistic expectations and points to simple, physical improvements.

After a reinstall or reset

A fresh Windows installation sometimes leaves a network adapter on a generic driver, or without a working driver at all, until the correct one is provided. This can feel like a chicken-and-egg problem, since downloading a driver usually needs a connection in the first place.

In these situations a wired connection, or a driver obtained on another device, bridges the gap. Recognising that the adapter is present but simply lacks its software explains why the hardware appears in the system yet cannot connect.