[German]Microsoft offers a firmware update for various Surface devices. If this is installed, some users will experience problems with the stability of the WiFi connection. Here is some information about this topic.
A few days ago I gave a short note about the Surface firmware updates in the blog post Firmware Updates for Surfaces. Neowin has summarized information about these firmware updates here.
Reports about WiFi issues
It looks like some users are experiencing issues with the WLAN connection caused by the firmware update of the Marvell Semiconductor, Inc. – Net – 15.68.17013.110 driver for the Wi-Fi connection. For the first time I became aware of this topic through a tweet by Woody Leonhard.
Many reports of failing WiFi after installing the latest Surface drivers. "Marvell Semiconductor, Inc. – Net – 15.68.17013.110" seems to blame, on various Surface devices. Thx @barbbowman https://t.co/w6tgUC5iDJ
— Woody Leonhard (@AskWoody) August 5, 2019
Marvell Semiconductor, Inc. – Net – 15.68.17013.110 WiFi driver breaks 5GHz connection on the Surface Book (1st Gen i5 with dGPU 256 GB)
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?
Within the MS Answers forum thread other users are confirming the issues with their Surface Books. A poster also names a Surface Pro 6 that can no longer connect to a specific Access Point (AP). At ComputerWorld Woody Leonhard writes, different surface models are affected. According to this Microsoft Answers forum thread, users andipeppa were able to repair it again by rolling it back to the WiFi adapter driver 15.68.9127.58. Martin Geuß has discussed this within this German article on Dr. Windows and also describes the steps how to get back to the previous driver.
Cookies helps to fund this blog: Cookie settings