Can't connect to WiFi Surface Pro 2.

Anonymous
2014-06-25T12:46:44+00:00

Iexperienced this problem this morning on my Surface Pro 2.  After being connected at a coffee shop, shutting down and rebooting at work I tried to connect to the wireless connection at work and am also getting the "no connection available".  I get the same network icon and red X.

When I troubleshoot I get "The Marvell AVASTAR Wireless Composite Device adapter is experiencing driver- or hardware-related problems" 

Any help greatly appreciated.

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.

0 comments No comments
Answer accepted by question author
Anonymous
2014-08-06T16:55:36+00:00

Hi SimonNissenbaum,

Thank you for contacting the Microsoft Community! I'm sorry to hear you are having connectivity issues with your Surface Pro 2. We appreciate you providing the steps that you have taken so far. We will be glad to help you find a viable solution.

First, we kindly ask you to double check that all and latest Windows updates are installed. Below you can find instructions on how to check for updates:

Also, please make sure you have followed the instructions presented by Zack_T  above, and the troubleshooting steps presented in the support article below:

Additionally, please try uninstalling and reinstalling the wireless driver:

  1. Go to the Desktop
  2. Swipe from the right
  3. Touch Settings
  4. Touch Control Panel
  5. Touch Device Manager
  6. Open the Network Adapters
  7. Right click on the Marvell Avastar 350N Wireless Network Controller
  8. Touch Uninstall
  9. *****Do not check the box*****
  10. Click on OK
  11. Restart your Surface.
  12. Once your Surface restarts, the Marvell driver will be reinstalled.

If none of the steps above work, and the issue persists, you might want to consider a Refresh:

We hope these solutions prove useful!

Keep us posted, we are always here to help!

Cheers,

Was this answer helpful?

50+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-01-14T04:09:39+00:00

Hi SimonNissenbaum,

Thank you for contacting the Microsoft Community! I'm sorry to hear you are having connectivity issues with your Surface Pro 2. We appreciate you providing the steps that you have taken so far. We will be glad to help you find a viable solution.

First, we kindly ask you to double check that all and latest Windows updates are installed. Below you can find instructions on how to check for updates:

Also, please make sure you have followed the instructions presented by Zack_T  above, and the troubleshooting steps presented in the support article below:

Additionally, please try uninstalling and reinstalling the wireless driver:

  1. Go to the Desktop
  2. Swipe from the right
  3. Touch Settings
  4. Touch Control Panel
  5. Touch Device Manager
  6. Open the Network Adapters
  7. Right click on the Marvell Avastar 350N Wireless Network Controller
  8. Touch Uninstall
  9. *****Do not check the box*****
  10. Click on OK
  11. Restart your Surface.
  12. Once your Surface restarts, the Marvell driver will be reinstalled.

If none of the steps above work, and the issue persists, you might want to consider a Refresh:

We hope these solutions prove useful!

Keep us posted, we are always here to help!

Cheers,

Uninstalling the driver worked!!! It reinstalled it after restart.

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2014-06-24T21:33:36+00:00

I re booted and it started working again, so I did a Windows update and so far so good.

Was this answer helpful?

0 comments No comments

54 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-04-12T11:38:48+00:00

    It is tough to say when it started. I first noticed it when I bought the dock. Of course, this is also when I started using my Surface Pro 2 as my primary machine. The issue occurred again this morning. Looking at device manager, everything looks fine (see below image.) As for toggling Airplane Mode, that also has no impact. It was a little tricky to do since when I click the network bars in the system tray to access Airplane Mode, nothing appears. I had to use the search feature to get to airplane mode.

    Thanks for the help, let me know if there is any more information that would help diagnose this issue.

    :: Tom

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-04-12T08:12:04+00:00

    I have the same problem with the refurbished Surface Pro I just received today. It's been a nightmare trying to deal with it. 

    I've restarted 10 times now and the wifi works every other time just like btnheazy03.  It seems like the restart command changes it from working to non-working. If I do repeated "shut downs" while it's already working, it will always work when I turn it back on. If I do a restart, it'll stop working and it will still not work after any subsequent shutdown and turn-ons (so yes it has something to do with restarts and not shut downs).

    When I go into the network adapter settings, the wifi adapter is "disabled" and I cannot re-enable it. I noticed than when it works, the wifi card appears as "Marvell AVASTAR 350N Wireless Network Controller" under network adapters in Device Manager. There's also some bluetooth devices listed under network adapters. But when it looses connectivity, all I see under network adapters is "Marvell AVASTAR Wireless Composite."

    I was using the latest driver. I have also tried rolling back to the previous driver and uninstalled the driver all together. It seems to reinstall the driver when I restart but it doesn't fix the problem. 

    I don't know if it was the latest firmware or network driver that caused the problem since I just got my device today and updated. But as I said, rolling back the driver doesn't help.

    Please help,

    Thanks

    Was this answer helpful?

    0 comments No comments