I am having issues with my new Archer TX20UH with intermittent ping spikes, sometimes over 500 ms, on my computer running windows 10.

Similar issue as described for other adapters here https://community.tp-link.com/en/home/forum/topic/509006

I do not have the problem with my tp-link T3U Nano.

Is there any solution for this problem for this adapter?

I have updated the driver to the 5001.15.134.1 from realtek and have a feeling the the problem is much better (it still uccurs but not as frequent). These drivers seems unstable though, the adapter dies after some use and needs to be plugged out and in to start working again.

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=248ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=82ms TTL=64
Reply from 192.168.1.1: bytes=32 time=194ms TTL=64
Reply from 192.168.1.1: bytes=32 time=186ms TTL=64
Reply from 192.168.1.1: bytes=32 time=176ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64