Packet Loss on Windows 11: Diagnose and Fix It

Packet loss on Windows 11 — stuttering in games, frozen video call images, or dropped packets in network diagnostics — isn’t just a network infrastructure problem. A significant portion of packet loss cases are caused by Windows-side settings, and many are fixable without touching the router. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.

First: confirm you actually have packet loss and where it’s happening. Open Command Prompt and run:

ping google.com -n 100

Look at the summary at the end. Anything above 1-2% lost packets over 100 pings is meaningful packet loss. Also run the same test to your router’s IP (usually 192.168.1.1):

ping 192.168.1.1 -n 100

If your router ping is clean (0% loss) but google.com shows loss: the packet loss is between your router and the internet. If your router ping also shows loss: the problem is between your Windows machine and the router — Wi-Fi signal, cable, or adapter settings.

Fix 1: Network adapter power management (most common cause on laptops)

Windows aggressively manages power on laptop network adapters, occasionally reducing transmission power to save battery. This intermittent power throttling causes exactly the “random packet drops” pattern that’s hard to explain otherwise.

Device Manager → Network Adapters → right-click your adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Then go to the Advanced tab and look for:

• Energy Efficient Ethernet → Disabled
• Power Save Mode or Power Saving Mode → Off or Maximum Performance
• Green Ethernet → Disabled

Apply these changes, reconnect if using Wi-Fi, and rerun the ping test.

Fix 2: Update the network adapter driver

Outdated NIC drivers often have bugs that cause packet drops under specific traffic conditions. Windows Update installs generic drivers that are more stable for general use but may miss model-specific optimisations that affect packet loss rates.

Download and install the latest driver for your network adapter from the laptop or motherboard manufacturer’s website — not from the NIC chip manufacturer (Intel, Realtek, Qualcomm) directly for laptops, as the laptop manufacturer customises the driver for their hardware.

Fix 3: Network adapter advanced settings

Several adapter settings directly affect packet loss. Device Manager → your network adapter → Properties → Advanced tab. Look for and adjust:

• Interrupt Moderation Rate: try “Low” or “Off” — higher moderation rates cause more variation in when packets are delivered to the CPU
• Receive Buffers / Transmit Buffers: increase to the maximum available value (512 or 1024) — small buffers drop packets during traffic bursts
• Speed and Duplex: confirm it’s set to “Auto Negotiation” — manual settings that don’t match the router/switch can cause ongoing packet loss from duplex mismatches
• Flow Control: try disabling this if it’s enabled, or enabling if disabled — Flow Control can cause artificial pauses that appear as packet loss

Fix 4: Reset the TCP/IP stack

Packet loss can result from corrupted TCP/IP configuration in Windows rather than hardware or driver issues. Reset the networking stack from an administrator Command Prompt:

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Restart after running these commands. Test for packet loss after the restart.

Fix 5: Wi-Fi-specific packet loss causes

Wi-Fi packet loss has different causes than Ethernet packet loss. For Wi-Fi:

• Signal strength: check with Task Manager → Performance → Wi-Fi → “Signal strength” — below 75% (-70 dBm) and packet loss increases significantly
• Channel congestion: too many networks on the same 2.4 GHz channel causes collisions and packet drops. Use a Wi-Fi analyser app to find a less crowded channel and set it manually in your router
• USB 3.0 interference: USB 3.0 ports emit 2.4 GHz interference that degrades Wi-Fi signal. Use a USB extension cable to move the wireless receiver away from USB 3.0 ports
• Roaming aggressiveness: if set too high, the adapter constantly scans for better access points, causing brief packet drops during scans. Device Manager → adapter → Advanced → Roaming Aggressiveness → set to Medium or Low

Fix 6: QoS settings and traffic prioritisation

Packet loss in specific applications while others work fine often indicates bandwidth saturation rather than true packet loss. When the connection is fully utilised, new packets get dropped. Windows QoS (Quality of Service) can prioritise traffic from specific applications.

Check router QoS settings first — the router manages traffic prioritisation more effectively than the Windows machine. Also check whether background applications (Windows Update, cloud backup, other streaming) are consuming bandwidth during the packet loss periods. Task Manager → Performance → Ethernet/Wi-Fi → look at the Send and Receive rates during the problem period.

Fix 7: Disable Large Send Offload

Large Send Offload (LSO) moves TCP packet segmentation to the network card hardware. While this improves throughput, it can cause packet loss in some network environments because some switches and routers don’t handle LSO-segmented packets correctly.

Device Manager → your adapter → Properties → Advanced → “Large Send Offload v2 (IPv4)” → Disabled. Do the same for IPv6 and any “Large Receive Offload” options. Test after disabling.

Note: disabling LSO slightly increases CPU usage for network operations. It’s a worthwhile trade if it eliminates the packet loss.

For the network performance improvements that go beyond packet loss prevention, our latency guide covers Nagle’s algorithm, TCP auto-tuning, and interrupt coalescing settings. For diagnosing whether packet loss is caused by hardware (cable, NIC) or software, our Ethernet disconnection guide covers the cable and hardware testing approach. Microsoft’s network diagnostic tools include the built-in pathping utility, which combines traceroute and ping to identify exactly which network hop is causing packet loss.

Using pathping for advanced packet loss diagnosis

Windows includes pathping, a utility that combines traceroute with packet loss statistics for every hop between you and a destination. Open Command Prompt and run:

pathping google.com

It runs for about 5 minutes (100 packets per hop), then shows a table. Read it like this:

• If packet loss only starts at hop 1 (your router): the problem is between your PC and router — Windows settings or local hardware
• If packet loss starts at hop 2 or 3 (ISP nodes): it’s an ISP infrastructure issue
• If packet loss only appears at the final hop (the destination server): the server itself is busy or restricting ICMP responses — this doesn’t necessarily affect actual traffic
• If loss accumulates from a specific intermediate hop: that router or link is the bottleneck

This information is particularly valuable when reporting packet loss to your ISP — specific hop data tells them exactly where to look rather than requiring them to investigate from scratch.

Hardware causes: cable and NIC

If Windows-side fixes don’t reduce packet loss:

• Ethernet cable: replace the cable, especially if it’s kinked, old, or over 50 metres. Cat5e or Cat6 cable is required for Gigabit connections — Cat5 (without the “e”) causes packet loss at Gigabit speeds
• NIC health: check the adapter’s error counters. Device Manager → adapter → Properties → check if there’s a “Statistics” or “Diagnostics” section, or use manufacturer diagnostic software
• Switch/router port: try a different port on your switch or router — individual ports can develop hardware faults that cause packet loss on that specific port

ISP-related packet loss patterns

Packet loss that occurs consistently during evening hours (6–10 PM) but not during the day is almost always congestion on your ISP’s network — shared cable infrastructure, overloaded backhaul, or peering point congestion. This is particularly common with cable ISPs in dense neighbourhoods.

To confirm: run a continuous ping throughout the day at different times:

ping google.com -t > ping_log.txt

Let it run for several hours, then examine the log for when packet loss occurs. If it correlates clearly with time of day, contact your ISP with the time-stamped evidence.

VPN and packet loss

VPN connections add overhead to every packet. On connections that are already near capacity, or on VPN servers that are overloaded, this overhead can push packets over the MTU limit and cause fragmentation or drops.

If packet loss occurs only when the VPN is connected: try a different VPN server location, switch to a lighter protocol (WireGuard has lower overhead than OpenVPN), or manually set the MTU lower in the VPN adapter’s advanced settings (Device Manager → the VPN adapter → Advanced → MTU size → try 1400 or 1350).

Checking for jitter alongside packet loss

Packet loss and jitter (variation in ping times) often go together. A connection with 2% packet loss but 200ms jitter spikes is worse for real-time applications than one with the same loss but consistent 20ms ping. In the ping output, look at “Maximum” vs “Minimum” response times — a large difference indicates high jitter.

PingPlotter (the free version does this) visualises packet loss and jitter over time in a graph, making it much easier to see patterns than reading raw ping output. Useful for identifying whether packet loss is random, periodic, or correlated with specific events.

Packet loss on wireless: monitoring signal quality

For Wi-Fi packet loss, signal quality metrics beyond just “signal strength” matter. Run this in Command Prompt to see more detail:

netsh wlan show interfaces

Look at “Signal” (should be above 80% for good performance), “Receive rate” and “Transmit rate” (the negotiated speeds), and “Radio type” (802.11ac/Wi-Fi 5 or 802.11ax/Wi-Fi 6 is preferable to older standards). If the transmit rate is much lower than expected for your router’s capability, signal quality — not just strength — is affecting the connection.

Quick diagnostic summary

Where packet loss occurs	Cause	Fix
Only on your PC (router ping is clean)	NIC driver, power management, or adapter settings	Disable green Ethernet; update driver; adjust buffer sizes
Router AND internet (everything loses packets)	Cable or router port hardware issue	Replace cable; try different switch port
From hop 2+ in pathping (ISP nodes)	ISP congestion or infrastructure issue	Report to ISP with pathping output
Only with VPN connected	VPN overhead or server overload	Switch server; lower MTU; try WireGuard
Only during peak hours	ISP shared infrastructure congestion	Report to ISP with time-stamped ping logs

Diagnosing exactly where packet loss originates — using the two ping tests at the start of this guide and pathping for more detail — saves significant time by immediately pointing to whether the fix is on the Windows machine, the local network hardware, or the ISP. Most Windows-side packet loss resolves with the power management and adapter settings fixes in the first three fixes above.

DPC latency and software-caused packet loss

High DPC (Deferred Procedure Call) latency — often caused by buggy device drivers — can cause Windows to miss network adapter interrupts, resulting in packet drops even when the hardware is perfectly fine. This is particularly common with certain audio and storage drivers.

Use LatencyMon (free from resplendence.com) to measure DPC latency while running a ping test during packet loss periods. If any driver shows high DPC counts, that driver is contributing to the packet drops. Common high-DPC drivers: older Realtek audio drivers, some USB 3.0 host controllers, and certain wireless adapters in power-saving mode. Updating the specific high-DPC driver often resolves packet loss that’s otherwise unexplained by hardware or ISP issues.

Gaming-specific packet loss vs general packet loss

Games often show packet loss statistics that don’t match what ping tests show. This is because games use UDP while ping uses ICMP, and some routers deprioritise or rate-limit UDP traffic differently from ICMP. A game showing 10% packet loss while your ping test shows 0% means the router or ISP is specifically affecting UDP game traffic.

Solutions for game-specific UDP packet loss: enable QoS on your router and configure it to prioritise gaming traffic, or check whether your router has a “Gaming Mode” that does this automatically. Also check whether the game’s servers are experiencing issues independently — game server status pages and social media are worth checking before assuming the problem is on your side.

Packet loss is one of the more diagnostic-intensive network problems because it requires identifying the exact point of failure in a chain that spans from your PC through the local network to your ISP and beyond. The ping and pathping tests at the start are not optional — they’re what converts “I have packet loss” into actionable information about which component to fix. Everything else in this guide flows from those two test results.

One more useful tool worth knowing: netstat -e in Command Prompt shows your network adapter’s error counters since the last boot. If “Errors” or “Discards” in the Received column are non-zero and increasing, the adapter is dropping packets at the hardware level — a strong indicator that the NIC settings (buffers, interrupt moderation) or the cable are the cause rather than the ISP or software configuration. You might also run into VPN Slow Internet.