Marvell Semiconductor, Inc. – Net – 15.68.17013.110 WiFi driver breaks 5GHz connection on the Surface Book (1st Gen i5 with dGPU 256 GB)

Anonymous
2019-08-04T02:22:56+00:00

The title says it all, I updated the wifi driver to "Marvell Semiconductor, Inc. – Net – 15.68.17013.110", and after that update, I can't connect to a 5GHz wifi connection, I can only connect to 2.4 GHz. when i try to connect to the 5GHz, it says: "Unable to connect to this network". Uninstalling the wifi driver, and restarting the device did help me get the 5GHz connection back to my Surface book, but when i decided to try to install the same driver again, and try to connect to 5GHz again, the same "Unable to connect to this network" appears. Does anyone have this issue?

Surface | Surface Book | Network

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
2019-09-27T21:26:13+00:00

Thank you for reporting the issue. A fix is now available through Windows Update.

For more information, please visit our Surface Update History page.

Eddy.

Updated: 11/18/2019

Was this answer helpful?

6 people found this answer helpful.
0 comments No comments

131 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-04-26T15:06:37+00:00

    Well to be honest. At our company we stopped buying Surface Products. We got several of those Access Points and won‘t change our infrastructure. HP 1030 and 1013 are working without problems.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-04-17T10:17:54+00:00

    My network card and bluetooth continue to crash within moments of Windows starting up even after the last update.  

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-04-16T07:15:42+00:00

    yep, but it is the same driver in your sp5, thats why both where not working in the past ..

    anyway .. i got it working and it is now back in business bc reinstalling was the key .. ThumbUp

    Was this answer helpful?

    0 comments No comments