Running Wireshark works for me too. I dug into it a bit and it seems related to the "Npcap Packet Driver" (npcap) that Wireshark installs. You can view it by running msinfo32.exe, then Software Environment > System Drivers. Look for npcap. You can see info there but can't change its Running state. To do that you can use command line "net stop npcap" and "net start npcap".   I've found that if you run (and then immediately close) Wireshark to get the decent speeds, and then stop the npcap driver, it goes back down to the bad speed. But then simply restarting the driver doesn't help; you've got to restart Wireshark. Note that if you try to stop the driver with WS still running, it fails- WS must have a lock on it.   So, there's something more going on; probably WS is doing something else when it starts, either directly or there's some dependency involving npcap. I'll post again if I learn any more that might help.     ... View more