Fix the Cause, in Order, Instead of Guessing

High ping on Windows 11 is almost never fixed by a single magic setting. In practice it comes down to four things, in descending order of impact: what you are connected with (Wi-Fi or Ethernet), what else on your network is using bandwidth, whether Windows is putting your network adapter to sleep to save power, and whether your adapter driver is current. Everything past that — DNS, Game Mode, metered connections — is a small refinement, and the registry "optimizer" tweaks people still post about are mostly obsolete. This guide walks the diagnostic order that actually finds the problem.

Step 0: Get a Baseline Before You Change Anything

You cannot tell whether a fix worked without a number from before the fix. Take three measurements and write them down:

Latency to your own router. Open Command Prompt and run ping -n 50 192.168.1.1, substituting your router address if it differs (find it with ipconfig, listed as Default Gateway). On a wired connection this should be roughly 1ms with zero loss. Anything above 5ms, or any packet loss at all, means the problem is inside your home and nothing beyond your router matters yet.
Latency past your router. Run ping -n 50 1.1.1.1. Compare it against the router figure. The difference between the two is everything outside your house.
A browser measurement for before/after comparison. Run our ping and jitter test and note the average and the jitter. It measures warm HTTPS round-trip time to nearby cloud endpoints rather than ICMP packets to a game server, so treat it as a reliable proxy rather than an exact in-game figure — but because the method is identical every run, before/after comparisons are fair.

Record all three numbers now; you will re-run them after each change below.

Step 1: Wi-Fi or Ethernet

This is the highest-leverage check and it takes two minutes. Plug in an Ethernet cable, disable Wi-Fi, and repeat the router ping test. If the average drops or the jitter collapses, wireless was your problem and no Windows setting will fully fix it.

Wi-Fi does not usually add much to your average latency on a healthy 5 GHz or 6 GHz link. What it adds is variance: when a wireless frame is corrupted, the radio silently retransmits it and that packet lands far late. Games feel that as a missed hit, not as a higher ping number. Our Wi-Fi vs Ethernet comparison covers when modern wireless is good enough and when a cable or MoCA run is worth the effort.

Step 2: Find What Else Is Using Your Connection

A saturated link is the most common cause of ping that is fine most of the time and terrible for ten minutes at a stretch, and Windows 11 ships several services that will quietly consume your entire connection.

Open Task Manager, go to the Processes tab, and click the Network column to sort by network use; Resource Monitor's Network tab gives a more detailed per-process view. Then work through the usual suspects:

Culprit	Where to Change It	What to Set
Windows Update Delivery Optimization	Settings > Windows Update > Advanced options > Delivery Optimization	Turn off "Allow downloads from other PCs", and in Advanced options cap the upload and download bandwidth used for updates.
Windows Update itself	Settings > Windows Update	Pause updates for a week if a large cumulative update is downloading mid-session, then let it finish outside play hours.
Cloud sync (OneDrive, Dropbox, Google Drive)	Tray icon > Settings > Sync or Network	Pause syncing while gaming, or set an upload bandwidth limit permanently. Uploads hurt ping more than downloads.
Game launcher downloads (Steam, Epic, Battle.net, Xbox)	Launcher settings > Downloads	Set a download bandwidth limit and enable the option to pause downloads during gameplay where the launcher offers it.
Other devices on the network	Router admin page > connected devices	4K streams, console updates, and phone backups share the same upstream. Check them before blaming the PC.

If your ping is fine idle but jumps to hundreds of milliseconds the moment a download starts, the real problem is bufferbloat, not Windows. That is a router-side fix — see our bufferbloat explainer for the Smart Queue Management setup that solves it.

Step 3: Stop Windows From Powering Down Your Adapter

Power saving on network hardware is a real, measurable cause of latency spikes, especially on laptops and on Wi-Fi. There are two separate places to check.

Device Manager. Open Device Manager, expand Network adapters, right-click your adapter, choose Properties, then the Power Management tab. Uncheck "Allow the computer to turn off this device to save power". Do this for both your Ethernet and Wi-Fi adapters.
Power plan. In Settings > System > Power & battery, set Power mode to Best performance while plugged in. For the deeper wireless setting, open Control Panel > Power Options > Change plan settings > Change advanced power settings, expand Wireless Adapter Settings, and set Power Saving Mode to Maximum Performance.

Also check the adapter's Advanced tab in Device Manager for vendor-specific energy features — names vary, commonly Energy Efficient Ethernet or Green Ethernet. Disabling those on a desktop that is always plugged in is safe and occasionally removes a stubborn source of intermittent latency.

Step 4: Update the Network Adapter Driver Properly

Windows Update ships generic network drivers that are frequently a year or more behind. Buggy or stale Wi-Fi drivers in particular produce jitter and packet loss that look exactly like an ISP fault. Get the driver from the source, not from Windows Update or a driver-updater utility:

Desktop with onboard networking: your motherboard manufacturer's support page, for your exact board model.
Laptop: the laptop manufacturer's support page for your exact model, since OEM wireless firmware is often customized.
Add-in card or USB adapter: the chipset vendor's own driver (Intel, Realtek, MediaTek, Qualcomm).

Re-run your baseline pings afterwards. If a new driver makes things worse, the Roll Back Driver button on the Driver tab in Device Manager restores the previous version.

Step 5: DNS and the Metered Connection Setting

Two smaller settings that are worth getting right, with realistic expectations.

DNS does not change your in-game ping. It changes how long name lookups take — page loads, launcher logins, matchmaking handshakes — because once a game connection is established it talks to an IP address directly, with DNS out of the loop. It is still worth changing if your ISP resolver is slow: go to Settings > Network & internet, select your active connection, click Edit next to DNS server assignment, switch to Manual, and enter a public resolver. Our breakdown of DNS and ping covers what it does and does not affect.

Metered connection is a genuinely useful switch. Marking your network as metered in Settings > Network & internet > (your connection) tells Windows to hold back non-critical downloads, including most update and Store traffic. It is blunt, but on a limited connection it is one of the more effective single toggles available.

Step 6: Game Mode — What It Actually Does

Game Mode lives in Settings > Gaming > Game Mode and is on by default. It prioritizes CPU and GPU resources for the foreground game and holds back driver installs and restart notifications during play. It does not touch network traffic and it will not lower your ping. Leave it on for frame pacing, but expect nothing from it latency-wise.

The same applies to the Windows 11 graphics options for windowed games: they can reduce the delay between your input and the frame on screen, which feels like less lag, but they are unrelated to network round-trip time. Knowing the difference stops you chasing a network fix for a display problem.

The Myths: What Does Not Work in 2026

Claim	Reality
Registry "TCP optimizer" tweak packs	Windows has auto-tuned TCP receive windows and congestion control for well over a decade, and the defaults are sane. Bulk packs mostly change values that do nothing or hurt throughput, and they are painful to reverse.
Disabling Nagle's algorithm (TcpAckFrequency, TCPNoDelay)	Largely obsolete. Nagle batches small outbound TCP segments — but almost all real-time game traffic is UDP, which Nagle never touches, and games that do use TCP set the no-delay socket option themselves. The gain for modern titles is essentially nil.
Disabling TCP autotuning or Receive Side Scaling	Both exist to improve performance. Turning them off usually reduces throughput without improving latency.
Turning off adapter interrupt moderation	Shaves a fraction of a millisecond at the cost of higher CPU use. Unmeasurable in gameplay on a modern CPU.
A VPN "optimizes routing" for lower ping	Only in the narrow case where your ISP routes badly to a specific server. In most cases it adds a hop and adds latency.

To see your current TCP settings before anyone convinces you to change them, run netsh interface tcp show global in an elevated Command Prompt.

What NOT to Do: Ping Boosters and Optimizer Software

The category of software marketed as "ping boosters", "game accelerators", or "network optimizers" ranges from harmless to genuinely hostile. Treat it with the following rules:

Nothing installed on your PC can reduce the speed of light. The bulk of your ping is distance and routing. Local software cannot change either.
Tools that reroute your traffic are VPNs with a gaming skin. A few legitimately find a better path to one game server in one region. Most add a hop and raise your latency. A claimed universal improvement for every game is marketing.
Anything requiring kernel drivers or "system optimization" privileges is a real risk. You are granting deep system access to a small vendor for a marginal benefit.
Bundled registry "cleaners" cause more problems than they solve. They disable services Windows needs and leave no clean way back.
Measure before and after any trial with a neutral tool, and cancel if the numbers are unchanged. They usually are.

The Working Order, Summarised

Measure: ping your router, ping a public address, and record a browser latency and jitter reading.
Test wired vs wireless. If wired is dramatically steadier, solve the wireless problem or run a cable.
Kill background bandwidth: Delivery Optimization, cloud sync, launcher downloads, other devices.
Disable adapter power saving in Device Manager and set the power plan to best performance.
Install the current adapter driver from the hardware manufacturer, then re-measure.
Set a fast DNS resolver and mark the connection as metered if your upstream is limited.
Re-measure after each change, one change at a time. If nothing helps, the problem is outside your PC — work through our full guide to lowering ping to check the router and the route itself.

If ping is still high everywhere rather than in one game, the cause is your line or your ISP's routing, not Windows — and that investigation starts with a traceroute.