Windows 8 pro and 8.1 pro WiFi connection issues

Question

I hope to start a meaningful dialogue with Microsoft about the WiFi issues that Windows 8 and 8.1 have.
I've been deploying Windows 8 and 8.1 since the Surface Pro was released.  Since then we've deployed about 50-75 Surface Pro, Surface Pro 2, Dell Latitude 7000 series, Lenovo Yoga 13 IdeaPad and Lenovo Yoga Thinkpad devices.  Some have Windows
8 pro, some have been upgraded to 8.1 Pro, and some were purchased with native 8.1 Pro builds on them.  All of these devices have difficulty with wireless in one form or another.  We were able to reduce some of the problems (not eliminate) on our
corporate LAN over the last year by turning off Windows' ability to turn off the wireless adapter to save power, or turning off some of the offload or chimney or other advanced capabilities of the adapters.  Problems were still present, but less so. 
Many of our users were able to be on the wired LAN, so the issues were somewhat glossed over. 
We were finally able to fix our Wireless LAN issue (we believe everything is working as expected after 2 weeks of testing and observation) by updating the controller and AP firmware for our Aruba wireless infrastructure (we have one controller and 11 ap's
across 5 well connected sites).  This is great- sort of...
The problem is that while it's now very obvious that in our case, updating the firmware on our corporate WiFi is able to get the various 8 and 8.1 devices working on our LAN, this is not a true fix as it does not address our mobile and wireless capabilities
while:
1. traveling
2. working at a partner's or customer's location and connecting to their WiFi
3. Working from Home
4. Etc.
We obviously can't update everyone's AP/wireless router firmware.  The solution, by necessity, must reside on the Windows 8/8.1 machine and it's inability to reliably connect and stay connected to existing Wifi networks.   I want
to know the current state and thinking that Microsoft has regarding this persistent issue (searching for "Windows 8.1 wifi" in the "Windows 8.1 IT pro" forums on TechNet returned 4000+ results).  Ignoring or not addressing this
problem head on is a huge mistake.  Let us know the root cause (SOMETHING has changed in the Network/IP stack) and a solution to work around the cause. 
I'll conclude like this: I KNOW that some Wifi issues can be resolved with firmware updates to WiFi routers/APs.  I KNOW that some WiFi issues can be resolved with driver updates or, in some cases, downgrades.  I KNOW some Wifi issues can be resolved
by uninstalling Intel ProSET, or getting manufacturer direct drivers.  I KNOW some issues can be resolved by turning off Windows' ability to turn off the adapter when "not in use" to save power.  I KNOW some owner's of Windows 8/8.1
machines have downgraded to Windows 7 or XP or abandoned Microsoft altogether and move to Linux or Mac.  The ONLY common problem across all of these solutions, is Windows 8/8.1.  Therein MUST lie the ultimate answer.
DLovitt

Answer 1

I hope to start a meaningful dialogue with Microsoft about the WiFi issues that Windows 8 and 8.1 have.
I've been deploying Windows 8 and 8.1 since the Surface Pro was released.  Since then we've deployed about 50-75 Surface Pro, Surface Pro 2, Dell Latitude 7000 series, Lenovo Yoga 13 IdeaPad and Lenovo Yoga Thinkpad devices.  Some have Windows
8 pro, some have been upgraded to 8.1 Pro, and some were purchased with native 8.1 Pro builds on them.  All of these devices have difficulty with wireless in one form or another.  We were able to reduce some of the problems (not eliminate) on our
corporate LAN over the last year by turning off Windows' ability to turn off the wireless adapter to save power, or turning off some of the offload or chimney or other advanced capabilities of the adapters.  Problems were still present, but less so. 
Many of our users were able to be on the wired LAN, so the issues were somewhat glossed over. 
We were finally able to fix our Wireless LAN issue (we believe everything is working as expected after 2 weeks of testing and observation) by updating the controller and AP firmware for our Aruba wireless infrastructure (we have one controller and 11 ap's
across 5 well connected sites).  This is great- sort of...
The problem is that while it's now very obvious that in our case, updating the firmware on our corporate WiFi is able to get the various 8 and 8.1 devices working on our LAN, this is not a true fix as it does not address our mobile and wireless capabilities
while:
1. traveling
2. working at a partner's or customer's location and connecting to their WiFi
3. Working from Home
4. Etc.
We obviously can't update everyone's AP/wireless router firmware.  The solution, by necessity, must reside on the Windows 8/8.1 machine and it's inability to reliably connect and stay connected to existing Wifi networks.   I want
to know the current state and thinking that Microsoft has regarding this persistent issue (searching for "Windows 8.1 wifi" in the "Windows 8.1 IT pro" forums on TechNet returned 4000+ results).  Ignoring or not addressing this problem head on is a huge
mistake.  Let us know the root cause (SOMETHING has changed in the Network/IP stack) and a solution to work around the cause. 
I'll conclude like this: I KNOW that some Wifi issues can be resolved with firmware updates to WiFi routers/APs.  I KNOW that some WiFi issues can be resolved with driver updates or, in some cases, downgrades.  I KNOW some Wifi issues can be resolved
by uninstalling Intel ProSET, or getting manufacturer direct drivers.  I KNOW some issues can be resolved by turning off Windows' ability to turn off the adapter when "not in use" to save power.  I KNOW some owner's of Windows 8/8.1 machines
have downgraded to Windows 7 or XP or abandoned Microsoft altogether and move to Linux or Mac.  The ONLY common problem across all of these solutions, is Windows 8/8.1.  Therein MUST lie the ultimate answer.
DLovitt
THIS.
I have been going through the same efforts as DLovitt with no joy.  I have ruled out all variables which leads directly to something with Win 8/8.1 being the problem.  Very frustrating that I cannot find a fix anywhere.
Subscribing to this thread in the hopes an answer is forthcoming.