Surface Pro 3 not discovering wireless network adapter

Anonymous
2017-03-05T03:17:33+00:00

After turning on my SP3 from sleeping for a couple of hours, I noticed that it had disconnected from the WiFi. After further investigation, I found that the WiFi wasn't even available as an option, and neither was Bluetooth. It's as if the computer doesn't even have a wireless card anymore. After some googling, I opened the device manager and was going to do the usual "open the driver and reinstall it, then reboot". However, the Marvell AVASTAR wireless adapter, which should be in the list of network adapters, isn't there at all (even when I check show hidden devices). I've done a "refresh", and then a full reinstall of Windows, and it still isn't working. Is this a hardware failure? What is my course of action provided my warranty is expired?

***Post moved by the moderator to the appropriate forum category.***

Surface | Surface Pro | 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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Anonymous
    2017-03-05T10:43:27+00:00

    unfortunately this does seem to be hardware. your only option is an out of

    warranty exchange which has been running about $450US for a refurb. Contact

    support

    https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

    >>. Is this a hardware failure? What is my course of action provided my warranty

    is expired?

    0 comments No comments
  2. Anonymous
    2017-03-06T02:36:49+00:00

     Marvell AVASTAR wireless adapter, which should be in the list of network adapters, isn't there at all (even when I check show hidden devices).

    Except for the things that you have already tried, I saw that after an update--no network devices at all (on a Surface 2 Pro).   I concluded that it was an extreme reaction to the fact that I had not uninstalled the Hyper-V feature before applying the update.  Fortunately I had a fairly recent ISO to do an upgrade repair with and that got me going again.

    0 comments No comments
  3. Anonymous
    2017-03-06T10:51:07+00:00

    his shows an Ethernet Adapter.

    >>-no network devices at all (on a Surface 2 Pro).

    0 comments No comments
  4. Anonymous
    2017-03-06T13:15:49+00:00

    his shows an Ethernet Adapter.

    >>-no network devices at all (on a Surface 2 Pro).

    Maybe a real one?  In my case that was my Virtual switch. 

    But you're right.  I overlooked that detail.  Thanks.

    0 comments No comments
  5. Anonymous
    2017-03-06T13:43:43+00:00

    This morning i turned it back on and got a message saying i needed to reboot. It turns off, gives me a loader, and boots back up with all functionality restored.

    ???

    Needless to say im glad i don't have to spend cash on a trade in now.

    Edit: Welp, now I've got an error 45 status on the driver saying it's "not connected" to the computer. How can this be? Is some part in the machine loose or something? Again, this is a surface so I don't expect to be able to open it up and check inside.

    0 comments No comments