After unboxing and neatly connecting my new premium Cat6a cable, I expected the internet speed to be blisteringly fast. However, I got sluggish downloads. I had ping spikes at the times when I was hoping for stability.
What I realized was that on modern Windows 11 builds, premium hardware isn’t the only determining factor for maximum throughput. Windows is designed to prioritize green energy initiatives, and these settings, buried deep within Device Manager, can affect network performance. In trying to save microwatts of power, my system was throttling my connection. Once I fixed it, my Ethernet speed was predictable and as fast as I expected.
The cable wasn’t the problem.
Windows had already decided how to handle my connection
Afam Onyimadu / MUO
Ethernet connection problems are typically blamed on cables, the ISP, or the router. But as soon as I had ruled out these three, I started digging through Device Manager, where the first answer was hiding.
By default, Windows had enabled Energy Efficient Ethernet. This feature is built on the 802.3az standard and makes it possible for the network adapter’s physical layer to enter a low-power idle state during traffic dips. In theory, this idea makes sense. The adapter can rest when it’s not needed as much and wake up when demand surges. For a laptop trying to conserve battery life, it’s handy, but it makes less sense on a desktop connected to power. Here, saving milliwatts isn’t essential.
However, power saving isn’t the real issue, but rather the inconsistency it introduces. Connections don’t drop, and speed tests typically still show good numbers, but traffic becomes less predictable. Intel has documented poor EEE implementation on some of its chipsets, and this unpredictability is worse on such devices.
On a desktop, you can disable it without losing anything meaningful. Here are the very steps I took:
- Right-click the Start menu and select Device Manager.
- Expand Network adapters.
- Right-click your Ethernet adapter and select Properties.
- Navigate to the Advanced tab, then locate the Energy Efficient Ethernet (or EEE) option, click it, and change the value of the dropdown on the right to Disabled.
After disabling it, things improved, but I started wondering what else could be wrong if Windows can make this call without me knowing.
Related
The USB trick that bypasses your smart TV’s 100Mbps Ethernet limit
A tiny hardware limitation is slowing your TV down, but it is easy to get around.
Speed tests lied to me
Latency was the real story
Afam Onyimadu / MUO
Running an internet speed test did not reveal much, as the numbers looked fine. But the real problem was that I was looking for a problem that speed tests are not designed to spot.
There is a feature called Interrupt Moderation. It allows your network adapter to intentionally delay relaying information about incoming packets to the CPU. It groups the packets into batches before it passes them off. The ultimate goal is efficiency, since with fewer CPU interrupts, you get lower overhead, which has a positive effect on raw throughput if the system is heavily loaded. This default is an advantage when there are bulk transfers, but it’s counterproductive for real-time gaming, voice calls, or remote desktop sessions.
Here, it didn’t show a lower throughput number but introduced noticeable latency/jitter. In gaming sessions, it felt like inputs were arriving slightly late, and it felt like remote desktop sessions were thinking before responding. While none of these were dramatic, they were present.
With Interrupt Moderation disabled, the CPU handles network interruptions at a faster rate, and the cost of disabling it is negligible on modern hardware.
The exact name of this feature varies by manufacturer; Intel: “Interrupt Moderation Rate”; Realtek: a simple enable/disable; Broadcom: settings like “Low/Medium/High.”
I set it to Disabled or Low for latency-sensitive work, and here are the exact steps:
- Right-click the Start menu and select Device Manager.
- Expand Network adapters.
- Right-click your Ethernet adapter and select Properties.
- Navigate to the Advanced tab, then locate Interrupt Moderation, and change the rate or disable it.
My network was solving problems I didn’t have
There was no congestion to control
Afam Onyimadu / MUO
A pattern had clearly formed: several features are genuinely designed to fix a problem that I did not have. A good example is Flow Control.
Flow Control prevents packet loss during congestion by sending pause frames when the receive buffer nears capacity. In managed enterprise networks with compatible switches, that’s useful, but on mixed home networks, it can pause an entire link and cause inconsistent transfers.
While it did not cause a hard ceiling on speed, I experienced inconsistency in sustained transfers, especially while copying to my NAS. It smoothed out after I disabled Flow Control.
Here are the exact steps I followed:
It’s safe to leave Flow Control if you are on a managed office network.
- Right-click the Start menu and select Device Manager.
- Expand Network adapters.
- Right-click your Ethernet adapter and select Properties.
- Navigate to the Advanced tab, then locate Flow Control, and disable it.
With each change I made, it was more obvious that Windows is configured for the kind of network environment that I don’t use.
The problem wasn’t only in the Advanced tab
Windows had a second set of controls
I was not finished yet. The Power Management tab was somewhere I also had to look into. The setting called Allow the computer to turn off this device to save power was enabled. It determines how the adapter behaves during sleep and resume cycles. Its default configuration makes the adapter enter a managed low-power state when the computer sleeps and brings it back when the system wakes.
This is a transition you don’t notice as long as the driver handles it cleanly. But very often the driver doesn’t, and it results in sluggish reconnection. You may even experience brief dropouts on resume.
There was another layer of power-related entries. Your adapter may present this as “Power Saving Mode,” “Reduce Speed on Power Down,” or “Gigabit Lite.” This one can go beyond wake, affecting active link behavior. I disabled it as well. When disabled, Windows doesn’t put the network card to sleep or throttle its hardware speed.
Finally, predictable Ethernet speed
The goal all along was to have a predictable Ethernet speed, and that’s exactly what I got with these four settings updated. While each of them is a reasonable default, I wasn’t operating in the network environment for which they were created. When I’m on Ethernet, these settings are among the first I change.
