Ethernet/LAN drivers
Wired LAN adapter drivers for stable gigabit connections.
You might also need
Ethernet/LAN 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 ethernet/lan driver do?
An Ethernet LAN driver operates two closely linked blocks on your wired controller: the Media Access Control layer, which frames and schedules packets, and the physical-layer transceiver, or PHY, which turns those frames into the electrical signalling that travels down the twisted pairs of an RJ45 cable. The driver programs the MAC's descriptor rings for DMA and configures the PHY registers that decide how the link behaves.
Auto-negotiation is the first thing the driver arranges when a cable is plugged in. The PHY exchanges capability pages with the switch or router to agree the highest common speed, whether 10, 100, 1000, or on newer parts 2.5 gigabit, and the duplex mode. It also negotiates the MDI or MDI-X crossover so a straight cable works either way. If negotiation is forced to a fixed value on one end only, the result is a duplex mismatch that quietly wrecks throughput.
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.
Where this driver fits in Windows
The ethernet lan 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.
Observable ethernet/lan device states
These observations can involve hardware, firmware, operating-system services, applications, or a driver. They are descriptive rather than diagnostic.
- The wired link trains at 100 Mbps despite gigabit-capable cabling because auto-negotiation settled on the wrong speed
- Throughput is poor and the switch port logs collisions, a classic sign of a half-duplex mismatch on the link
- The connection flaps or drops briefly on a quiet network when Energy-Efficient Ethernet enters low-power idle
- Wake-on-LAN stopped waking the PC because the driver no longer arms the magic-packet pattern before sleep
- The Ethernet controller shows Code 10 and cannot start after a Windows feature update changed its power contract
- Large transfers stall under load as the controller drops out and only recovers after a disable and enable cycle