Dropped frames in games, choppy video calls, and laggy downloads — all of these point to one root cause: packet loss. If you’re trying to figure out how to fix packet loss on Windows 11, you’re dealing with one of the most frustrating network problems that doesn’t show up on a basic speed test. Your bandwidth might look fine, but data is silently vanishing between your PC and the server.

The tricky part about packet loss is that it can originate from your Wi-Fi adapter, your router, your ISP’s infrastructure, or even a misconfigured Windows 11 setting. A standard “restart your router” suggestion rarely solves persistent cases. What you actually need is a structured approach — first diagnose where the loss is happening, then apply the right fix for that specific cause.

This guide walks you through exactly that. You’ll learn how to detect packet loss using built-in Windows 11 tools, understand the 9 most common causes behind it, and apply both quick and advanced fixes that actually resolve the problem — not just mask it temporarily.

---

What is Packet Loss and Why It Happens on Windows 11

Every piece of data you send or receive over the internet — whether it’s a webpage loading, a game server responding, or a voice call transmitting audio — travels in small units called packets. These packets take a path from your device through your router, your ISP’s network, multiple intermediate servers (hops), and finally reach the destination. Packet loss occurs when one or more of these packets fail to reach their destination or fail to return.

Even a small amount of loss — say 1% to 2% — can cause noticeable degradation. In gaming, it results in rubber-banding and hit registration failures. In video calls, it causes audio cutting out and frozen frames. In file transfers, it forces retransmissions that slow everything down. For a deeper breakdown of the mechanics behind this, you can read our full explanation on what packet loss is and why it happens.

On Windows 11 specifically, packet loss tends to surface more frequently than on older versions for a few reasons. First, Windows 11 aggressively manages power states for network adapters, sometimes putting them into low-power mode mid-session. Second, the OS runs more background services — telemetry, update checks, OneDrive syncing — that compete for bandwidth on already-constrained connections. Third, driver compatibility issues remain common, especially with older Realtek and Broadcom Wi-Fi chipsets that didn’t receive proper Windows 11–optimized drivers until late 2024 or 2025.

It’s also important to distinguish packet loss from latency. High latency means packets arrive slowly. Packet loss means packets don’t arrive at all. You can have perfect latency with terrible packet loss, or high latency with zero loss. They’re separate problems with separate causes, and fixing one doesn’t automatically fix the other.

The bottom line: if your internet speed tests fine but your connection still feels broken during real-time tasks, packet loss is almost certainly the culprit. The next step is confirming it with actual diagnostic data — not guessing.

How to Check Packet Loss on Windows 11 (Ping, Pathping, Tracert)

Before applying any fix, you need to confirm that packet loss is actually occurring — and ideally, identify where in the network path it’s happening. Windows 11 includes three built-in command-line tools that give you this information without installing anything. You can also supplement these with browser-based tools like the Cloudflare Speed Test, which measures packet loss, latency, and jitter in a single run.

To open Command Prompt on Windows 11: press Win + S, type cmd, and select Run as administrator. All commands below should be run from this elevated prompt.

Run Continuous Ping Test in Command Prompt

The simplest way to detect packet loss is a continuous ping test. This sends ICMP echo requests to a server and reports whether each one gets a response.

Run this command:

ping -t 8.8.8.8

This pings Google’s DNS server continuously until you stop it with Ctrl + C. Once you stop, the summary will display something like:

Packets: Sent = 100, Received = 97, Lost = 3 (3% loss)

If you see 0% loss, your connection to that server is clean. Anything above 0% confirms packet loss is present. For a more targeted test, replace 8.8.8.8 with the IP address of the server you’re actually having trouble with — a game server, a video call relay, or your default gateway.

To find your default gateway (your router’s IP), run:

ipconfig

Look for the line labeled Default Gateway under your active adapter. Pinging this address tells you whether loss is happening between your PC and router — before it even reaches the internet. For a more detailed walkthrough of ping usage, check our guide on using the ping command for internet troubleshooting.

Use Pathping to Find Exact Hop Where Loss Starts

Ping tells you that loss exists. Pathping tells you where it’s happening. This tool combines traceroute and ping — it maps every hop between your PC and the destination, then measures loss at each one over approximately 275 seconds.

Run:

pathping 8.8.8.8

After the trace completes, you’ll see a table with columns showing packet loss percentage at each hop. For example:

• Hop 1 (your router): If loss shows here, the issue is local — your cable, Wi-Fi signal, or router hardware.
• Hop 2–4 (ISP nodes): Loss at these hops means your ISP’s infrastructure is dropping packets. This is outside your control and requires contacting them.
• Final hop (destination server): Loss only at the end could indicate server-side congestion.

Microsoft’s own documentation on diagnosing packet loss recommends pathping as the primary diagnostic approach for isolating network-layer problems.

What Do the Results Mean?

Here’s how to interpret the numbers you’ll see:

• 0% loss — Connection is healthy. Your issue may be jitter or latency, not loss.
• 1–2% loss — Borderline. Noticeable in real-time applications like gaming and video calls, but may not affect browsing.
• 3–5% loss — Significant. Voice calls will cut out, games will rubber-band, and streaming will buffer.
• 10%+ loss — Severe. Connections will time out, pages will fail to load, and online games will be unplayable.
• 100% loss — Complete connectivity failure to that destination. Either the target is down, or your connection is fully broken at a specific hop.

The critical takeaway from these tests: where the loss starts determines which fix applies. If loss appears at hop 1, the problem is between your PC and router. If it appears at hop 3 or beyond, the fix likely involves your ISP or routing path — not your Windows settings.

9 Common Causes of Packet Loss on Windows 11

Now that you’ve confirmed packet loss and identified the hop where it starts, the next step is understanding why it’s happening. Packet loss on Windows 11 rarely has a single universal cause — it depends on your hardware, connection type, driver state, and network environment. Below are the nine most common reasons, ordered from the most frequent to the least obvious.

1. Weak or Unstable Wi-Fi Signal
This is the single most common cause. Wi-Fi signals degrade with distance, walls, floors, and interference from other devices operating on the same frequency. If your pathping showed loss at hop 1, a weak wireless connection is the most likely explanation. The 2.4 GHz band is especially prone to congestion in apartment buildings where dozens of networks overlap.

2. Outdated or Corrupt Network Drivers
Windows 11 doesn’t always install the best driver for your adapter. Generic drivers installed via Windows Update often lack performance optimizations and can introduce instability. Realtek, Intel, and Broadcom adapters each have known driver versions that cause intermittent drops on Windows 11, particularly builds released before mid-2025.

3. Network Congestion on Your Local Network
Multiple devices streaming, downloading, or syncing simultaneously can saturate your router’s capacity. This creates a queue overflow where the router physically cannot process all packets and starts dropping them. This is especially common on older routers with limited NAT table sizes.

4. Bufferbloat
Bufferbloat occurs when your router’s buffers become overloaded during heavy traffic, causing massive latency spikes and packet loss. It’s a distinct problem from simple congestion — your connection appears to have bandwidth available, but real-time traffic gets buried behind queued bulk data. If your internet lags during downloads, bufferbloat is likely the cause. [VERIFY — moved this link to Phase 5 where bufferbloat fix is discussed. Checking plan… Plan says this link goes in Phase 5. Let me use the jitter and video calls links here instead.]

4. Bufferbloat
Bufferbloat happens when your router excessively buffers packets during heavy traffic, resulting in both high latency and dropped packets. It commonly appears when someone on your network starts a large download and everything else — gaming, calls, browsing — degrades instantly.

5. ISP-Side Issues
If your pathping results showed loss starting at hop 2, 3, or beyond your router, the problem sits within your ISP’s infrastructure. Overloaded nodes, damaged lines, or poorly maintained peering connections all cause packet loss that no local fix can resolve.

6. Faulty Ethernet Cable or Port
Not all wired connections are equal. A damaged Cat5 cable, a loose RJ45 connector, or a failing Ethernet port on your motherboard can introduce intermittent loss. If you’re on Ethernet and still seeing drops at hop 1, the physical cable or port is a prime suspect.

7. Windows 11 Power Management Throttling
By default, Windows 11 enables power-saving features on network adapters. This allows the OS to reduce the adapter’s power state or even temporarily disable it during idle moments. For real-time applications, this creates brief disconnections that register as packet loss. This problem also contributes to related issues like jitter — small timing variations in packet delivery that degrade call quality and gaming responsiveness.

8. Background Processes Consuming Bandwidth
Windows Update downloads, OneDrive file syncing, Microsoft Store app updates, and telemetry services all run silently in the background. On limited bandwidth connections, these processes can push your link to capacity, causing the router or adapter to drop lower-priority packets. This is a frequent reason why video calls lag or freeze even with fast internet.

9. DNS Resolution Failures
While DNS issues technically cause timeouts rather than ICMP packet loss, they mimic the same symptoms — pages fail to load, connections drop, and games disconnect. A slow or unresponsive DNS server adds failure points that compound existing marginal loss into a completely broken experience.

Each of these causes maps to a specific fix. The next two sections break those fixes into two tiers: quick solutions that resolve the majority of cases, and advanced adjustments for stubborn, persistent packet loss.

Quick Fixes That Work for Most Users

If your diagnostic tests confirmed packet loss — especially at hop 1 or within your local network — the fixes below resolve the problem in the majority of cases. Start with the one that matches your connection type, then work down the list.

Switch to Ethernet (Biggest Improvement)

If you’re currently on Wi-Fi and experiencing packet loss, switching to a wired Ethernet connection is the single most effective fix. Wi-Fi is inherently lossy — it operates on shared radio frequencies, contends with physical obstacles, and is susceptible to interference from microwaves, Bluetooth devices, and neighboring networks. Ethernet eliminates all of these variables.

Use a Cat5e or Cat6 cable — not an old Cat5 cable, which lacks the shielding and bandwidth capacity for modern gigabit connections. Plug one end directly into your PC’s Ethernet port and the other into your router. Once connected:

1. Open Settings → Network & internet.
2. Confirm that Ethernet shows as the active connection.
3. Click on the Ethernet adapter and verify it shows Connected with a valid IP address.

Now re-run the ping test from earlier:

ping -t 8.8.8.8

In most cases, loss at hop 1 drops to 0% immediately. If you still see loss on Ethernet, the problem isn’t your wireless signal — it’s either the cable, the router, or something upstream.

If running a cable directly to your router isn’t practical, a powerline Ethernet adapter is a reasonable middle ground. It won’t match a direct cable’s reliability, but it’s significantly more stable than Wi-Fi for packet-sensitive applications. If your Wi-Fi keeps disconnecting on Windows 11 entirely, that’s a separate but related issue worth addressing alongside packet loss.

Restart Router + Modem Correctly

A proper restart clears your router’s memory, flushes stale NAT tables, and forces a fresh DHCP lease from your ISP. However, most people do this incorrectly — they press the power button and turn it back on within five seconds, which doesn’t fully clear volatile memory.

Follow this exact sequence:

1. Unplug the power cable from both your modem and router (if they’re separate devices).
2. Wait 60 seconds. This ensures capacitors fully discharge and cached state is cleared.
3. Plug the modem back in first. Wait until all indicator lights stabilize — typically 1–2 minutes.
4. Then plug the router back in. Wait for the Wi-Fi and internet LEDs to show a stable connection.
5. On your Windows 11 PC, open Command Prompt and run:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

These three commands release your current IP lease, request a fresh one from the router, and clear any stale DNS cache entries that might be contributing to resolution failures.

After the restart, run another ping test to check whether loss has improved. If loss was caused by router memory saturation or a stale routing table, this alone resolves it.

Update or Reinstall Network Drivers

Outdated or corrupted network drivers are a persistent cause of packet loss on Windows 11, particularly for Realtek RTL8111/8168 Ethernet controllers and Intel AX200/AX210 Wi-Fi adapters. Windows Update often installs generic Microsoft drivers that lack vendor-specific optimizations for packet handling and interrupt moderation.

To check your current driver version and update it:

1. Press Win + X and select Device Manager.
2. Expand Network adapters.
3. Right-click your active adapter (Ethernet or Wi-Fi) and select Properties.
4. Go to the Driver tab — note the Driver Version and Driver Date.
5. Click Update Driver → Search automatically for drivers.

If Windows reports the best driver is already installed, go directly to the manufacturer’s website:

• Intel: Download from Intel Driver & Support Assistant
• Realtek: Download from the Realtek support page for your chipset
• Broadcom/Qualcomm: Check your laptop manufacturer’s driver download section

If updating doesn’t help, a clean reinstall often does. In Device Manager, right-click the adapter, select Uninstall device, check Attempt to remove the driver for this device, and click Uninstall. Restart your PC — Windows will reinstall a fresh driver on boot. Then apply the manufacturer’s latest driver on top.

Intel’s own packet loss troubleshooting guide emphasizes driver updates as one of the first steps, particularly for systems running Intel Wi-Fi 6/6E/7 adapters on Windows 11.

After updating drivers, run another round of ping tests to confirm whether loss at hop 1 has been eliminated. If these quick fixes didn’t fully resolve the issue, the next section covers deeper system-level adjustments.

Advanced Fixes for Persistent Packet Loss

If the quick fixes didn’t eliminate your packet loss — or if it keeps returning after a temporary improvement — the problem likely sits deeper in your system configuration. These advanced adjustments target bufferbloat, DNS behavior, and Windows 11’s background resource management.

Enable QoS and Fix Bufferbloat

Bufferbloat is one of the most underdiagnosed causes of packet loss on Windows 11. It happens when your router’s internal buffers hold too many packets during heavy traffic, creating a queue that delays and eventually drops real-time data. You can test for it using the Waveform Bufferbloat Test — if your grade is C or worse, bufferbloat is actively contributing to your packet loss.

The fix involves enabling SQM (Smart Queue Management) or QoS (Quality of Service) on your router. The exact steps depend on your router’s firmware:

• On routers running OpenWrt or DD-WRT: Enable SQM under Network → SQM QoS. Set the download and upload limits to approximately 85–90% of your actual measured speed. This prevents buffer overflow by keeping traffic below the saturation point.
• On consumer routers (TP-Link, ASUS, Netgear): Look for QoS or Traffic Management in the admin panel. Enable it and prioritize gaming or video traffic categories.

On the Windows 11 side, you can also configure QoS through Group Policy:

1. Press Win + R, type gpedit.msc, and press Enter.
2. Navigate to Computer Configuration → Administrative Templates → Network → QoS Packet Scheduler.
3. Open Limit reservable bandwidth, set it to Enabled, and set the bandwidth limit to 0%.

This ensures Windows doesn’t reserve bandwidth for system processes at the expense of your active applications. For a detailed explanation of why your internet lags during downloads and how bufferbloat works, our dedicated guide covers the mechanics and router-level fixes in depth.

Change DNS Servers

While DNS issues don’t cause ICMP packet loss directly, a slow or failing DNS server creates timeouts and failed connections that feel identical to packet loss in daily use. Windows 11 defaults to your ISP’s DNS servers, which are often overloaded and unoptimized.

Switching to a faster, more reliable DNS provider takes under a minute:

1. Open Settings → Network & internet → Wi-Fi (or Ethernet).
2. Click your active connection, then click Edit next to DNS server assignment.
3. Select Manual, toggle IPv4 on.
4. Enter the following:

Provider	Preferred DNS	Alternate DNS
Cloudflare	1.1.1.1	1.0.0.1
Google	8.8.8.8	8.8.4.4

5. Click Save.

After changing DNS, flush your local cache by running:

ipconfig /flushdns

This clears any stale or failed entries cached from your previous DNS server. If DNS resolution was compounding your packet loss symptoms, the improvement should be immediate.

Disable Background Apps & Power Management

Windows 11 runs numerous background services that consume bandwidth and CPU cycles — both of which can contribute to packet loss on constrained connections. Additionally, the OS enables aggressive power management on network adapters by default, which can cause brief disconnections during idle moments.

Disable adapter power management:

1. Open Device Manager (Win + X → Device Manager).
2. Expand Network adapters, right-click your active adapter, select Properties.
3. Go to the Power Management tab.
4. Uncheck “Allow the computer to turn off this device to save power.”
5. Click OK.

Disable background app bandwidth usage:

1. Open Settings → Network & internet → Advanced network settings.
2. Click Data usage — review which apps consumed the most data in the last 30 days.
3. For apps consuming unexpected bandwidth (OneDrive, Microsoft Store, etc.), open their individual settings and pause or limit syncing.

To stop Windows Update from downloading during critical sessions:

1. Open Settings → Windows Update → Advanced options.
2. Toggle on Metered connection for your active network — this prevents automatic downloads on that connection.

Disable Delivery Optimization (peer-to-peer update sharing):

1. Open Settings → Windows Update → Advanced options → Delivery Optimization.
2. Toggle off Allow downloads from other PCs.

These changes collectively reduce background bandwidth competition and prevent the adapter from entering low-power states during active sessions. After applying them, run a final ping test to confirm the improvement.

---

Frequently Asked Questions

What causes packet loss on Windows 11?

The most common causes are weak Wi-Fi signal, outdated network drivers, router congestion, bufferbloat, ISP infrastructure issues, faulty Ethernet cables, Windows 11 power management throttling the adapter, background processes consuming bandwidth, and DNS resolution failures. The exact cause depends on where in the network path the loss occurs — which you can identify using pathping.

How do I check packet loss on Windows 11?

Open Command Prompt as administrator and run ping -t 8.8.8.8. Let it run for at least 50–100 packets, then press Ctrl + C. The summary shows your loss percentage. For hop-by-hop analysis, run pathping 8.8.8.8 — this identifies the exact network hop where loss begins.

Is 1% packet loss bad on Windows 11?

For browsing and file downloads, 1% loss is barely noticeable because TCP automatically retransmits lost packets. For real-time applications — online gaming, video calls, VoIP — even 1% causes visible degradation. Competitive gaming generally requires 0% loss for a clean experience.

Why do I get packet loss only in games on Windows 11?

Games use UDP protocol, which does not retransmit lost packets. Regular browsing uses TCP, which hides loss through automatic retransmission. The loss is likely present on both, but games expose it because there’s no recovery mechanism — every dropped packet translates directly into a missed game state update.

Does switching to Ethernet fix packet loss?

In most cases, yes. If your loss is caused by Wi-Fi interference, signal weakness, or wireless congestion, Ethernet eliminates those variables entirely. If loss persists on Ethernet, the cause is upstream — your router, cable, or ISP — not your wireless adapter.

Can outdated drivers cause packet loss on Windows 11?

Yes. Outdated or generic drivers can mishandle interrupt moderation, checksum offloading, and power state transitions — all of which result in dropped packets. Updating to the manufacturer’s latest driver specifically designed for Windows 11 resolves driver-related loss in most cases.

How to fix 100% packet loss on Windows 11?

100% loss means no packets are reaching the destination at all. First, ping your default gateway — if that also shows 100%, the problem is between your PC and router. Restart both devices, try a different Ethernet cable, and reinstall your network driver. If the gateway pings fine but external addresses show 100%, your ISP connection is down — contact them directly.

Will a VPN reduce packet loss on Windows 11?

A VPN can reduce packet loss only if the loss is caused by a specific bad route between you and the destination server. The VPN reroutes your traffic through a different path, potentially bypassing the congested or faulty hop. However, if loss originates from your local network (hop 1), a VPN won’t help — it adds overhead that can actually make things worse.

---

Wrapping Up

Fixing packet loss on Windows 11 comes down to two things: finding where the loss happens and applying the right fix for that location. Use ping and pathping to pinpoint the problem hop. If loss is at hop 1, your local setup — Wi-Fi, cable, driver, or adapter power settings — is the cause. If it’s beyond hop 1, the issue sits with your router configuration, ISP, or destination server.

For most users, switching to Ethernet, updating network drivers, and disabling adapter power management resolves the problem permanently. For persistent cases, addressing bufferbloat through router-level QoS and reducing Windows 11 background bandwidth consumption provides the remaining improvement.

If you’ve applied every fix in this guide and still see consistent loss beyond hop 1, the problem is with your ISP’s infrastructure. Document your pathping results — showing exactly which hop drops packets — and contact your ISP with that data. This gives their support team the specific evidence needed to escalate the issue to their network engineering team rather than running you through scripted troubleshooting.