Surface Pro 3 Slow WiFi - 72Mbps Max (driver)

Hello all,

As many of you are aware, we released a Surface Update on September 9^th^ that makes improvements to Wi-Fi performance to address specific situations that some of our customers are experiencing. 

The September update included improvements to Wi-Fi speed by addressing the following:

• Reduced Wi-Fi speed on some access points after the Surface Pro 3 resumed from sleep
• Incorrect link speed reporting (incorrectly reporting a reduced speed) in the Windows Wi-Fi Status window
• Reduced speed while connected on the 2.4GHz band while the Bluetooth feature is enabled

We are also aware of the following additional scenarios that this update does not resolve:

• When both a 2.4 GHz network and a 5 GHz network share the same SSID, Surface Pro 3 may connect to the slower 2.4 GHz network if the signal strengths are similar when the connection is made.  We are currently working on an update to address this.

While we realize these updates should help the majority of customers, they may not resolve all instances of Wi-Fi behaviors described below. We also continuously review your feedback and are working on additional improvements.  We are planning to release additional updates in the future to further improve Wi-Fi performance.

If you are experiencing any of the scenarios below relating to Wi-Fi performance, we encourage you to provide feedback on these community threads:

No networks available after resuming from sleep -**http://answers.microsoft.com/thread/69c3cd0f-daac-44be-bec6-643d2e53f98a**

The September update improved Wi-Fi performance for Surface Pro 3’s that showed no Wi-Fi networks available after waking from sleep, requiring a reboot to make the network adapter available.

We are also aware of the following additional scenario that this update does not address:

• We are working on a future update to address the same scenario described above caused by the installation of Hyper-V, which was not addressed by the September 9^th^ update.  Additional information and workarounds for this topic can be found here:  Connected Standby is not available when the Hyper-V role is enabled.

Limited Wi-Fi -**http://answers.microsoft.com/thread/bd17691d-f00d-491c-a65e-fcd77a304b3a**

The September update included improvements that minimized instances of limited Wi-Fi by addressing the following:

• We further reduced instances of limited connectivity that would sometimes appear after resuming from sleep on some configurations of access points.

We are also aware of the following additional scenario that this update does not address:

We are working on a future update to ensure that, when Hyper-V is enabled, Wi-Fi reliably reconnects and/or does not become Limited after resuming from hibernate. Additional information and workarounds for this topic can be found here:  Connected Standby is not available when the Hyper-V role is enabled.

Details about the updates available for Surface Pro 3 can be found here:

http://www.microsoft.com/surface/support/install-update-activate/pro-3-update-history

Hello all,

As many of you are aware, we released a Surface Update on September 9^th^ that makes improvements to Wi-Fi performance to address specific situations that some of our customers are experiencing. 

The September update included improvements to Wi-Fi speed by addressing the following:

• Reduced Wi-Fi speed on some access points after the Surface Pro 3 resumed from sleep
• Incorrect link speed reporting (incorrectly reporting a reduced speed) in the Windows Wi-Fi Status window
• Reduced speed while connected on the 2.4GHz band while the Bluetooth feature is enabled

We are also aware of the following additional scenarios that this update does not resolve:

• When both a 2.4 GHz network and a 5 GHz network share the same SSID, Surface Pro 3 may connect to the slower 2.4 GHz network if the signal strengths are similar when the connection is made.  We are currently working on an update to address this.

While we realize these updates should help the majority of customers, they may not resolve all instances of Wi-Fi behaviors described below. We also continuously review your feedback and are working on additional improvements.  We are planning to release additional updates in the future to further improve Wi-Fi performance.

If you are experiencing any of the scenarios below relating to Wi-Fi performance, we encourage you to provide feedback on these community threads:

No networks available after resuming from sleep - **http://answers.microsoft.com/thread/69c3cd0f-daac-44be-bec6-643d2e53f98a**

The September update improved Wi-Fi performance for Surface Pro 3’s that showed no Wi-Fi networks available after waking from sleep, requiring a reboot to make the network adapter available.

We are also aware of the following additional scenario that this update does not address:

• We are working on a future update to address the same scenario described above caused by the installation of Hyper-V, which was not addressed by the September 9^th^ update.  Additional information and workarounds for this topic can be found here:  Connected Standby is not available when the Hyper-V role is enabled.

Limited Wi-Fi - **http://answers.microsoft.com/thread/bd17691d-f00d-491c-a65e-fcd77a304b3a**

The September update included improvements that minimized instances of limited Wi-Fi by addressing the following:

• We further reduced instances of limited connectivity that would sometimes appear after resuming from sleep on some configurations of access points.

We are also aware of the following additional scenario that this update does not address:

We are working on a future update to ensure that, when Hyper-V is enabled, Wi-Fi reliably reconnects and/or does not become Limited after resuming from hibernate. Additional information and workarounds for this topic can be found here:  Connected Standby is not available when the Hyper-V role is enabled.

Details about the updates available for Surface Pro 3 can be found here:

http://www.microsoft.com/surface/support/install-update-activate/pro-3-update-history

Awesome! Please keep us updated!

With this post at least we know that you are aware of the wifi issues and Microsoft is working on a fix.

It does not sound like any of your planned fixes will help me with the dreadful performance I am getting on my Surface Pro 3.  I can't figure out on this forum how to point to a preceding post, so I am copying it here.  Please let me know you are going to fix this.

The wifi performance on my I5 Surface Pro 3 is remains miserable after the update.

I use wifi mainly for file-sharing between my desktop and the Surface.  To demonstrate the dreadful performance, I transfer a 1GB folder containing three files.  Before the update this took 47 minutes 4 second.  After the update it took 38 minutes 2 seconds.  A great improvement you say? 

My son had a small Patriot 11n USB adapter sitting around, so I disabled the Surface internal adapter, plugged in the Patriot dongle, and transferred the same folder.  Before the update this took 1 minute 46 seconds, and after the update it took 1 minute 2 seconds.  My wife's old Dell laptop does this transfer in about 2 minutes.

After the update, the Surface internal adapter gives me still 3.8 Mbps (says Task Manager) and 355 KBps (says the copy progress dialog).  The Patriot dongle gives me 131 Mbps  (Task Manager) and 17 MBps (copy dialog).

The Surface internal adapter is 36 times slower than a cheap dongle.

Something is really really wrong here.  Note that the only thing that changed in the above tests is the wireless adapter on the Surface -- no other network changes.

This article claims that all WIFI issues has been resolved in Windows 10...

http://www.science20.com/quantum\_gravity/blog/24\_hours\_with\_windows\_10\_on\_a\_surface\_pro\_3-146256

You're experiencing the first issue Zack_T described. Very slow wifi performance using the 2.4GHz wireless band. I've personally given up on my Surface Pro 3. It's just not the reliable portable that I need for everyday work. I'm back to using my Sony VAIO Pro. I just don't understand why on earth did Microsoft get into the computer hardware game if they don't have the ability to resolve issues like this in a timely fashion. It would be more understandable if Microsoft were dealing with multiple products but there is only 1 Surface Pro 3 (with different CPU, memory and storage options). I'll keep monitoring these threads but I won't be a Surface Pro return customer in the future.