Surface Pro 3 WiFi

Surface Pro 3 Purchased in USA – Wireless May not Work Outside North America


I’ve been involved in a couple of threads on Microsoft communities like which highlight and issue that Microsoft doesn’t seem to care about.

While the majority if wireless routers and AP’s in Europe and Asia by default are set at channels 1-11 for the 2,4 GHz band, additional higher power channels 12-14 are optionally available. Many private organizations and companies utilize this. I don’t know the situation with public WiFi abroad, but I suspect the configuration may vary, depending on the provider. I’m certainly hearing from afflicted users like this one from Germany:


germany 802.11d



If you read the above referenced thread, you can draw your own conclusions, but as *I* read the available information, Microsoft owes folks a localized optional driver.

I’d love to hear from afflicted users on Twitter. @barbbowman

Microsoft, Your Users are Crying Louder for Surface Pro 3 WiFi Fixes


Reading Microsoft Community Surface Pro 3 Forums has become even more painful than yesterday. Today, a marketing type statement post from a Forum Moderator went up stating:


Hello all

We have received a limited number of inquiries related to Wi-Fi connectivity on Surface Pro 3, which we are actively investigating. We are committed to providing the best customer experience possible and are working to quickly resolve.


Gee whiz. How about moving beyond the marketing-speak and  provide a real “status”.


sp3 wifi 9.4


After 60 days, there should be hard information and a status available of individual issues and more timing information on fixes. Not boilerplate:

wifi marketing answer

Microsoft, Your Users are Crying for Surface Pro 3 WiFi Fixes


Reading the Microsoft Community Surface Pro 3 Forums has become unbearably painful. There are three major threads and several others with large numbers of customers begging for relief from persistent WiFi issues. The numbers are growing. A capture from this morning shows:

sp3 wifi bugs

You can be sure that the number of people lurking and not posting is far larger than the number of replies.

Surface Phone and Chat Support has had people refreshing and resetting (which won’t resolve these issues) and they’ve replaced hardware. Some folks have replaced their hardware 4 times.

The official Forum support folks posted a vague statement a while back that “fixes would be available in the September timeframe’. It’s hard to tell if they even have a handle on the various issues since their participation has been abysmal. Refresh/reset is not participation.

Some of the worst issues:

1. Persistent slow WiFi

2. Adapters for WiFi/BT go missing after wake from sleep

3. Connection drops during use and goes Limited

4. Machine goes to sleep at home, travel elsewhere and on wake, SP3 doesn’t realize environemnt has changed and reports old SSIDs and does not see current SSIDs.

There are reports of some routers that the Marvell WiFi in the SP3 won’t connect to at all. If the same SSID name is used for 2.4 and 5GHz, the Marvell WiFi never sees the 5GHz.

Microsoft, you need to ENGAGE with your users and give them a status. The forum has turned ugly. I’m done trying to support your users on this issue. I know they don’t mean to take out their aggravation on me, but I’m not willing to get beat up.

Some Theories on WiFi Issues with Surface Pro 3


I’ve been reading about issues with WiFi connectivity in the Microsoft Community Forums (and trying to help folks with these problems), primarily in two long threads:


I have some theories, but am having trouble extracting answers to my questions in these threads because I’m asking afflicted users to make changes to their router configurations WHICH THEY SHOULD NOT HAVE TO DO UNDER NORMAL CIRCUMSTANCES. I’ve developed a couple of theories about some of the connectivity issues.


1. SLOW WIFI: Some routers (Apple has been doing this for years) ship with both the 2.4 and 5 GHz channels set to the same SSID (name). Other vendors have started doing this, some by default, others let you specify this optionally. It’s marketed as an “Smart Connect” type config where the “best” channel is selected by the client/router automatically. I asked a couple of users in the forum about their config and learned that they were using the same SSID. I asked them to make a change and specify unique SSIDs and attach to 5GHz. They’ve reported their problem has disappeared.

Over the weekend, I experimented with my newest Netgear Router, the newly released R8000. This router has TWO 5GHz radios that support the newest 802.11AC speeds. Netgear optionally offers the “Smart” connect where you can enable the same SSID name.


You have no control which radio you connect to when this is enabled.

If you enable this kind if smart connect on routers covering both the 2.4 and 5GHz bands on certain routers, apparently you will always connect to the 2.4GHz SSID if you are using a Surface Pro 3.

For folks with 2.4GHz 802.11n routers with no 5GHz, your speeds will be slower than if you had a dual band router. There’s just no getting around this.


2. LIMITED CONNECTIVITY WHEN COMING OUT OF INSTANT GO ‘SLEEP’: Most routers ship with channels set to auto select so that the user doesn’t have to figure out what channel has the least interference/usage. I’ve always changed this to specific channels here and have had no issues. My theory here is that while the SP3 is in InstantGo sleep mode, the channel has changed and the Marvell adapter can’t find it. Similarly, if the initial connection is made, while using the SP3, if the channel changes, the same “can’t find new channel” situation occurs. I’ve been asking people to make changes in their settings to test this. Again, I know this should not be necessary. But it would seem to be a great diagnostic.

Blue Screen Crash on Surface Pro 3 with wificlass.sys


Microsoft Communities users are reporting a blue screen crash in wificlass.sys in a growing thread:


As yet, there is no official participation from office Surface support.

I’m wondering how many people are afflicted with this issue. If you are experiencing this, please post in the thread above and also tweet @barbbowman.

Windows 10 users: Read this blog with my PWA (Progressive Web App) from the Windows Store

Read this blog with my Windows 8 App

Get the App