Windows 10 Insider Preview build 14915 kills WiFi for some users

Reading time icon 2 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Microsoft released Windows 10 Insider Preview build 14915 this week to the Fast Ring, bringing fixes to a number of issues that were introduced in the previous Insider build. However, as sometimes happens with beta programs, a new issue has been introduced that affects a limited but meaningful number of users.

Microsoft acknowledges the issue at the Answers community:

Hello Windows Insiders,
After the release of build 14915 to to the Fast ring for PC yesterday, a Wi-Fi bug has been discovered that is impacting a subset of users. Please review the following:

  • Surface Pro 1
  • Surface Pro 2
  • Wi-Fi adapters using the Marvell driver
  • (There may be other similar drivers affected, research is ongoing)

You may review in Device Manager to see if your PC is affected. You will see an icon on your Wi-Fi adapter similar to this:


The percentage of users impacted is limited, but for those affected, all Wi-Fi functionality is lost and there is no temporary fix to restore Wi-Fi on this build given the nature of the bug. Affected users will need to use a wired connection if available or roll back to the previous OS version on their device to bypass this issue.

Our Engineering teams have quickly completed a root cause analysis of the issue and are working to get the fix checked-in to make it available in our next flight.

Thank you as always for the feedback that has been provided and for the quick efforts to share this issue with us.

There’s some evidence that this issue is affecting a number of other machines, including this writer’s homebuilt desktop using a Netgear A6210 802.11ac adapter. This Answers thread provides a discussion of various unsuccessful attempts to resolve the issue.

We’ll be looking forward to the next Insider build, where this issue will hopefully be rectified. Those without a wired Ethernet connection will likely need to roll back to the previous build and then update to the next build to get around this issue. Let us know in the comments if you’re suffering from the bug, and what system you’re running.