Packet loss on Wi-Fi but not Ethernet points first to the wireless hop between the device and router, not automatically to the ISP or game server. Reproduce the problem, ping the router, compare Wi-Fi bands and position, inspect the Windows wireless report, then change one setting at a time.
Windows ping, Wi-Fi troubleshooting, and wireless-report steps were checked against current Microsoft documentation on July 24, 2026. The public comparison address was checked against current Cloudflare documentation.
IN THIS GUIDE
Getting packet loss on Wi-Fi but not Ethernet is one of the more useful troubleshooting clues. The game, ISP, and server did not suddenly become nicer because you found a cable. Your test changed the short wireless hop between the device and router, so that hop moves to the front of the suspect line.
It is still a clue, not a conviction. A wired test performed at noon cannot clear Wi-Fi tested during the evening download festival. Compare the same device, game, region, and time window before changing six router settings and summoning a new problem.
Prove the Wi-Fi and Ethernet results are comparable
Start with a controlled A/B test. Use the same PC or console and the same nearby game region. Pause downloads, cloud backup, livestreaming, and device updates. Play or test over Wi-Fi, then plug the device directly into the main router with a known-good network cable and repeat within the same hour.
Record three runs for each connection:
- time and game mode
- displayed ping and packet loss
- whether the problem affected one match or every match
- Wi-Fi band and room location
- anything else using the connection
One clean wired match is encouraging, not peer review. If all three wired runs stay clean while all three wireless runs lose packets, you have a repeatable local difference. If Ethernet also loses packets, move to the broader packet loss but internet is fine checklist.
Do not use download speed as the deciding result. A speed test can finish successfully while short bursts of wireless loss make a real-time game wobble. Throughput is how much data arrives. Packet loss is data that does not arrive. They can be annoying in separate ways.
Ping the router before the wider internet
On Windows, open Command Prompt and run ipconfig. Find the Default Gateway for the active Wi-Fi adapter. Then test that router address:
ping -n 200 YOUR_GATEWAY_IPA common example is:
ping -n 200 192.168.1.1In a second Command Prompt, run a public comparison:
ping -n 200 1.1.1.1Microsoft documents ping as a reachability and round-trip-time test. Cloudflare lists 1.1.1.1 as a public resolver address. It is not your game server, so use it as a second checkpoint, not a tiny courtroom.
Run both tests while the game problem is happening, first on Wi-Fi and then over the network cable.
| Wi-Fi result | Ethernet result | First place to inspect |
|---|---|---|
| Router ping loses packets | Router ping stays clean | Wireless signal, interference, band, adapter, or access point |
| Router ping stays clean, public ping loses packets | Both stay clean | Wireless handling under load or a test that needs repeating |
| Router and public pings lose packets | Ethernet also loses packets | Router, modem, ISP path, household traffic, or wider outage |
| Both pings stay clean | Game still reports loss | Game route, server, client, or traffic the ping test did not reproduce |
Some devices and routers limit diagnostic replies, so one missed response is not proof. Look for a repeatable pattern that appears on Wi-Fi, disappears on Ethernet, and lines up with the actual game problem.
Fix the wireless hop one variable at a time
Once the gateway test points to Wi-Fi, work from the simplest physical comparison outward:
- Move closer to the main router. Test in the same room with a clear path. If loss disappears, distance, walls, or interference is involved.
- Bypass extenders and powerline adapters. Connect to the main access point for the baseline. Extra hops add extra places for a packet to take unpaid leave.
- Compare frequency bands. Microsoft notes that many consumer routers offer 2.4 GHz and 5 GHz networks. Try the other band. In general, 5 GHz can be cleaner at short range, while 2.4 GHz reaches farther but often shares more crowded spectrum.
- Reposition the router and device. Keep the router open and elevated rather than behind a television, inside a cabinet, or beside other electronics.
- Restart using the router maker’s instructions. This can clear a stuck state, but a daily reboot habit is evidence that something still needs diagnosis.
- Update the wireless adapter driver and router firmware. Use the PC, adapter, or router manufacturer’s official support page. Avoid driver-updater roulette.
- Test automatic versus a cleaner channel. Use the router’s documented controls. Save the original setting and change only one band or channel option before retesting.
After each change, repeat the same gateway and game test. If you change the band, channel, driver, router position, and three advanced adapter values at once, a good result teaches you nothing and a bad result earns you a factory-reset side quest.
For recurring spikes rather than steady loss, the timing worksheet in our ping spikes every few seconds guide can help reveal background scans, uploads, or repeatable local events.
Read the Windows wireless report
Windows can generate a report covering recent wireless sessions. Open Command Prompt as administrator and run:
netsh wlan show wlanreportMicrosoft says the resulting HTML report includes Wi-Fi events from the last three days, connection sessions, failures, warnings, adapter details, and disconnect reasons. Match those timestamps to your game notes.
Look for:
- the wireless session ending when the game stuttered
- repeated disconnect reasons
- driver or adapter failures
- a network switch between access points or bands
- the same warning before several bad sessions
The report is supporting evidence. A disconnect at the exact recorded time matters more than an old warning from yesterday. If the report stays clean and gateway pings stay clean, the game may be reporting loss farther along the route.
Know when Wi-Fi is no longer the main suspect
Stop tuning wireless settings when the evidence changes:
- Ethernet also loses packets: inspect the cable, router port, household load, modem, ISP access, and wider route. Our high ping on Ethernet guide covers that branch.
- Only one game reports loss: check its official status, compare another nearby server, and save match IDs. Different games can use different destinations.
- The picture hitches but network stats stay steady: inspect frame time, CPU, GPU, storage, and overlays. That is likely performance stutter wearing a network costume.
- Loss appears only during uploads or downloads: pause the traffic and retest. Congestion can increase loss and delay, as the IETF’s UDP guidance explains.
A VPN does not repair the wireless hop. Its packets still cross the same Wi-Fi link before reaching the VPN server. Once gateway tests are clean, a VPN can be tested as a route comparison if one upstream path remains troublesome. Read does a VPN lower ping? before treating a single lucky match as a permanent upgrade.
FAQ
Why do I get packet loss on Wi-Fi but not Ethernet?
The wireless connection between your device and router may be losing or delaying traffic because of weak signal, interference, a crowded band, an extender, an adapter issue, or an access-point problem. A repeatable wired comparison makes those local causes more likely, but it does not identify which one without further tests.
Can 5 GHz Wi-Fi fix packet loss?
It may help at short range when the 2.4 GHz band is crowded. It can also perform worse through distance and walls. Test both bands from the same position, record the gateway result, and keep the one that is consistently cleaner.
Does changing DNS fix wireless packet loss?
Usually not. DNS helps the device find a service address. It does not repair packets dropped between the device and router during an active match. A DNS change may fix a lookup or sign-in issue, but it is not a general Wi-Fi loss fix.
Can a gaming VPN fix packet loss on Wi-Fi?
Not when the loss begins between the device and router. A VPN uses that same wireless hop. It may help later if the local connection is clean and the direct upstream route is the problem, so test it only after the gateway result is stable.
If the local hop is clean and one upstream route still behaves badly, join the LagZero list to compare a nearby route when access opens. No guaranteed lower ping, just a controlled test with fewer mystery toggles.