My internet plan promises speeds up to 1000 Mbps. My laptop, sitting a few feet from the router, was pulling in a consistent 330 Mbps on Wi-Fi, about a third of what I was paying for. I’d already ruled out the obvious suspects: the router was fine, the modem was fine, other devices on the network tested faster.

So I went digging through Device Manager’s advanced adapter settings (and the internet) to find four changes I could make that basically doubled what I was getting. Here’s what I changed, and how the speeds differed per step.

How speed testing works

There are quite a few variables

Before touching anything, I ran a baseline: three back-to-back Fast.com tests, same spot in the house, background apps closed. That gave me 340, 330, and 320 Mbps, an average of 330. Then I changed one setting at a time and re-tested after each one.

Speed test tools don’t just download a file and clock it. A single connection ramps up its transfer rate gradually and can’t always fill a fast pipe by itself, so tools like Fast.com and Speedtest.net open multiple parallel connections and average across them.

Ookla’s Speedtest, for instance, adapts its connection count in real time and even discards the slowest 30% and fastest 10% of its samples before calculating a final number, according to a CAIDA analysis of the platform. Fast.com works on the same principle but routes through Netflix’s Open Connect CDN instead of dedicated speed-test servers, which is great for predicting real streaming performance but noisier test to test, since the server it lands on varies in distance and load.

Local traffic matters, too. Bandwidth is shared, not reserved per device, so a background update or someone else streaming in another room eats into the same number your test is reporting, even on a stable connection.

Turn off Wi-Fi adapter power management

The setting doing most of the work

Windows laptops run a set of power-saving behaviors on the Wi-Fi radio to protect battery life, and on many systems these behaviors bleed into active use instead of staying limited to idle or sleep states. The adapter reduces its own radio activity and accepts higher latency in exchange for lower power draw, which can be a good trade-off when the lid is closed, but a bad one mid-download.

To fix it, just drop into Device Manager, expand Network adapters, right-click your Wi-Fi adapter, and open Properties. On the Power Management tab, uncheck “Allow the computer to turn off this device to save power.” You should see a result right away without the need for a restart.

Personally, I saw a pretty big jump, from 330 Mbps to 730 Mbps average (I ran each speed test three times). If you’re only going to make one change, this is the one to go for.

Set your adapter’s preferred band and wireless mode

Stop Windows from picking the wrong frequency

Even with a dual-band router, Windows doesn’t always put you on the faster band. It tends to prioritize signal strength over speed, which means it can settle you onto a strong 2.4GHz signal instead of a slightly weaker but much faster 5GHz one without asking. The real-world gap between the two bands is bigger than most people expect: 2.4GHz tops out around 100-150 Mbps in practice, despite a much higher theoretical ceiling, while 5GHz can realistically deliver up to 1 Gbps depending on your hardware and distance from the router.

In Device Manager, open your Wi-Fi adapter’s Properties, go to the Advanced tab, and look for “Preferred Band.” Set it to 5GHz (or 6GHz if your router and adapter both support Wi-Fi 6E). Some adapters also show a “Wireless Mode” property, though on mine this only listed legacy 802.11a/b/g options rather than anything referencing ac or ax; that’s a leftover compatibility field on a lot of drivers and not the thing actually capping your connection, so I left it alone.

Testing this alongside the power management step above, I saw higher numbers that were noticeably less consistent. Four runs came back at 920, 860, and 760, with one outlier at 520 Mbps, averaging 765 (closer to 847 if you set the low outlier aside). Still, it’s faster and I’m happy with the result.

Lower roaming aggressiveness

A setting that mostly matters if you have more than one access point

The Roaming aggressiveness setting controls how much your adapter looks for stronger connection points. Setting it to Low tells Windows to stay connected until the signal actually drops. Setting it to high means more scanning and more possibility of access point hopping.

This setting is also in the Wi-Fi adapter Properties in Device Manager’s Advanced tab. It might be called “Roaming aggressiveness” or maybe “Roaming sensitivity level,” but either way, set this to the Lowest setting. It’s mainly designed for places with multiple access points that share the same network ID, or a house with Wi-Fi extenders. If you have a single router setup like mine, you might not see much improvement.

I added a fourth setting tweak to see how it would work before I tested again.

Disable Windows’ network throttling index

An old Vista-era limit that’s still capping modern connections

Windows has come with a network throttling limit since the Vista era, and it was originally built to stop background network traffic from starving audio playback threads on much older, much slower hardware. The limit is controlled by a registry value called NetworkThrottlingIndex, and it caps non-multimedia network traffic at roughly 10,000 packets per second by default, which works out to about 120 Mbps on a modern connection.

It’s an easy fix through Terminal, and probably the safest route to it, as well. Open Terminal or PowerShell as an Administrator, and run the following command:

netsh interface tcp set global autotuninglevel=normalI did that, got the result, “Ok,” and then tested my speeds again. I got an average of 703 Mbps, which was a little lower than my previous tweak’s results, so figured it might be less important to make these changes.

However, after I’d applied all four settings, I kept testing for a bit. My first re-test hit 1.0 Gbps, which is my plan’s limit. Then I ran five more tests back to back, getting 730, 790, 780, 800, and 650 Mbps, averaging 750. Even if the 1.0 Gbps result was a spike, not the norm, it’s nice to see it on Wi-Fi. Real-world 802.11ac and 802.11ax throughput typically runs 40-70% of the negotiated link rate due to normal protocol overhead like contention, acknowledgment frames, and retries, according to Cisco’s own Wi-Fi 6 documentation.

The setting that actually mattered

Honestly, the first setting tweak I did, turning off Wi-Fi power management, made the most difference. 330 to 730 Mbps is quite a jump, a little more than double the original speed. The other three settings tweaks seemed to help a little, so are still worth doing due to the ease of use. I’m keeping it all as is, and now I’m off to see how to do the same to my Mac (which gets a higher Wi-Fi throughput rating already).