Surface Pro 3 WiFi
On January 15, 2015, Microsoft released a package of drivers to Windows Update that includes an updated Marvell WiFi driver for the Surface Pro 3. If you are one of the folks that has been trying to resolve issues of connecting to 2.4GHz instead of 5 GHz on your dual band router, this new driver includes settings to fine tune your connectivity preferences.
First, verify that you have Driver Version 15.68.3073.151:
1. Type the words device manager on the Start Screen/search and then open device manager.
2. Expand Network adapters
3. Right Click or tap and hold the Marvell AVASTAR Wireless-AC Network Controller and select Properties
4. Open the Driver tab and verify the version
Specify the band:
By default, the Band is set to Auto in the Value field. Access the dropdown list and select 5GHz if you want to connect to only the 5GHz band. Note that the 5GHz band is the one that provides the 802.11ac speeds. You can also specify 2.4GHz only.
Important: If you change locations and have specified a setting other than Auto, you should change the setting back to Auto to insure connectivity “on the road”. This is especially important when using public WiFi which normally uses the 2.4GHz band.
Some good news, Microsoft has announced upcoming updates to the Surface Pro 3 on TechNet. In particular, there are some WiFi updates that hopefully will fix some of the horrific issues that have plagued some customers since launch.
Note in particular:
Wireless Network Controller and Bluetooth driver update (v15.68.3066.135)
- Enables better throughput after waking from sleep and connecting to an 802.11AC network.
- Ensures Infra scan list is not empty while connected to a wireless display adapter.
- Resolves an issue connecting to Cisco 1242 access points.
- Ensures device reconnects properly to a hidden SSID using a 5Ghz DFS channel after waking from sleep.
- Adds customer-requested functionality to prefer 5Ghz connections when both a 2.4ghz and 5ghz connection are present with the same SSID.
Too bad Microsoft didn’t have the common sense to post this information in the Answers Community Forums where users are begging for relief.