Slow Ethernet on Windows 11 — connected via cable but getting speeds far below what the connection should deliver, or noticeably slower than other devices on the same network — is a Windows-side problem in most cases. Ethernet itself doesn’t introduce the variables that Wi-Fi does; when speeds are consistently low only on Windows, the adapter settings are usually responsible. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Run the test that matters: connect another device directly to the router via Ethernet (another laptop, a desktop with Ethernet, or even a phone with a USB-to-Ethernet adapter) and run speedtest.net. If that device gets expected speeds but Windows 11 doesn’t: Windows or the adapter is the bottleneck. If both are slow: the issue is upstream (the cable, router, or ISP).
Start with adapter advanced settings — the fastest fix
Windows 11’s default NIC settings aren’t optimised for throughput. Several settings actively limit Ethernet speed in the name of power saving. Device Manager → Network Adapters → right-click your Ethernet adapter → Properties → Advanced tab:
- Speed and Duplex: confirm “Auto Negotiation” — if it’s set to a fixed lower speed (100 Mbps Full Duplex on a Gigabit connection), you’re capped there. Switch to Auto Negotiation and let the adapter and router negotiate the best speed
- Energy Efficient Ethernet: Disabled — EEE reduces power by throttling the connection during low-traffic periods; it can affect throughput even during active transfers
- Green Ethernet: Disabled — similar to EEE; reduces power at the cost of stability and sometimes speed
- Receive Buffers: increase to maximum available (256, 512, or 1024) — larger buffers absorb traffic bursts without dropping packets
- Transmit Buffers: increase to maximum similarly
- Large Send Offload v2 (IPv4 and IPv6): Enabled — offloads packet segmentation to the NIC hardware, reducing CPU bottleneck during large transfers
After changing these settings: reconnect the Ethernet cable (or disable and re-enable the adapter in Device Manager) → run a speed test. The combination of enabling buffers and disabling power-saving features often increases throughput by 20-40% on connections where these were limiting.
Driver quality matters significantly
Windows Update installs generic Intel, Realtek, or Broadcom drivers that work functionally but miss performance optimisations in manufacturer-specific drivers. If the Ethernet adapter driver is a generic Windows driver:
- For desktop motherboards: go to the motherboard manufacturer’s support page (ASUS, MSI, Gigabyte, ASRock) and download the specific LAN driver for your motherboard model and chipset
- For laptops: the laptop manufacturer’s support page has the correct driver for the built-in Ethernet controller
- For add-in Ethernet cards: the card manufacturer’s website (Intel, Realtek, Aquantia) for the specific chip
Manufacturer-specific drivers include the full register tuning for the specific NIC chip, which generic drivers lack. The difference is measurable — particularly noticeable on Gigabit and multi-Gigabit connections where throughput should be close to the theoretical maximum.
TCP/IP stack and auto-tuning
Windows auto-tuning dynamically adjusts the TCP receive window size based on available bandwidth. In some network configurations — corporate networks with packet inspection, routers with aggressive QoS — auto-tuning causes worse performance than a fixed window size. Test:
netsh int tcp show globalIf “Receive Window Auto-Tuning Level” shows “disabled”: run:
netsh int tcp set global autotuninglevel=normalIf it’s already normal and speeds are low: try setting it to experimental:
netsh int tcp set global autotuninglevel=experimentalAlso check Chimney Offload: netsh int tcp show global → “Chimney Offload State” should be Enabled for modern NICs. Enable if disabled: netsh int tcp set global chimney=enabled.
Duplex mismatch
A duplex mismatch — where one end of the connection is set to full duplex and the other to half duplex — causes severe performance degradation (50-80% lower throughput) even though the connection appears functional. The connection works; it just performs at a fraction of its capacity.
Signs: transfer speed is consistently about 50% of expected, or performance is highly variable with many retransmissions visible in Task Manager’s Network tab. Fix: ensure both the Windows adapter (Device Manager → Advanced → Speed and Duplex) and the router/switch port are both set to Auto Negotiation. Forcing a specific speed on one end without matching the other creates the mismatch.
Cable quality
Not all Ethernet cables are equal. For Gigabit connections (1000 Mbps): Cat5e minimum is required. Cat5 (without the “e”) supports Gigabit in theory but often fails to sustain it on longer runs. For 2.5G or 10G connections: Cat6 or Cat6a is recommended.
Cable length also matters: Gigabit Ethernet is rated for 100 metres. Beyond that, speeds drop. Cables stored in walls that run near power cables (including mains power in conduit) suffer interference that reduces throughput. If an in-wall Ethernet run is consistently slower than expected: the cable run may have interference issues or exceed the maximum length.
Background processes consuming bandwidth
Task Manager → Performance → Ethernet → the Send and Receive graphs. If bandwidth is consistently non-zero even when you’re not actively downloading: background applications are consuming bandwidth. Task Manager → Processes → Network column → sort descending. Common background consumers: Windows Update, OneDrive, game launchers, antivirus cloud scanning.
For a speed test to reflect true available capacity: close or pause these applications before testing. A speed test running while OneDrive uploads 5 GB of files shows the remaining bandwidth, not the total capacity.
Our guide on general network performance covers the TCP/IP tuning and background bandwidth management that applies to both Ethernet and Wi-Fi. For the NIC hardware specifications and multi-Gigabit networking, our network packet loss guide covers the interrupt and buffer settings in more detail. Microsoft’s Ethernet performance documentation covers the Windows performance counters for detailed per-interface throughput measurement and the PowerShell network adapter statistics commands.
Interrupt moderation and CPU processing
The NIC’s Interrupt Moderation Rate (IMR) setting controls how often the network card interrupts the CPU to process received packets. Higher moderation = fewer interruptions but higher latency. Lower moderation = more CPU overhead but more responsive handling.
Device Manager → Ethernet adapter → Advanced → “Interrupt Moderation Rate” → try “Low” instead of the default “Adaptive” or “High.” For high-throughput scenarios (large file transfers, NAS access): medium to high moderation provides better throughput at the cost of slightly higher latency. For low-latency scenarios (gaming, video calls): low or off provides more responsive processing.
Wake-on-LAN and link state
Network adapters configured for Wake-on-LAN maintain a low-power connection even when the system is sleep. Some adapters in this state fail to re-negotiate full Gigabit speed when the system wakes, instead staying at a lower speed. Device Manager → Ethernet adapter → Advanced → disable “Wake on Magic Packet” and “Wake on Pattern Match” if WoL isn’t needed → restart and reconnect → run speed test. The adapter re-negotiates from scratch rather than resuming a potentially slow sleep connection.
VPN and Ethernet throughput
VPN connections route all traffic through an encrypted tunnel, adding overhead regardless of whether the connection is Ethernet or Wi-Fi. If speeds are slow only when the VPN is connected: VPN encryption overhead is the cause. Options: use WireGuard (lower overhead than OpenVPN), configure split tunneling to only route work traffic through VPN while high-bandwidth transfers go direct, or accept the speed reduction as the cost of VPN security.
ISP provisioning and modem cap
Some ISPs provision connections below the advertised maximum, or the cable modem caps the maximum achievable speed. Even a pristine Ethernet connection from Windows to a modem can’t exceed what the modem is authorised to deliver. Run a speed test: if it consistently shows 90% or more of the advertised speed, the connection is performing correctly. If it consistently shows 50% or less despite everything being correctly configured: contact the ISP. Request a modem provisioning check and a line quality test from their side.
Multi-Gigabit connections (2.5G, 5G, 10G)
If using a multi-Gigabit NIC: Windows 11 supports these natively, but achieving full speed requires matching hardware throughout the chain: a multi-Gigabit NIC, a multi-Gigabit port on the router or switch, and a Cat6 or Cat6a cable. If any component in the chain is standard Gigabit: speeds cap at Gigabit (approximately 940 Mbps real-world). Device Manager shows the current negotiated speed — check the speed displayed for the NIC after connecting.
For 2.5G NICs achieving only 1G speeds: verify the router or switch port also supports 2.5G. Most consumer routers still have 1G WAN and LAN ports even in 2025, making a 2.5G NIC bottleneck at the router regardless of the NIC capability.
Real-world throughput vs rated speed
Understanding what “Gigabit Ethernet” actually delivers helps calibrate expectations. The theoretical maximum is 1000 Mbps (125 MB/s). Real-world throughput accounting for TCP/IP overhead, protocol headers, and CPU processing:
- File transfer between two Gigabit-connected Windows machines: typically 80-115 MB/s
- Internet downloads over Gigabit ISP connection: typically 100-130 MB/s (actual bytes per second)
- speedtest.net reading: shows Mbps (megabits). Divide by 8 to get MB/s for comparison with File Explorer copy speeds
If speeds are within 80-90% of these figures: the Ethernet connection is performing normally. Only speeds below 70% of expected warrant investigation.
Router and switch port capacity
The router port the Ethernet cable connects to has its own rated speed. If it’s an older router with 100 Mbps LAN ports (Fast Ethernet rather than Gigabit): the connection is capped at approximately 94 Mbps download regardless of what the NIC or ISP can do. Check the router’s spec sheet for “LAN speed” — it should show “10/100/1000 Mbps” for Gigabit. “10/100 Mbps” only means Fast Ethernet (100 Mbps max).
For homes where the main router has Gigabit ports but an older switch was added to expand port count: check whether the switch is Gigabit or Fast Ethernet. Devices connected through a Fast Ethernet switch are capped at 100 Mbps even if their NIC and the router both support Gigabit.
| Speed achieved | Likely bottleneck | Where to look |
| ~90-100 Mbps consistently | Fast Ethernet cap somewhere in chain | Check router/switch port speed |
| ~50% of expected speed | Duplex mismatch | Adapter advanced settings → Speed and Duplex |
| Varies widely | Auto-tuning or power management | Disable EEE; set buffers to max |
| Below 70%, stable | Driver, cable, or ISP provisioning | Reinstall driver; test different cable; contact ISP |
| Full speed then slows | Thermal throttling or QoS | Check router QoS; monitor NIC temperature |
Ethernet troubleshooting on Windows 11 is methodical: confirm the issue is Windows-specific (compare speeds with another device), check adapter advanced settings (power management, buffers, duplex), update the driver from the manufacturer’s page, then investigate upstream hardware. The adapter settings changes alone — particularly disabling Energy Efficient Ethernet and setting buffers to maximum — resolve most Windows-side Ethernet performance issues in under 5 minutes.
A final practical note: if the Windows machine consistently achieves 940 Mbps on a Gigabit connection (close to the theoretical 1000 Mbps), but a competing benchmark claims it should be faster: the connection is working at its maximum. Ethernet at Gigabit is very close to saturating the link — there’s no “further optimisation” once you’re within 6% of the line rate. Focus on investigating bottlenecks at the application level (does the download server send fast enough? is the SSD write speed keeping up with the download?) rather than the networking layer.
Antivirus HTTPS inspection overhead on downloads
Security suites that decrypt and re-encrypt HTTPS traffic (Kaspersky, ESET, Bitdefender with SSL scanning) add processing time to every HTTPS download. On fast Ethernet connections where download speeds should be several hundred Mbps: the antivirus scanning becomes a real bottleneck — the CPU can’t decrypt, scan, and re-encrypt fast enough to keep up with the network. The result: a Gigabit Ethernet connection that only delivers 100-200 Mbps on HTTPS downloads.
Test: temporarily disable HTTPS inspection in the antivirus → run a speed test (which uses HTTPS) → compare. If speeds improve dramatically: the antivirus HTTPS scanning is the bottleneck. Whitelisting known-trusted domains (Microsoft, Google, major CDNs) in the antivirus HTTPS inspection exclusion list preserves scanning of higher-risk traffic while removing the bottleneck from trusted sources.
Windows Network Reset
As a last resort when individual settings changes haven’t resolved persistent slow Ethernet: Settings → Network and internet → Advanced network settings → Network reset → Reset now. This reinstalls all network adapters and resets all networking components to defaults. It requires reconfiguring any custom network settings, VPN clients, and static IPs afterward — but it creates a completely clean networking stack that eliminates accumulated misconfiguration. See also How to Fix Ethernet Not Working on Windows 11 for a related case.
After the reset: reinstall the Ethernet driver from the manufacturer’s page (not Windows Update), reapply the advanced adapter settings (disable EEE, set buffers), and test. This combination produces the cleanest possible Ethernet configuration and provides the most reliable benchmark of what the hardware can actually deliver. You might also run into Ethernet Slow on Windows 11.
