Windows 8.1: WiFi dropping and/or "Limited"

Same problem after upgrade to 8.1.

lenovo y510p and vaio pro SVp 13xxx

Good point! They do have a network called MSDN they publish items like this http://msdn.microsoft.com/en-us/library/windows/hardware/dn312128(v=vs.85).aspx and Microsoft has these too http://support.microsoft.com/kb/2749073/en-us

However, the error limited connection is like saying my car doesn't work. The issue could be the router, the NIC, the driver, virus software. user error or any combination. On top of that there isn't much information that is usable to figure out what the issue is. The network troubleshooter handles many of the parts windows has control of and that they can get errors from and try to figure out what the issue are. 

The WiFi issue is unique. For example, the network goes down and is limited (the data given to the PC isn't working) The router can't log errors so the next time you get connected the router works and has no clue what happened and because this issue was the router Windows only knows that it didn't work, it has no access to why,  

The info is collected when it can be, including the field team that services PCs at business usually, and is used to release updates (which is catch 22, the computer can't connect so it doesn't go to get them and you have to do it manually). When possible they notify the manufactures. The thing that would help the most is if a user has an issue, and they can't solve it, they contact the PC maker or the hardware maker to let them know.

However, what happens is people write it off as Windows and the hardware makers do the same, ignoring the customer. The interesting part of that is the PC maker is supposed to offer support for 1 year even if the issue is Windows. They get a discount for doing this, I don't know if it is everyone but it is most.

There is one last issue that prevents MSFT from fixing it. Say they find an issue with a device. They have to do a lot of testing to make sure it doesn't create a security risk, break even more drivers that were made correctly or interfere with software.

There are people that work for Microsoft and their sole job is to go to the manufactures and work with their staff then report to Microsoft and relay back the info the engineers find to the manufactures so they can fix it faster.

If you have some networking issues in the future this site gets updated with the most common solutions that are currently breaking peoples connections

http://www.vindamedia.com/windows/help/windows-8-general-errors

http://www.vindamedia.com/windows/help/troubleshooting-your-network

Let me know if you have a question I would be glad to expand. I didn't want to get to in depth and make it confusing (hope I didn't)

So, knowing that this is a HUGE issue for thousands of users, why doesn't Microsoft put out notices to the device makers who can't seem to get their drivers to function with 8 and 8.1, telling them where the problem lies and what they need to do? It's bad form to put something out that major manufacturers can't create drivers to work with.

To any one who is reading. Windows makes a SDK and WDF and the device makers use it to make their drivers. Microsoft's job is to make sure the SDk doesn't have bugs or WDF. But if the bug is in the hardware or the driver the hardware maker built then it is their fault. Microsoft gets millions of pieces of data and updates form manufactures. If there is an issue they will address it if it is the WDF or SDK but not if it is the driver.

Most manufactures like to say it is a Windows issue because that takes the pressure off them and most people accept it as true thinking that a lot of windows computers have issues which is a given because there are 100s of millions of windows devices people use with millions of 3rd party hardware and software that are broken but Windows will fail. Looking at BSOD and bugchecks we know that windows isn't usually the issue and Virus software, viruses, hardware and drivers are the main issue even though that the bugcheck will appear to fails on a windows system process the windows process isn't what failed it got a bad instruction or noticed something wrong earlier in the stack and had to shut down to protect the system

Have you tried updating the router firmware? Usually when an older driver works it is because it doesn't use a newer protocol that the router isn't set up for? Similar to this http://support.microsoft.com/kb/2749073/en-us

It could also be that a Bluetooth device uses the same band and with the older driver it isn't using the Wirelless N