What the claim is
Shah's piece points at three settings: Energy Efficient Ethernet (EEE), "Green Ethernet," and "Power Saving Mode." It says all three are on by default and can drag down wired throughput. It also recommends clearing one Power Management checkbox and turning off two more advanced options, Interrupt Moderation and Flow Control.
The "unlock the speeds you paid for" framing goes further than the evidence does. Neither the article nor the documentation I could check gives a measured throughput loss. They show that these features can add small delays or odd behavior on some adapter, driver and switch combinations.
EEE: real, standardized, and sometimes a latency culprit
EEE is the best-documented of the three. Microsoft's driver documentation lists a standardized *EEE keyword, described as controlling IEEE 802.3az energy-efficient Ethernet. The documented default for that keyword is Enabled. That means a driver using the standard keyword can ship with EEE on. It doesn't mean every PC exposes the setting or has it on.
The idea is simple. During quiet periods the adapter's physical layer drops into a low-power idle state. When traffic resumes, it wakes. Intel's adapter guide, as summarized in the research notes, says both ends of the link must support and enable EEE. It also says the transition may add a small amount of latency.
Other outlets report that this wake-up can show up as jitter or brief pauses. How-To Geek says in some cases it can introduce inconsistent transfer speeds, higher latency, or brief pauses as the link moves between states. A MakeUseOf piece on Green Ethernet makes a useful point: it doesn't go unnoticed on every adapter/driver/router combination; on some pairings, it causes noticeable delays.
My read:
- EEE is a plausible suspect for latency spikes, micro-stutters, or odd pauses on a wired link.
- It is much less plausible as the cause of a steady speed shortfall. If a gigabit line tops out at 300 Mbps, look at the link speed, cable, router and ISP first.
"Green Ethernet" and "Power Saving Mode" are driver-specific labels
Shah describes Green Ethernet as a vendor-specific variant of EEE. That is broadly consistent with the public record. Wikipedia describes Green Ethernet as a superset of the 802.3az standard, and it can include things like more efficient circuitry. Another MakeUseOf guide notes that manufacturers sometimes use these terms for slightly different power-saving features.
So there is no single Windows control called Power Saving Mode that behaves the same everywhere. These are driver-exposed options. Your adapter might list one, three, or none. One Windows 11 optimization guide puts it plainly: the Advanced Properties exposed by Windows depend on the Ethernet controller, chipset, driver, firmware, PC manufacturer, and Windows build. If a label isn't there, don't go hunting for registry hacks or a "tuning" utility.
The Power Management checkbox: what it does
Shah suggests clearing "Allow the computer to turn off this device to save power." Microsoft's NDIS documentation gives useful detail here:
- For a NIC that supports power management, the option is selected by default, according to Microsoft's description of the Power Management tab. Clearing it makes NDIS treat the NIC like an old card for power management purposes.
- A separate option, "Allow the device to bring the computer out of standby," controls wake-on-LAN. It's cleared by default and is unavailable if the hardware can't support it.
- Windows writes any change to the registry, so it persists across restarts.
This matters for the "no downside" claim. The checkbox is tied to the adapter's low-power states as the system sleeps. It is not evidence that Windows routinely powers down an active link during normal use. Unchecking it is a reasonable test if your connection drops after idle periods or overnight. It could also change power use and wake behavior, so if you rely on wake-on-LAN or managed-device policies, test first.
Interrupt Moderation and Flow Control: tradeoffs, not cleanup
Shah's last two tips deserve the most caution.
Interrupt Moderation. Microsoft explains that the NIC hardware doesn't generate an interrupt immediately after it receives a packet but waits for more packets or a timeout. That is the CPU-saving batching Shah describes. It also makes the round-trip time for a given packet look longer. Microsoft's keyword documentation lists Interrupt Moderation as enabled by default. Turning it off may help latency-sensitive work such as competitive gaming or local-network testing. The cost is more CPU work under load, so it shouldn't be treated as a universal best setting.
Flow Control. Microsoft's keyword table lists different defaults: Rx & Tx Enabled for clients and disabled for servers. Pause frames can help during congestion, and they can misbehave with some switches. Microsoft's documentation also describes a case where a NIC pushing pause frames while a kernel debugger was attached could cause many switches to briefly take down the network for other machines. That is a niche debugging scenario, but it shows why flow control is not a harmless toggle. Leave it alone unless you have a reproducible problem, such as stuttering transfers that track congestion, or vendor guidance.
A safer troubleshooting procedure
- Right-click Start and open Device Manager.
- Expand Network adapters and double-click your wired Ethernet adapter. Don't pick the Wi-Fi adapter or a virtual one.
- Open the Advanced tab. Write down the current value of every setting you plan to change.
- Look for Energy Efficient Ethernet (or a Green Ethernet label, depending on the driver). Set it to Disabled, click OK, and test. Some guides recommend restarting the adapter or the PC afterward.
- If drops happen after idle periods, open the Power Management tab. Clear Allow the computer to turn off this device to save power, and consider whether you need wake-on-LAN first.
- If latency is still a problem, test Interrupt Moderation on its own. Treat it as an experiment, not a default.
- Change Flow Control only for a specific, reproducible reason.
- Change one setting at a time. If it makes no difference, put it back.
What success looks like: fewer latency spikes in ping tests or games, no link drops after idle, and steady transfers. If nothing changes, the settings weren't your problem. Revert them.
Check the basics before blaming power saving
Power-saving settings are a long way down the diagnosis list for a plain "slow Ethernet" complaint. Check these first:
- Does the adapter negotiate the speed you expect? A bad cable can drop a link to 100 Mbps.
- Is the router or switch port healthy? Try another port.
- Is your driver current? Another MakeUseOf guide lists the latest manufacturer driver as a fix for adapter-specific bugs.
- Is the slowdown local, or does it come from your ISP?
Bottom line
EEE and adapter power management are legitimate suspects for intermittent wired problems, especially latency spikes, short stalls, and disconnects after idle. Disabling EEE is a low-risk test, and the energy it saves on a desktop is tiny. The sweeping claims in the original piece, that these settings are always on, always throttle throughput, and carry no downside, aren't backed by the documentation. Treat them as a test list, not a fix-all.
For managed or enterprise PCs, check with your IT team first. Power policies and wake-on-LAN are often set on purpose.
References
- Plugging in an Ethernet cable won’t save you from Windows’ power-saving habits MakeUseOf · 2026-11-18T12:30:17+00:00
- Stop changing every Ethernet setting you see online, only these actually matter makeuseof.com
- Standardized INF Keywords for Power Management - Windows drivers | Microsoft Learn learn.microsoft.com