5G Wi-Fi transmission freezes every 10s in Windows 10 - how to fix it?

Question

WiFi

I noticed that every 10 seconds the data transfer rate drops to zero


. As it turned out later, this does not even depend on the load on the network:

ping -t 192.168.0.1

Packet exchange from 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: number of bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: number of bytes=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=3638ms TTL=64
Response from 192.168. 0.1: number of bytes=32 time=1ms TTL=64
Response from 192.168.0.1: number of bytes=32 time=2ms TTL=64
Response from 192.168.0.1: number of bytes=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168. 0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Request timed out.
Response from 192.168.0.1: byte count=32 time=3ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: number of bytes=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=3ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2972ms TTL=64
Response from 192.168.0.1: byte count=32 time=5ms TTL=64
Response from 192.168. 0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=3ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=3ms TTL=64
Response from 192.168.0.1: byte count=32 time=2984ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168. 0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=3ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=3351ms TTL=64
Response from 192.168.0.1: byte count=32 time=3ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168. 0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=1ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Query timeout exceeded.
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=4ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168. 0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=2ms TTL=64
Response from 192.168.0.1: byte count=32 time=3ms TTL=64
Response from 192.168.0.1: bytes=32 time=3178ms TTL=64
Response from 192.168.0.1: bytes=32 time=1ms TTL=64

this is only on Win 10 (the same computer and adapter, but Ubuntu 16 - everything is OK), on different devices (I tried a laptop with this adapter). If you switch to the 2.4G band, there is no problem. I rolled back the driver, disabled all protocols except IPv4 / IPv6 in the settings - it did not help. Adapter TP-Link Archer T4U , a dozen with the latest updates. Tried disabling IPv6 - same thing.
I noticed this last week somewhere, perhaps after the latest Windows updates, but these are just guesses, maybe it has been like this for a long time.