Ethernet Stuck at 100 Mbps in Windows 11? Diagnose the Link

A Windows 11 PC can have a Gigabit Ethernet adapter yet show a 100 Mbps connection. Before changing Windows settings, establish whether the physical Ethernet link negotiated at 100 Mbps or whether the link is already at 1.0 Gbps and an internet speed test is slower. Those are different faults with different next steps.

Open Settings > Network & internet > Ethernet and inspect the connected adapter's properties, including its link speed where shown. Alternatively, open PowerShell and run `Get-NetAdapter | Select-Object Name, Status, LinkSpeed`. Identify the wired adapter rather than Wi-Fi, VPN, or a virtual adapter. Microsoft's Get-NetAdapter command exposes basic adapter properties; Intel's Ethernet support guidance explains that the displayed link speed is the negotiated rate between the adapter and its link partner.

If the wired link reads 100 Mbps, concentrate on the Ethernet endpoints, cable path, negotiation and adapter driver. If it already reads 1.0 Gbps or higher, skip the physical-link repair steps and investigate the separate throughput path. A 100 Mbps link does not prove that Windows or your ISP imposed an arbitrary download cap.

A Gigabit-capable motherboard cannot negotiate 1 Gbps with a switch, router, dock, USB Ethernet adapter or other link partner whose relevant port supports only 10/100 Mbps. Look up the exact Ethernet adapter model and the exact port on the device at the other end. Routers can mix LAN and WAN port capabilities, and some docks or inexpensive USB Ethernet adapters contain only 100 Mbps Ethernet hardware.

If the PC has a 2.5GbE adapter connected to a 1GbE port, a 1Gbps negotiated link can be entirely normal. The diagnostic problem here is a link unexpectedly falling to 100 Mbps despite both endpoints supporting 1000BASE-T or faster. A product name containing 'Gigabit' somewhere does not establish the speed of every physical port.

For common twisted-pair Ethernet, 100BASE-TX uses two cable pairs while 1000BASE-T uses all four. Cisco's switch specifications document this distinction. That is why a cable with a damaged conductor, bad termination, partially wired wall socket, loose plug or faulty coupler can sometimes maintain a 100 Mbps link even though the same path cannot reliably establish Gigabit. A 100 Mbps link is a clue, not a cable-fault diagnosis by itself.

Disconnect and firmly reseat both plugs. Then test a short, known-good, correctly terminated Cat5e or Cat6 patch cable directly between the PC and a verified Gigabit switch/router port. Proper Cat5e is sufficient for normal 1000BASE-T operation; upgrading to Cat6 is not a prerequisite for Gigabit. If the direct short cable restores 1 Gbps, add the wall run, patch panel, coupler, dock or other intermediate segment back one at a time until the failing section is identified.

Do not assume the cable is sound solely because it is printed 'Cat6' or because an internet connection works through it. Equally, do not replace an entire in-wall run before a known-good patch cable and alternate port have isolated the fault.

Move the same PC and known-good cable to another port whose manufacturer documentation confirms Gigabit capability. If possible, connect a second known-Gigabit PC to the original cable and port, then compare the negotiated rates. Intel explicitly recommends alternate cables, hosts and network connections when investigating an adapter limited to 100 Mbps.

If two different PCs are limited on the same cable or switch port, the shared physical path deserves attention first. If only one PC is limited across multiple verified Gigabit ports and known-good cables, the adapter, its configuration, driver or physical connector becomes more plausible. A single successful or failed test is not enough to declare the motherboard faulty.

In Device Manager, expand Network adapters, open the affected Ethernet controller, and inspect Properties > Advanced > Speed & Duplex if the driver exposes that option. For Intel Gigabit/Killer adapters, Intel's guidance is to leave Speed & Duplex on Auto Negotiation. A missing '1.0 Gbps Full Duplex' menu entry does not mean the adapter cannot establish Gigabit; Intel notes that some of its drivers do not expose a manual Gigabit choice.

Do not force a speed setting simply because a forum post recommends it. Both endpoints must agree on a supported mode, and forced settings can create a different connectivity problem or conceal a damaged cable. Record the original setting, make only a vendor-supported change when there is a specific reason, and revert a test that does not improve negotiation.

If the same adapter still negotiates at 100 Mbps across verified Gigabit equipment and multiple known-good cables, identify its exact model and current driver version. Check the PC or motherboard maker's supported Windows 11 Ethernet driver; for a separate retail NIC, use the adapter manufacturer's guidance. Intel recommends OEM drivers for OEM adapters and testing across networks or systems before escalating an adapter-specific fault.

A driver update or rollback is most informative when the problem started immediately after a specific update or when the manufacturer documents a relevant negotiation issue. Do not uninstall multiple network adapters, reset TCP/IP, change registry keys or flash BIOS firmware as the first response to a physical link-rate mismatch. Microsoft's network-reset guidance is a last-resort connection repair and warns that it removes network adapters and their settings, potentially affecting VPNs or virtual switches.

A negotiated 1 Gbps link is not a promise that an internet download will reach 1 Gbps. Online speed tests also depend on the ISP plan, router WAN path, server, concurrent traffic, VPN, software and measurement method. A file transfer to a NAS additionally depends on the destination's link and storage performance. If Windows shows 1.0 Gbps but downloads are near 90 Mbps, a Gigabit cable-pair fault is no longer the first explanation.

Compare a local wired transfer or another reputable test endpoint, check the router's WAN-port capability and ISP service, and verify that no intermediate device has a slower link. Avoid changing Ethernet duplex or disabling Windows TCP features to solve a problem that has not been shown to occur at the physical link.

Record the adapter model, Windows-reported link speed, NIC driver version, exact switch/router port model, cable and wall-jack path, and the outcome with a known-good direct patch cable and alternate port. Note whether the link is consistently 100 Mbps or intermittently renegotiates. If a second known-good host negotiates Gigabit on the same equipment while this PC repeatedly does not, provide that comparison to the NIC or PC manufacturer.

The goal is to find the first point in the wired path that changes the negotiated rate. Once that point is isolated, the remedy may be as simple as a cable, port or termination replacement; a driver or hardware repair is warranted only when the tests actually point there.