Latest Surface update bricks the Wi-Fi on some devices

by Vlad Turiceanu
Vlad Turiceanu
Vlad Turiceanu
Passionate about technology, Windows, and everything that has a power button, he spent most of his time developing new skills and learning more about the tech world. Coming... read more
Affiliate Disclosure
Surface driver update bricks the Wi-Fi on many devices
To fix various PC problems, we recommend DriverFix:
This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:

  1. Download DriverFix (verified download file).
  2. Click Start Scan to find all problematic drivers.
  3. Click Update Drivers to get new versions and avoid system malfunctionings.
  • DriverFix has been downloaded by 0 readers this month.

Microsoft recently released some new driver updates for their Surface line-up to improve Bluetooth and Wi-Fi connectivity.

Microsoft’s driver updates for Surface devices are faulty

The update rolled out on the Surface Pro, Surface Book, and the first-generation Surface Laptop. But it seems like the drivers that came with the latest firmware update have some big problems.

A lot of Windows 10 users are reporting that Marvell Semiconductor, Inc. – Net – 15.68.17013.110 driver, intended to improve Wi-Fi connectivity, is affecting their Surface devices.

Here’s what some of them are saying:

Marvell Semiconductor, Inc. – Net – 15.68.17013.110 WiFi driver breaks 5GHz connection
I’ve been wondering why my surface book was the only device I had that couldn’t get wifi
Had the same issue. It also made my bluetooth mouse very jittery

Surface users who updated can’t connect to 5Ghz Wi-Fi bands

According to user reports, after installing the Marvell driver, they were unable to connect to 5Ghz Wi-Fi bands. This is a particularly odd problem, as the 2.4Ghz band works just fine for them.

Surface owners confirm that when they try to connect to a 5Ghz band, they get the “Unable to connect to this network” error message.

It’s worth noting that the update changelog didn’t confirm any known issues, so Microsoft isn’t aware of the problem.

If you’re in the same boat, the only solution for now is to rollback to the previous network adapter driver version using Device Manager.

Requests for a solution have been sent to Microsoft through the Feedback Hub, but there isn’t an ETA for an official resolution.