Windows 8.1: WiFi dropping and/or "Limited"

to those of you still having issues, if you haven't tried the following...give it a try.  i worked for me on my toshiba L70 8.1 machine with atheros ar956x wireless adapter.

TCP/IP Stack Reset

open admin command prompt and type the following:

netsh int ip reset C:\resetlog.log

restart the computer/laptop

Disabling TCP/IP Autotuning

disable the TCP/IP autotuning.   Open admin command prompt and run the following commands one by one:

netsh int tcp set heuristics disabled

netsh int tcp set global autotuninglevel=disabled

netsh int tcp set global rss=enabled

<8<--- cut my own quoted post above here--->

What will you do if:

• Old router  G + N 150Mbs
• Old TV  G
• Old Printer  G
• smartphone G + N
• Your new computer N + W10

• hardware driver, this is a decision? or not ?

Again, the system will be guilty  :-)

EX: If one milion "go to" it is time for W11 :-)

I don't exactly understand your point, Microstuff_8.1 Was it maybe that W10 that was suggested by  ccicarl already before launch has become an unviable upgrade strategy for fixing this??? So that W11 may be the fix to W10 ?

OK, ALL my other devices of different brands at home work nicely on my new Asus RT-AC66U router - EXCEPT my old Dell that I fitted with a new Intel AC7260 adapter. Bought the AC router and card after the very unfortunate FREE upgrade of my Win 8.0 to 8.1 that failed and that I have regretted as a dog ever since and put hundred+hours into trying to fix without luck.

JUST DON'T DO IT is my only advice - or maybe wait till W11 if I understand your advice (?)

I had this problem with my IPHONE5S and a Dell Venue 11 Windows 8.1 pro tablet. Always getting limited connectivity on Hotspot Wifi connection.

After reading this thread I tried a few things and determined it was definitely the IPHONE and the Tablet not connecting well as other devices connected to the IPHONE fine as well as my tablet to other mobile devices.

I finally found and updated the Wireless AC 7260 adapter driver from INTEL to a version 17 from late 2014 as opposed to a version I had from 2013.

It immediately started working on first attempt afterwards and will see how it goes..... Thanks for all the good help in finding the problem.

Same problem with HP Pavillion dv6 that started shortly after I upgraded to Win 8.1.  I suspect Win 8.1, itself, or one of it's updates. Please help, Microsoft.

I respect and think I understand what you write here, ccicarl - BUT it's not enlightening. There maybe hope that history mayrepeat itself (as with W7, W3.11) and that the industry (not MS!?) mayput enough effort into it to fix W10 (...but probably not W8.1, if so - I guess a response team already would have gotten into it...)

After reading this, my conclusion is that we, who have tried all possible tricks during the past 18 months - without resolution - are to be left in the cold until W10 mayfix things :-(

(Btw, my impression is also, that the finger seems to be (too) politely pointed at MS from other vendors...)

Having worked with MSFT for many years, often in Redmond, I am well experienced with driver development and how the process usedtowork. My lab would never have tolerated a situation that affects so many users to linger. 

<...cut...>

As would have been expected, Dell advised I contact MSFT, as did Intel, regarding this issue. 

I respond and monitor this thread on behalf of my clients. Myself and all of the engineers I work with prefer and still use W7 for technical and lab use. Not because we want tobut because the industry has not come together in the historical and successful manner of W7, W3.11, etc., to make W8.1 solid enough. Hopefully W10 will

What will you do if:

• Old router  G + N 150Mbs
• Old TV  G
• Old Printer  G
• smartphone G + N
• Your new computer N + W10

• hardware driver, this is a decision? or not ?

Again, the system will be guilty  :-)

EX: If one milion "go to" it is time for W11 :-)