Windows 8.1: WiFi dropping and/or "Limited"

Can Microsoft please stop telling us that manually re-installing drivers will fix the problem. It doesnt fix the problem.

I have turned off the energy saving settings.

I have tried new drivers and windows 7 drivers.

I have tried to uninstall and install the latest microsoft windows updates.

I have tried to change the ip-addresses.

And some other things I dont remember.

Why not come with a real fix. This problem has existed for more than six months now?

Thanks - sorry to have impugned you! Oddly enough, out of the blue yesterday the system started to work. I had updated the driver and done everything else suggested to no avail. I'm not sure why it started to work - I've not installed any Windows updates, not fixed the router nor anything else; which is worrying.

In case it's any use, though, on reflection, there was one minor incident. I am working on a 3G wifi router (I'm writing software from a boat in Greece - somebody has to!). I've recently changed ISP and gone from Vodafone to Cosmote. The problem seemed to start at about that time (though not exactly at that time, at first the Cosmote device worked fine as did Vodafone's)  - and for both devices (the Vodafone contract had some days left when I changed). On Friday I tried to connect to the Vodafone device and it brought up a screen to show its contract had now expired (asking me to log in rather than bringing up the browser). That was when I realised that I was again getting wifi connectivity.

So I wonder whether this is some sort of caching or persistence problem in Windows 8.1. Perhaps if  it fails for whatever reason to get a DNS connection it "remembers" that, even if the machine is turned off and rebooted, and then steadfastly refuses to reconnect. If that cache is time-limited, it will eventually expire and then the system will start to work again. That would also explain why people report that applying a fix works for a few days then fails again.

This makes me more sure that this problem is Microsoft based. Either they've got some errant code whereby this cached value remains even across a connection session, or they've mis-directed their wifi card suppliers and told them to persist some value in Windows 8.1. That would explain why going back to a previous level fixes it.

Networks - spawn of the devil!

Exactly, DanzIZme, totally agree. While digging for a solution, that's exactly what I found too... lots of Lenovo's with this issue, lots of Intel Wifi devices with this issue (some not using a Lenovo). For ME, what worked was the newest driver, and a small configuration tweak.  Eventually, I'm sure there will be a patch which will correct the issue without needing to tweak it. For now, I'm happy.

Windows doesn't handle the WiFi adapter the driver which is third party companies that are responsible for it working. Most people that have issue seem to have Lenovo laptops or devices. Complaining to them and let them know what fixed it will get a working driver to people faster then blaming Microsoft who has no more control over any third party manufacturers then anyone else.

I've been frustrated with this problem and looking for a solution too.  It seems to be predominantly a Win 8.1 problem, but I focused on hardware, and this solution WORKED for me.

My hardware:

Lenovo Yoga 2 13 Laptop

Windows 8.1

Intel Wireless-N 7260

Cisco Meraki Access Points

Go to the Intel Support site (if you're rocking an Intel Wireless) and look up the most recent driver for your 7260 (also if that's what you have).  After driver version 17.0.2 (I am using 17.0.3.2 Driver Date: 4/23/2014) there is a configuration option to disable u-APSD in the adapter settings. It's enabled by default.  IT WORKS NOW!  Reliable, moving access point to access point, and on other networks.  

A little history of my issue: I purchased this laptop recently from Best Buy. The problem started immediately when moving from access point to access point.  It would start off connected, but eventually, always go Limited.  I uninstalled the device and old drivers, and updated to the newest ones.  I even rolled down to the oldest available driver from Microsoft, that didn't work consistently.  Contacted Lenovo, and they were no real help, issuing me an RMA and saying they would swap out the WiFi card - at minimum, a 7 business day turn around.  Who reading this can do without their laptop for 2 days?  Figuring it was no different than exchanging the entire laptop at Best Buy, that's what I did.  With 100% new hardware... SAME PROBLEM!

Unacceptable, so I did more research and found this article in an Intel forum:

https://communities.intel.com/thread/51812

The very last suggestion by the Intel employee was the only thing that I tried from his list... and it worked!

I really hope this helps others.  It was an annoying problem, big enough I was about to return the thing and get something different altogether.