Internet is slow only on one Windows PC
Find PC-specific causes of poor internet performance with controlled comparisons.
- Updated
- September 3, 2026
- Reading time
- 7 min read
- Windows support
- Windows 11 · Windows 10
Quick diagnosis
Find PC-specific causes of poor internet performance with controlled comparisons. The key distinction is whether “One PC tests slower” occurs by itself or together with “latency affects one pc.” That difference helps separate background transfers from weak wi-fi.
Symptoms
- One PC tests slower
- Latency affects one PC
Likely causes
- Background transfers
- Weak Wi-Fi
- VPN or driver issue
Quick reversible checks
- Pause cloud sync
- Compare Ethernet and Wi-Fi
Establish the scope
Confirm when one pc tests slower and whether latency affects one pc. Note the exact time and the last relevant change, then compare the closest known-good device, account, connection, or application using the same task.
Apply the safer fix first
Use Task Manager and Resource Monitor to find network-heavy processes. Compare the same server, location, and connection type.
- Record the current state related to pause cloud sync.
- Apply the narrow change, then check whether one pc tests slower.
- Continue only if the result still points toward weak wi-fi.
Investigate the cause
Ping the gateway, review negotiated link speed, test without VPN, and update the OEM adapter driver before changing advanced properties.
Protect the recovery path
Before work that could affect network & internet, protect relevant files and sign-in or recovery credentials. Keep the original error wording and the results involving background transfers, weak wi-fi, vpn or driver issue for support.
Verification
- Repeat the affected task under the same conditions used to confirm one pc tests slower. Confirm the symptom is gone, not merely that a Windows status label changed.
- Repeat the relevant connection, startup, sign-in, sleep, application, or device transition and specifically check whether latency affects one pc.
When to stop
Do not continue with broader resets when loss persists on known-good networks or Ethernet cannot negotiate a stable link. Preserve the observations already collected and use the device maker, network administrator, Microsoft support, a qualified repair technician, or data-recovery help according to the evidence.
Review the safe troubleshooting workflow before any broader recovery step.