wifi issues

Anonymous
2012-10-28T18:24:01+00:00

I had an issue this morning where Surface couldn't find any wifi networks (when 5 were in the area) and it was connected the previous night. I solved this issue by searching windows rt for Network. Open Network Connections, find the wifi device and then disable this connection. After a minute - I re-enabled the connection and then it started to work.

Just wanted to share my experience if anyone runs into the same issue. Thanks!

Nate

Surface | Other

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
2013-02-19T00:22:07+00:00

Greetings all,

We are working on a solution for the Limited WiFi issue. Please refer to the following thread for potential workarounds while we are working on the WiFi issue:

http://answers.microsoft.com/thread/c593dff8-61b3-496c-b8f2-f9deb3e4b35e

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2013-07-26T22:53:04+00:00

Greetings everyone,

Thank you for your continued interest, feedback and assistance in investigating the Limited WiFi issue on the Surface.

Not all limited connectivity scenarios have solutions that can be controlled by the Wi-Fi drivers of a given device. Limited connectivity scenarios result from a complex interaction of device Wi-Fi drivers, access point firmware, access point configuration, and other environmental factors.

If following the steps in the provided links below fail to resolve your Wi-Fi issue I encourage you to create a new thread.

Connect to a wireless network

Can’t connect to a wireless network?

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2013-08-20T01:28:23+00:00

You will most likely have to do a REFRESH.  Most of us has had to do that.  For some reason or another the driver gets corrupted.  You may also do a trick that most others have done as well as long as you don't have the 8.1 Preview of Windows 8 RT installed.

That trick is to open the Control Panel and go do Device Manager.  Look for the Marvel WiFi adapter and "Uninstall" the driver but "DO NOT DELETE IT".  When finished, reboot the tablet and it should connect.

Try that trick first and if it doesn't work, then do a REFRESH.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2013-05-26T21:44:35+00:00

Hello priscillaodendaal,

Sorry to hear you are having problems connecting to WiFi.

You should be able to connect to WiFi. Are you getting any errors when trying to connect? Are you able to see the networks and not connect to them?

Let us know.

Best regards.

Was this answer helpful?

0 comments No comments

682 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-03-09T19:44:54+00:00

    for now your only recourse is to

    a) downgrade all your N routers to G and see if that helps

    b) buy something like this: AirLink101 AWLL5088 Wireless N 150 Ultra Mini USB Adapter (search for it on Amazon)

    I chose option b and it looks like we will be stuck with it a good long while.  I tried the built-in wifi after the latest patch tuesday and the problem continues to persist...microsoft support will only say "we're working on a fix, no ETA", and since the problem has existed since Oct 2012...well you can see where this is going

    I am telling everyone considering buying a Surface that 802.11n is totally unreliable with this device and to decide accordingly

    also beware of people in this thread who say it is fixed, the problem is related to throughput on the nic, so it is possible to get 1-3 days of light web browsing before the problem resurfaces...I have yet to see anyone who has pushed a couple of gigs through an N router and not seen the problem hit the Surface

    microsoft has not even pushed any networking or driver updates so it makes utterly no sense to say that a recent update has fixed it, but many people don't know how to troubleshoot and leap to conclusions prematurely

    Was this answer helpful?

    0 comments No comments