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.

  1. Open up an elevated command prompt.
  2. 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.

  1. Open up an elevated command prompt.
  2. 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.

This post may contain affiliated links. When you click on the link and purchase a product, we receive a small commision to keep us running. Thanks.


  1. 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.

  2. Also fixes SEVERE performance issues with Remote Desktop and Dameware…. un-useable in Vista unless you disable Auto Tunning

  3. I have found that setting autotuning to HIGH also corrects the problem:

    netsh interface tcp set global autotuninglevel=high

  4. 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


    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 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.

  5. 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.

  6. 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.

  7. well…..i put the next command

    netsh interface tcp set global autotuninglevel=normal

    but… 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

  8. 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.

  9. 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 .

  10. 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’)

  11. 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,

  12. 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…

  13. @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.

  14. I also had the host problem and believe it or not after a couple of hours surching i came here and i didnt red of the option aututuning high and…….. YES id did work for me also

    gr from holland

  15. That it goes back to highly restricted has to do with the heuristics setting. First you need to disable and then run the commands again. To disable it run the following command:

    netsh interface tcp set heuristics disabled

1 Trackback / Pingback

  1. Lenovo System Update Woes! **SOLVED**

Leave a Reply