Windows 10 experts help if possible.

[toseland]

Ok so here is the deal..

wlan autoconfig is causing issues as of late with the PC.. was running smooth as a babies bottom so to speak..


Anyway cue a nice huge HDD failure and reinstall of windows,  everything remains the same but this time wlan autoconfig is causing massive issues.. 

I have so far
Reinstalled drivers for wlan card
Started and stopped, refreshed all DLL files for the network associated anything.. 
changed Wifi card, with new aerials, just in case.

Anyhow.. the issue manifests itself quite simply as lagspikes in any sort of online streaming activity.. whether that is gaming, skype calls, youtube etc and is noticeable with a significant lagspike every exactly 10seconds. 

using the command "netsh wlan set autoconfig enabled=no" completely stops the issue,  as does restarting the wlanautoconfig service from services.msc in winblows. but if you dont reenable autoconfig and your connection drops (ie you restart) you will have no connectivity until the autoconfig is turned back on, which is massively inconvenient (having to open up command prompt every time)

below is a small snippet of a ping to google.com showing how it manifests. Microsoft techsupport have been absolutely f*cking useless with this and but have practically rebuilt the system.

The issue will continue for maybe 120seconds and each 10 second interval will see the ping lower somewhat returning to normal after a while for 5-6 minutes then go again. 

eply from 172.217.17.68: bytes=32 time=600ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=24ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=528ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=462ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=24ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=23ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54
Reply from 172.217.17.68: bytes=32 time=498ms TTL=54
Reply from 172.217.17.68: bytes=32 time=22ms TTL=54

[cully]

your woggle pin is broken!

[Ruan]

What network adapter?
What AP?

Bet you it's an adapter driver bug/fault, will likely need to wait for a later release of the driver to fix it...

[toseland]

Had a tp link wireless n150, changed that to, with a fresh install of drivers, an Asus n300 one.

[Ruan]

What chipset is each using?!