vista wlan autoconfig bug

The wlan autoconfig in vista(known as WZC on XP) causes lagspikes in my wireless lan connection every 60 seconds. It's extremely annoying when playing games online, but it doesn't effect anything else like web browsing or p2p. I guess this is caused by the autoconfig polling for a better connection every minute, but so far i've found no way of disabling it without not being able to connect to my wireless network. I've tried Vista Anti-lag, and Wlan optimizer, neither work. I've tried disabling the polling through the command prompt(netsh wlan set autoconfig enabled=no interface='name of network') and I still get the same results, a latency spike every 60 seconds during online games. This makes games like counterstrike unplayable, i've searched everywhere for a fix, and still i'm without one. If you guys have any ideas on a workaround, i'd appreciate it.

I'd also like to add that this isn't a hardware related problem, my wireless card is functioning properly, and this never happens when i'm using a wired connection to my router. Up until now I haven't had any problems with Vista, but if I can't fix this I guess i'm going back to XP.

 

same problem here

 

does anyone have a solution for this?

 

hate to keep bumping, but i still haven't found a way to fix this

 

any news on this?

 

In Windows Vista the networking components were designed to be much more intelligent and automatically adjust the network settings to optimize the connection speed. This is a great new feature. Your network components basically tweak themselves for optimal performance. In most situations, these components automatically adjust perfectly for best performance. However, with wireless WAN cards the detection of network conditions is flawed and can result in slower network performance.

To fix this problem, Microsoft has released a hotfix for users affected by this issue. If you have a Wireless WAN device, I suggest you give this hotfix a try.

KB 940646

 

I'm having this problem too, I've looked everywhere and can't find a solution.

Yeah I tried that and nothing. It doesn't let me disable WLAN Autoconfig and have an internet connection at the ame time. Any other suggestions?

 

The hotfix didn't work for me either, it's been quite a while and i've been searching for a solution to no avail. If anyone at all has a suggestion, it would be much appreciated.

 

Here is a nice little freeware utility which solves the problem by suppressing the 60 second scan: wlan optimizer

 

Any updates on this problem, I've used the following that MXXL has tried as he stated in his initial post and had no results, I've also downloaded the hotfix. My next move is to dump vista and go back to XP or say "I'm going to Linux, to hell with Windows!"- sigh
"I've tried Vista Anti-lag, and Wlan optimizer, neither work. I've tried disabling the polling through the command prompt( netsh wlan set autoconfig enabled=no interface='name of network') and I still get the same results, a latency spike every 60 seconds during online games."

 

Yeah I am having the same issues as well. I play cod4 and I get spikes about every 30-60 seconds. This is becoming a major problem as I play this game in competitive leagues. I've tried all the above mentioned options with no avail.

vista ultimate x86, intel pro/wireless 3945abg.

 

Hello, I've been deeling with the same problem. It is extremely frustrating. I now have to connect using a cable con. on a laptop. I created an alert on the service when it fails gives me a message. And mostly happens when high bandwidth usage and looks like if im using 80211 N network it fails more then G. So im guessing wlan ac is just not taking bandwith it requires and loses connection. I am desperet to find a solution. Please some who fixed it help us.

 

Install SP1 for Vista and download LWAN Optimizer at: http://www.martin-majowski.de/wlanoptimizer/

It's been said this didn't work, but that's before SP1. Go there for more info.

 

Also, there should be a setting in the wireless configuration that will let you adjust how ready the system should be to jumping to a better signal - it should be called something like roaming; set that so that the machine will not roam unless it absolutely has to.