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
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
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.
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
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.
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.
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.
2nd or 3rd time removing Marvell device in Device Manager may be the charm, for me at least.
After reading a string of posts where removing the device driver, rebooting, and rescanning for hardware changes fixed things up for a number of people, I decided to retry and things have been working pretty smoothly since then.
First time around, I just deleted the Marvell device from Network Adapters in Device Manager and I thought that should be equivalent to what Martin recommends as I got a Confirm Device Uninstall pop-up and I left the Delete Device Driver Software From This Device UNCHECKED. Perhaps my fatal error was not shutting down and just restarting before the rescan? That was back in April shortly after the Wi-Fi firmware update.
Just a few days ago I picked Properties for the Marvell device by mouse right click. Went to Driver tab, picked Uninstall (Advanced) at bottom, left Delete Device Driver Software From This Device UNCHECKED. Shut down my Surface RT and waited 20-30 secs before reboot. Then rescanned computer for hardware changes in Device Manager using Action menu (Marvell was already reinstalled, anyway(.
I also went into my Wi-Fi settings and "forgot" any extra connection settings to my router that were hanging around. Initially in setting up my Surface RT, being fairly ignorant of Wi-Fi and Win8, I had followed Microsoft's security recommendation of NOT checking the connection property "Connect Even If Network Is Not Broadcasting Its Name (SSID)" not realizing by leaving this box unchecked, I'd be requiring a manual connection if my router does not broadcast its SSID. Since I use WPA2-Psk and MAC address filtering, I decided it's no big deal to connect automatically, and I deleted all the leftover connection property settings from previous manual connections (usually had at least 1 or 2 extra floating around at any one time).
Since doing the above, I've had no lost connections with Windows Store, no hiccups waiting for page requests from busy forum web sites. Perhaps all of this is not really related to the dropped Wi-Fi connection issue but since retrying the Marvell driver uninstall/reinstall, things have been going a LOT smoother for me connecting and browsing. So easy to do that can't hurt for anyone having problems to try again with a driver uninstall/reinstall.