Vista Auto-Tuning
Vista introduces a new feature called “Receive Window Auto-Tuning”. What it does is to adjust the receive windows size continually based upon the changing network conditions. You can see this article if you are interested in details.
Some people reported that auto-tuning cause network time-out problems with some applications and routers. You can turn it off if you have experienced such problems.
- Open up an elevated command prompt.
- Enter the following command to disable auto-tuning
netsh interface tcp set global autotuninglevel=disabled
If you found that this doesn’t fix your problem, you can turn it back on.
- Open up an elevated command prompt.
- Enter the following command to enable auto-tuning
netsh interface tcp set global autotuninglevel=normal
You can use this command to view the states of the TCP global paremeters.
netsh interface tcp show global
[Update: 12/21/2007] I found that for some routers, no matter what settings you use, the network stops working after a while. To solve the problem, you just have to run the command again.
on March 20th, 2007 at 9:35 pm
This command is also known to correct problems for people who cannot access HTTPS sites using IE7 in Vista.
on April 4th, 2007 at 5:08 am
This has also solved the login issues with Windows Live Messenger. If anyone sufferes the spinning people after entering password and nothing ever happening try this FIX ! !
Worked for me ! in fact every thing seems better.
on May 1st, 2007 at 12:44 pm
Also fixes SEVERE performance issues with Remote Desktop and Dameware…. un-useable in Vista unless you disable Auto Tunning
on May 5th, 2007 at 8:44 pm
I have found that setting autotuning to HIGH also corrects the problem:
netsh interface tcp set global autotuninglevel=highon November 10th, 2007 at 4:54 pm
I have being having a problem where my connection works fine for a couple of hours, but then suddenly I cannot access the internet, although it still shows data been recieved and sent.
I have just bought this new system:
AMD Athlon 64×2 3.0ghz AMZ
ASUS M2M SLI Deluxe
Gigabyte GV-NX86T512H PCI-E GeForce 8600GT Graphics
Western Digital Carvair SATA2 HD
3GB HYNIX SDRAM
Vista Home Premium 32
The other computer on the network is not expericing any timeouts or connection problems, running XP. Both computers connect via 5port Qos Switch, which is connected to our ADSL modem provided by our ISP.
I have just run your command above and hoping this will fix my problem, or are you albe to tell me what my problem could be.
My network adapter controller, driver version is 65.7.4.0 and it says it is up-to-date. However I do not know how to adjust the properties of the controller for better performance.
Have googled and googled and still not found a solution or a why.
on November 10th, 2007 at 10:31 pm
Pearlsofwisdom,
You can try this hot fix.
http://support.microsoft.com/kb/931770/en-us
The other thing to consider is turn off remote differential compression.
on November 12th, 2007 at 12:15 am
I actually rolled back my driver and instead of using the NVIDIA one, I rolled it back to a microsoft one, and the instant I did that, I got my connection back. Today I have not lost connection at all. I will bookmark your link in case I have any further future problems.
on November 12th, 2007 at 12:16 am
Oh BTW…thanks for your reply
on December 20th, 2007 at 6:57 pm
[...] now on, I will be disabling auto-tuning on every Windows Vista Machine I ever work on. To quickly run this command, open up an command [...]
on January 1st, 2008 at 7:25 pm
very nice information , thx
on January 8th, 2008 at 9:03 am
Hey amida your the greatest. I used to get latencies of 5000+ in World of Warcraft under vista but now after entering the CMD i am now getting an average of 320 ms…….THANKS!!!!
P.S I used your name by mistake lol.
on January 8th, 2008 at 10:13 am
Serrone,
You are welcome.
on January 14th, 2008 at 2:01 pm
Thank you, thank you! My HP Office Jet Pro L7780 now prints full jobs! This was driving me crazy!
on January 14th, 2008 at 2:25 pm
Kansas A,
You are welcome.
on January 19th, 2008 at 2:37 am
It doesn’t let me, it says “Set global command failed on IPv4 The requested operation requires evaluation”
on January 19th, 2008 at 8:55 am
Yorico,
That’s because you didn’t open an elevated command prompt. Please follow the link in the step 1.
on January 23rd, 2008 at 3:21 am
Thanks! It works for me.
on February 13th, 2008 at 7:03 am
Thanks Works like a charm on my system
on February 20th, 2008 at 11:13 pm
I disabled the autotuning function and it still times out. Any more options?
Thanks
on February 21st, 2008 at 9:45 am
Ed,
Please see comment #6.
on February 21st, 2008 at 8:59 pm
THX!!!!!!!!!!!!!!!!!!!!!!!!
on February 21st, 2008 at 9:24 pm
Try the hotfix or turning off the remote differential compression
Thanks Amida168
on March 2nd, 2008 at 1:21 am
well…..i put the next command
netsh interface tcp set global autotuninglevel=normal
but…..it keep saying to me:
Set global command failed on IPv4 The requested operation requires elevation.
can anyone help me……???
i have a really bad problems with MMORGames
on March 2nd, 2008 at 8:09 am
Lester,
You need to type the command in an elevated command prompt. See the step #1 on how to do this.
on March 5th, 2008 at 12:26 am
hey….really thank you…i have to learn to put more attention…
(XD)
ok…see you
on March 24th, 2008 at 9:41 am
Re: Christopher Says:
May 5, 2007 at 8:44 pm
I have found that setting autotuning to HIGH also corrects the problem:
netsh interface tcp set global autotuninglevel=high
Thanks Christopher. After setting autotuning to disable i was still unable to connect to the .Net Messenger Service. This was the only solution that worked for me so thank you. I’m running Vista Ultimate with Norton 360 as my firewall program.
on April 19th, 2008 at 2:46 am
I tried the netsh interface tcp set global autotuninglevel=disabled but it wouldn’t work how do I put the setting back to normal
on April 19th, 2008 at 8:04 am
Jose,
Have you tried netsh interface tcp set global autotuninglevel=high ? If it still doesn’t work, just use netsh interface tcp set global autotuninglevel=normal .
on April 20th, 2008 at 5:59 am
There’s no reference anywhere to the setting “autotuninglevel=high”. Just to let you know this command does not do anything.
The manual autotuning settings can be overwritten only when CMD prompt is opened with admin privileges. Sometimes they are also ‘protected’ by the Group policy setting, which block manual changes. You need to edit the Group Policy through ‘gpedit.msc’ to overcome this blockage (find it somewhere under ‘computer setting’)
on April 20th, 2008 at 12:04 pm
Hey thanks,
I didn’t know that Vista had this option. I have Vista installed with Microft Virtual PC so I can play around with it before I decide to have it as my main operating system.
I look foward to trying a few of these things out.
Take care,
Paul
on May 7th, 2008 at 3:38 pm
intriguingly this setting does seem to un-set itself on every system across the board eventually. I queried the current status of the TCP interface using the last command stated above about 20 minutes after the first time I set it, and it had returned to “normal”. So I reset it, and it remained disabled for a month or so. Then I installed SP1 on Sunday (3 days ago) which did not affect it instantly - I checked it after the install and 3 reboots. And yet I checked it today and it had set itself to “highlyrestricted”. I have seen similarly eratic behaviour from around 15 other machines at various locations on various networks.
Could this be something to do with the fact the that this feature is (I suspect) mainly aimed at use on IPv6 networks, and 99.99999% of the world still runs on IPv4? It sounds like Microsoft trying to be too clever to me…
on July 11th, 2008 at 6:33 pm
@daverandom
IE 7 sets it to restricted strangely enough. The Local group policy can also be configured to set it to a certain setting. This setting supersedes manual setting.
on August 20th, 2008 at 2:45 pm
thanks!