Windows 10: Lossing Internet Packets only on Windows 10

Discus and support Lossing Internet Packets only on Windows 10 in Windows 10 Gaming to solve the problem; Hello, when i bought computer with windows 10 i realized, i got normal ping, but sometimes i got weird delay in League of Legends. Then i turned ON cs... Discussion in 'Windows 10 Gaming' started by masynmassino, Sep 7, 2018.

  1. Lossing Internet Packets only on Windows 10


    Hello,
    when i bought computer with windows 10 i realized, i got normal ping, but sometimes i got weird delay in League of Legends. Then i turned ON cs go, with net_graph, which showed me loss from 0 to 2%.

    Then i went to console, and pinged LOL IP, and look at this raports below my text - i got serious loss (7% !!). And i tried it on my second computer with windows 7 - its 0% loss. I tried on diffrent wifi, in my second house, from diffrent technology router and diffrent operator company - THE SAME. I got loss only specificly THIS computer.

    I did many things to fix it, like performance personalising, some youtube tutorials with REGEDIT, some windows update turning off, drivers actualisation of webcard, turning off xBox options, dvrs, blocking xbox with firewall, etc.... nothing helps. I still got the loss as BELOW:

    C:\WINDOWS\system32>ping -t 104.160.142.3

    Pinging 104.160.142.3 with 32 bytes of data:
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=40ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Request timed out.
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=38ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=46ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=133ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=38ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Request timed out.
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=52ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Request timed out.
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=38ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Request timed out.
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=39ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Request timed out.
    Reply from 104.160.142.3: bytes=32 time=38ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=40ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=40ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=44ms TTL=56
    Request timed out.
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=38ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=37ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=38ms TTL=56
    Reply from 104.160.142.3: bytes=32 time=36ms TTL=56

    Ping statistics for 104.160.142.3:
    Packets: Sent = 83, Received = 77, Lost = 6 (7% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 133ms, Average = 38ms
    Control-C
    ^C
    C:\WINDOWS\system32>

    C:\WINDOWS\system32>

    C:\WINDOWS\system32>pathping 104.160.142.3

    Tracing route to 104.160.142.3 over a maximum of 30 hops

    0 DESKTOP-NEPKP5J [192.168.100.3]
    1 192.168.100.1
    2 10.0.2.35
    3 10.0.2.34
    4 89.228.6.21
    5 89.228.6.22
    6 89.228.6.17
    7 host-89-228-40-1.dynamic.mm.pl [89.228.4.1]
    8 * * *
    Computing statistics for 175 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 DESKTOP-NEPKP5J [192.168.100.3]
    0/ 100 = 0% |
    1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.100.1
    1/ 100 = 1% |
    2 13ms 1/ 100 = 1% 0/ 100 = 0% 10.0.2.35
    0/ 100 = 0% |
    3 13ms 3/ 100 = 3% 2/ 100 = 2% 10.0.2.34
    0/ 100 = 0% |
    4 19ms 1/ 100 = 1% 0/ 100 = 0% 89.228.6.21
    1/ 100 = 1% |
    5 --- 100/ 100 =100% 98/ 100 = 98% 89.228.6.22
    0/ 100 = 0% |
    6 21ms 2/ 100 = 2% 0/ 100 = 0% 89.228.6.17
    0/ 100 = 0% |
    7 17ms 2/ 100 = 2% 0/ 100 = 0% host-89-228-40-1.dynamic.mm.pl [89.228.4.1]

    Trace complete.


    If someone got idea, ill be happy and thankful. Ty.

    :)
     
    masynmassino, Sep 7, 2018
    #1

  2. Experiencing Severe packet loss and high pings

    Bump, the command spearman suggested boosted the d/l speed to 70kb/s, however it didn't fix the packet loss issue, the ping issue's still there but has much less of an effect.
     
    crazy pyro, Sep 7, 2018
    #2
  3. Jetling Win User
    Packet Loss in Windows 10 Only

    So I have scoured the internet and this community forum to try and figure out what the **** is going on with windows 10 and my home network. So, let me start off with what is happening.

    So I upgraded my computer running Windows 7 to Windows 10 via the free upgrade a while back. I rarely use my computer but I did noticed that internet was really slow on it, however, I didnt really do anything about it. Now however, I am starting to use it
    for training and the slow internet was killing me so I started investigating into it. It turns out I was getting heaps of packet loss ranging from 11% to a whooping 32%. Thinking it was my network card, I reinstalled the drivers to it (as well as everything
    else) but still have packet loss. I ended up doing a full format since it was 'upgraded' to Windows 10. After the full format and reinstall of windows, I have the same issue. I ended up buying a USB Wireless AC dongle but I still have massive amount of packet
    loss.

    I borrowed my brothers laptop which was running Windows 10, connected it to the wifi and still getting packet loss issues. I also tried the Ethernet port on the laptop and still the same issue. Now, my phones, tablets, Wii U and etc all have 0 issues, there
    is no issues pinging the router or wireless access point. I grabbed my work laptop which is running Windows 7 and I have no issues with that as well, so its only isolated to Windows 10.

    I tried everything I could find on the internet... Disabling P2P updating, turning off power management, disabling Cortana, disabling HIT, flushing DNS, release and renew IP address, updated windows and all of the hardware drivers... Nothing seems to fix
    the problem. Now to add a spin onto this issue, when I turn on the hotspot on my smartphone and connect the PC and laptop running Windows 10 to it, I get 0 packet loss.

    I spoke to my ISP and they said there is no issues on their end and since its running perfectly fine with all the other devices but only have packet loss issues with Windows 10, they believe its a compatibility issue with Windows 10 and my home network.

    Now heading out and replacing my ADSL router and my $300 AC AP is out of the question and I dont have another ADSL router that I can use to test. So anyone here has any suggestion? I want to avoid going back to Windows 7 if I can so any suggestions is much
    appreciated.
     
    Jetling, Sep 7, 2018
    #3
  4. jellymold Win User

    Lossing Internet Packets only on Windows 10

    Packet Loss in Windows 10 Only

    ONEDRIVE!!!!!!!!

    I got a new windows 10 and suddenly my xboxlive games keep dropping out on my xbox. If you have xbox you can test the network statistics very easily.

    Here's the result.

    PC TURNED OFF COMPLETELY

    Latency 166ms

    Packet Loss 0%

    upload 0.91mbps

    dowmload 11.04

    PC TURNED ON (Idle)

    Latency 231ms

    Packet Loss 33%

    upload 0.13mbps

    dowmload 10.99

    Wow packet loss 33% with the pc on and idling.

    Right click on onedrive in file explorer and turn off the starts automatically (etc).

    Otherwise your pc is constantly uploading your hard drive contents to the internet and any files you alter as well. Its a crazy bandwith eating monster.
     
    jellymold, Sep 7, 2018
    #4
Thema:

Lossing Internet Packets only on Windows 10

Loading...
  1. Lossing Internet Packets only on Windows 10 - Similar Threads - Lossing Internet Packets

  2. Packet loss due a driver problem

    in Windows 10 Ask Insider
    Packet loss due a driver problem: I made this post on more than 10 forums, TP-Link support, Microsoft forum and more. No one can solve and i hope you guys can. I have a TL-WN8200ND v2 adapter to use Wifi, on the lastest windows updates (1909, 1903, 1803, 1809) this device started to be slower than ever, I...
  3. Ping spikes / Potential packet loss

    in Windows 10 Network and Sharing
    Ping spikes / Potential packet loss: Good evening, Recently I have switched over to Verizon Fios as my ISP. I have a dual band USB adapter in my PC which allows me to connect to WiFi. After having Fios for 2 weeks, I have noticed that I am getting consistent Ping spikes when playing games or even browsing the...
  4. Wifi Menu packet loss?

    in Windows 10 Network and Sharing
    Wifi Menu packet loss?: Hello, I have been using the ASUS ac1200 56r use wireless adapter for a couple months now and it has been a pain to say the least. I have constant wifi drops on 5GHz and randomly my receive would drop to 0 Kbps ranging from half a second and sometimes up to 5. I as able to...
  5. 0% Network Utilization, Packet Loss

    in Windows 10 Network and Sharing
    0% Network Utilization, Packet Loss: Hey, so as of yestarday, 10/20/19, for some reason task manager decided to stop showing network utilization, and keep it at 0% for everything. I checked the network details in the performance tab for network, and here is what it looks like. I have a wireless connection, and...
  6. 100% Packet Loss

    in Windows 10 Network and Sharing
    100% Packet Loss: I've been experiencing this problem for a couple of days now. My wifi works but I either I can't connect to a game or I am getting massive ping spikes every couple of seconds....
  7. Packet loss is 100% in the application Xbox for Windows

    in Windows 10 Software and Apps
    Packet loss is 100% in the application Xbox for Windows: Packet loss is 100% in the application Hbox for Windows after starting the local server through OpenServer. I previously tried to reinstall Windows and the problem was solved, but after restarting OpenServer, the problem returned. I turned to the provider, he says that there...
  8. Packet loss after computer upgrade

    in Windows 10 Network and Sharing
    Packet loss after computer upgrade: I recently upgraded my 9 year old computer from an i7-860 to a Ryzen 7 2700X along with a MB and DDR4 ram. Since the upgrade everything has run well, except for lag spikes in gaming that I think are related to packet loss. I am pretty sure I had this problem to some extent...
  9. LAN packet loss

    in Windows 10 Network and Sharing
    LAN packet loss: Hello , This is a strange one, every test of ping i got a packet loss using Ethernet cable but when i use WI-FI adapter it's work fine (no packet loss) . Im sure that the router is OK and my hardware & software (motherboard) is OK, i tested with same pc a portable Linux...
  10. Loss of internet connectivity

    in Windows 10 Network and Sharing
    Loss of internet connectivity: I am posting this in what may be a brief window of connectivity. Last night I was unable to restore either Ethernet or Wireless connectivity in any of the ways that usually work, including a network reset. My ISP (BT, UK) told me they had a fault but later changed their mind;...