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
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
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
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

54 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-08-20T18:11:13+00:00

    This happened to me this weekend, on 8/17.  I also have a Pro 2.  It happened very suddenly, in the middle of a session.  I was able to fix it by uninstalling the driver, as instructed here and elsewhere. 

    My question is, does that fix have anything to do with the driver I'm being offered by Windows Update today?  The modern app is calling it just "7/8/14", but the webpage gives this:

    "Wireless Network Controller (v 14.69.24054.176) enables functionality on wireless networks utilizing hidden SSIDs"

    I was offered an driver update by Windows Update and installed it only a few days before the wifi issue arose, you see, and now I'm wondering if it was the cause of the malfunction.  Is the "7/8/14" on offer now a fix for a known problem, or just a renewed attempt by the system to install a driver that might be buggy?  How do you let Microsoft know that their driver is causing malfunctions?

    It would be nice if Update were more specific in identifying driver updates.  The date labels don't change if there is a later fix.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-08-20T20:01:34+00:00

    Hi Mar,

    I just want to reiterate that in my case, step 4 is what may have caused the malfunction, and that step 5 is what fixed it.  I should add that i had to repeat step 5 and restart FIVE TIMES before it began working again.  i kept trying out of desperation, since i'm currently hundreds of miles from the nearest MS store. 

    Thanks!

    Was this answer helpful?

    0 comments