Surface Pro 3 - Windows 10 - WiFi (slow or limited connectivity )

Anonymous
2015-07-30T14:16:39+00:00

Have a Surface Pro 3 that worked fine till I updated to Win10.  Now the wireless connection seems to randomly go to a "limited connectivity" mode.  Fortunately was purchased from Costco a coupe of weeks ago so it is going back there if we can't get this figured out by Sunday.

The Surface Pro3 is a flagship device - why in the world would you subject your customers to have to resort to looking for help in forums like this?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-11-13T10:20:54+00:00

Everyone,

Build 10586 - the November Windows 10 update - was released yesterday, and it contains a newer Marvell wireless driver 15.68.9032.47 - people are reporting that this greatly improves wireless connectivity. Please download the large update, and if you used the registry hack, reverse it as follows:

Press Windows button. Search for regedit. Open it

  1. Navigate to the following path:

 HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\mrvlpcie8897

  1. Find the item labeled “TXAMSDU”. Double tap and modify the value from 0 to 1
  2. Restart the machine

Then test your connectivity, and post results.

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-11-13T10:44:26+00:00

Fred,

the November Windows 10 update to build 10586 has new wireless drivers. Can you download and install the update (it should be offered via WU) and let us know if this changes your connectivity?

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2015-08-05T18:12:39+00:00

Penny,

These kinds of issues WERE present on 8.1 for months but they mostly all cleared after several driver updates.

And that particular router is not one known to exhibit slow wifi. I'm suggesting you trade it because it is SP new and you can now get one with 10 pre-installed and not have to go through an upgrade AND because you have this issue. Getting it swapped will rule out a hardware issue and would be a step forward.

This is what *I* would do if in this situation.

For what it's worth - Microsoft needs to fix the driver and any underlying Win 10 OS issues. It took them 9 months to get a "good" Windows 8.1 wireless driver. For now, consider an external USB wireless adapter. I carry around a http://www.amazon.com/Edimax-EW-7811UTC-Dual-Band-Connectivity-Exceeding/dp/B00FW6T36Y

Was this answer helpful?

0 comments No comments

417 additional answers

Sort by: Newest
  1. Anonymous
    2015-10-23T19:10:11+00:00

    using the same name for both bands has been problematic off and on since the launch of the SP3. I know that the Apple routers use the same name by default. You might want to try the .151 driver. You can search softpedia for the Surface Marvell .151 driver

    • folks have found it there and reported better performance.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-10-23T16:54:54+00:00

    Picked up my brand new Surface Pro 3 yesterday, and connected it to my Apple AirPort Extreme. I thought something was wrong with the Surface. I went to speedtest.net and was getting 6-8 Mbps down (I get 120 Mbps down on wired devices), so I would expect a wireless device would yield 70-80 Mbps minimum.

    My AirPort is set up with the SSID FBISurveillanceVan1 and the same name is used for both the 2.4 and 5 GHz bands. My guess is that the Surface uses the 5 GHz band by default.

    I also have a Comcast XFINITY gateway, which also has its wireless enabled. I have a 5 GHz SSID named S.H.I.E.L.D. and a 2.4 GHz SSID named HYDRA. I connected to the 5 GHz first, and performance was still dreadful. I switched over to the 2.4 GHz and boom! Blazing saddles. My driver version is 15.68.3091.193, dated 6/4/2015. Based on several posts in this thread, people have had good luck with the .193 driver. I'm not feeling the love, though.

    Guess I'll stick with 2.4 until Marvell releases an update.

    Was this answer helpful?

    0 comments No comments