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
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
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
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

417 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-09-07T00:09:02+00:00

    I've been watching the progress on this issue. I had almost the same problems with my Pro 3.

    I narrowed it down to the ARC Mouse I had connected through Bluetooth. As soon as I disconnected the Bluetooth I suddenly had complete and fast wireless. I have a router with 2.4 and 5.0G. I am using 5G exclusively with no further internet problems.

    The aggravation of course is that I paid a lot for that mouse and not being able to use it or get any Microsoft solution is not satisfactory.

    Fact is, it's only using MS OS (Win10) that I even stick with this Surface. My iPad is totally trouble free. I've had so many problems with this Surface I've lost count.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-09-06T17:22:31+00:00

    I'm wondering if the symptom may be a sign that Homegroup connectivity ICS is being used?  FWIW one of the strange symptoms I had last night (part of the hang scenario I mentioned) is that when I asked my Surface RT to troubleshoot the Homegroup, everything on the Surface Pro sprang temporarily back to life.  Another reason why I'm not ready to suspect such problem symptoms are due simply to networking.  There is a whole lot more involved in this convoluted stuff and the troubleshooters are interfering (probably for "security" reasons) more than helping.  E.g. the fact that I was able to use my Surface RT to connect with the "hung" Surface Pro through the wireless connectivity (bridge not router--router is in the modem) puts the lie to the troubleshooter's hypothesis that all I needed to do to make everything work again was power off all my comm hardware for at least 10 seconds and then wait for it to become active again.  This is why we need some objective facts (not guesses, especially ones which ignore security considerations) to understand what is really going on.

    Was this answer helpful?

    0 comments