Some users suffering from Surface Wi-Fi glitch

Coming as a complete surprise to the technical world, Microsoft’s own Surface tablet hardware went on general sale on October 26th and has enjoyed, depending on what reports you read, modest degrees of success.

Following reported keyboard/touchpad splitting issues, another issue has been discovered with the hardware, involving Wi-Fi connectivity. The glitch causes users to lose connectivity to their Wi-Fi network(s), with the connection switching to ‘limited.’ The Microsoft Community page where users are reporting their issues is, at the time of writing, 18 pages long, with varying solutions being provided by users who have been able to work around the issue. These include:

  • Resetting the Wi-Fi connection
  • Setting the wireless network card from mixed to 11g only
  • Disabling the wireless card’s power management
  • Reinstalling the tablet’s wireless card

But the results of these fixes vary for each user. A Community moderator said over a week ago that Microsoft is aware of the issue and is currently working on a fix. In the meantime, they have recommended that any affected user sets their wireless router to 802.11g as a temporary fix.

While Patch Tuesday included a firmware update for the Surface RT which was supposed to have fixed the issue, results from users is again mixed. Some are still noticing a degraded service provided when connected to Wi-Fi networks and others appear to be having difficulty installing the update altogether.

Source: PC Mag | Image courtesy of Winsource

Report a problem with article
Previous Story

Rumor: Latest Xbox World issue reveals next Xbox details

Next Story

VMware, sort of, admit to being more expensive than Microsoft

34 Comments

View more comments

trip21 said,

Even the iPad 3 has it's "undocumented features" but they are all explained away as "the way it's meant to be" much like the purple haze from th iphone 5 camera or iphone 4 antenna!

EG http://www.zdnet.com/blog/hard...-the-bugs-to-be-fixed/19436


Looks like someone else needs to get their facts straigt... I can't stand people talking out of their asses!

The purple haze from iPhone 5 is actually not just from the iPhone 5, but comes out of almost 100% of cell phone cameras ever released. This is the result of shrunken optic systems.

Get a clue before spewing FUD!

tanjiajun_34 said,
What problem did the first iPad had? o.0

Here is just one example, direct from Apple's support. A problem with WiFi, where the fixes are similar to this problem with Surface.

http://support.apple.com/kb/TS3304

And my favorite fix for the iPad problem - decrease the brightness of the screen.

I thought Surface has MIMO technology that is suppose to be great. I can tell you my Surface signal isn't as strong as my iPad and WP when they are the same distance away from the AP.

I would love to know what these people at MS be thinking because I feel I can do better than them.

I would recommend an actual distance to lost signal or download speed test at the same locations. Apple has in the past reported higher signal then was actually achieved. I'm not saying this is the case here, just saying it is possible.

gullygod said,
I thought Surface has MIMO technology that is suppose to be great. I can tell you my Surface signal isn't as strong as my iPad and WP when they are the same distance away from the AP.

I would love to know what these people at MS be thinking because I feel I can do better than them.

I have a great signal, and great performance. Again, I must be lucky or the 64GB models have a better build quality because I haven't had ANY issues, or glitches including performance issues. I thought I would have to have a Pro, but really, I don't. I may get one just cuz, but I'm a truly impressed with my Surface. Just need more apps.

More problems with WART machines, not surprising now. A great way to launch a new product and a new OS! iPad did not have this many problems. Apple developed the iPad over many many years and Apple did not need to rush because there was no competition. Windows 8 and the WART machines are MS trying to catch up to Apples tablet success but MS are failing badly. Anyone who spends 5 minutes doing research before an intended WART purchase would be mad to go ahead and most people who pre ordered the WART must be very disappointed.

derekaw said,
Apple developed the iPad over many many years and Apple did not need to rush because there was no competition. Windows 8 and the WART machines are MS trying to catch up to Apples tablet success but MS are failing badly.

no. just no. Microsoft has been developing Surface for three years (http://www.neowin.net/news/mic...-on-surface-for-three-years), and they've been working on a similar project in their Research branch since 2008 (the Courier: http://en.wikipedia.org/wiki/Microsoft_Courier).

Not to mention that Microsoft has far more experience in tablets than apple, in fact, they first made Windows for Pen Computing in 1991 to work with Windows 3.1, and they (at least attempted to ) spearheaded a lot of the tablet industry when they launched Windows XP tablet edition.

derekaw said,
More problems with WART machines, not surprising now. A great way to launch a new product and a new OS! iPad did not have this many problems. Apple developed the iPad over many many years and Apple did not need to rush because there was no competition. Windows 8 and the WART machines are MS trying to catch up to Apples tablet success but MS are failing badly. Anyone who spends 5 minutes doing research before an intended WART purchase would be mad to go ahead and most people who pre ordered the WART must be very disappointed.

The article never mentioned Apple products, but since you did...

I have had 2 different iPad ZIT tablets, 3 iPhone HEMMOROID phones, and 2 iTouch BOIL players, all of them had wireless problems at one time or another. When I had my app on the Apple store for the iPhone HEMMOROID and iTouch BOIL, there was a bug in iOS 3 FESTERING WOUND that I had to contact Apple support for, where WiFi would not connect, they partially fixed it in a point release, but it never worked correctly. They fixed it in a later release, but on my iPad ZIT with iOS 6 FESTERING WOUND it seems to be back, where WiFi seems to take forever to reconnect.

Meanwhile, I have had my Surface disconnect once, and manually disconnecting and reconnecting fixed the problem. Reconnecting on my Surface is not as slow or unreliable like on my iPad 3 ZIT, which did not have the problem when it ran iOS 5 FESTERING WOUND.

nohone said,

The article never mentioned Apple products, but since you did...

I have had 2 different iPad ZIT tablets, 3 iPhone HEMMOROID phones, and 2 iTouch BOIL players, all of them had wireless problems at one time or another. When I had my app on the Apple store for the iPhone HEMMOROID and iTouch BOIL, there was a bug in iOS 3 FESTERING WOUND that I had to contact Apple support for, where WiFi would not connect, they partially fixed it in a point release, but it never worked correctly. They fixed it in a later release, but on my iPad ZIT with iOS 6 FESTERING WOUND it seems to be back, where WiFi seems to take forever to reconnect.

Meanwhile, I have had my Surface disconnect once, and manually disconnecting and reconnecting fixed the problem. Reconnecting on my Surface is not as slow or unreliable like on my iPad 3 ZIT, which did not have the problem when it ran iOS 5 FESTERING WOUND.

I want to like this comment twice.

Go and seek some professional help, like a psychiatrist.

nohone said,

The article never mentioned Apple products, but since you did...

I have had 2 different iPad ZIT tablets, 3 iPhone HEMMOROID phones, and 2 iTouch BOIL players, all of them had wireless problems at one time or another. When I had my app on the Apple store for the iPhone HEMMOROID and iTouch BOIL, there was a bug in iOS 3 FESTERING WOUND that I had to contact Apple support for, where WiFi would not connect, they partially fixed it in a point release, but it never worked correctly. They fixed it in a later release, but on my iPad ZIT with iOS 6 FESTERING WOUND it seems to be back, where WiFi seems to take forever to reconnect.

Meanwhile, I have had my Surface disconnect once, and manually disconnecting and reconnecting fixed the problem. Reconnecting on my Surface is not as slow or unreliable like on my iPad 3 ZIT, which did not have the problem when it ran iOS 5 FESTERING WOUND.

Had no problems at all in two week of heavy use.

In other news I was reading today of someone upgrading iOS on an older iPhone to the latest version, it shorted his wifi and Apples only suggestion was to have the phone replaced (at the users cost) apparently this is not an uncommon problem yet I missed reports of it?

This happened to me a couple of times when I first got my Surface but the issue hasn't resurfaced for a couple weeks now. It happens with Windows 7 occasionally too so it's not that big a deal.

Weird, I had a similar wifi issue during the beta (resetting the power management options was the solution) - used to happen while streaming 720p/1080p video. It seems it was fixed for the release (in my case). Hopefully this is a driver issue and is resolved soon!

I have the issue. It's happened about 6 times. Mostly when I switch to another wireless network other than my own home. The real problem is that their own troubleshooter, either does not actually pull the network card from device manager to reinstall, or does not do what it is supposed to. I am easily able to fix the issue by going in to Dev Man and pulling the wifi adapter and re detecting it. But can you imagine the average user running in to this problem 6 times in a couple of weeks? I'm an early adopter, I'm available for this kind of stuff, but the average consumer would lose there mind.

Since the last firmware update I don't think it has happened. Keeping an eye on it. However with all the recent updates, over all stability has greatly improved.

As one of the original people to report this problem to Microsoft, let me clarify the issue. I've been able to connect my Surface RT to dozens of Wi-Fi networks without any problems. The one problem I experience is connecting to a Cisco Wi-Fi network at work. I head up the Technology department, so we were able to do a lot of diagnostics to test the problem.

I'm able to connect to this network using Radius authentication, as an open Wi-Fi network, but was not able to connect when it was locked down as a guest network requiring a network key. Testing showed that if the network was reconfigured to using 802.11g only then you could connect. When I do connect the connection is fast and stable. Others that reported the same issue were also able to connect using 802.11g after reconfiguring their network.

This appears to be a driver software issue in my opinion since I'm able to connect with different protocols to dozens of different networks including those that require a network key. For whatever reason, my office network (One Controller with multiple WAPs and Wi-Fi networks) has an handshake problem or something preventing the connection. This network has been in place for years and no other devices have problems connecting.

Those are the facts!

Had this problem at home with a Linksys router. Changing to g only fixed the issue. Hopefully this will get patched soon.

This is not an issue with the Hardware its the Windows Core... i have the same issue with Windows 8 on 6 different computers... and the WiFi signal gets lost , says no DNS or limited connectivity, the real problem is that Windows 8 for some reason tries to get a Dynamic IP even if you set a Static one, so even if your network settings are fine... Windows isn't... so just reboot and it gets rid of the problem for a while then it comes back... FYI this never happened to Windows 7 and i reported this to Microsoft but just like all the other issues they didn't fix it.. i asked why and they said.. the Core networking was not to blame its the new HAL (same reason why IDE DVD-RAM drives during testing never worked) on RTM they just used a quick fix to add legacy support to the HAL and well is not working fine...

I'd also like to add my support that this isn't a Surface specific issue, because I've also experienced it on a non-surface laptop. The laptop in question has an Intel 4965AGN WiFi card in it, and it does the same thing as described in this article.

It never had an issue with Windows 7, but after upgrading the computer to Windows 8, the wireless connection will drop out repeatedly during (What I suspect is) heavy use.

I noticed it most when queuing up lots of large apps to download from the app store. As soon as it starts to download them all, the connection goes into limited mode, and all network access ceases. I connect it to the same 802.11n network that other laptops and phones connect to, and they can access it without issues. I've also tried updating the drivers using the latest version on Intel's site, no change.

One other odd thing I noticed was, every time it connected fine it was running at 802.11n speeds, and when it died, it would often cap itself to 802.11g speeds. Resetting the network adapter didn't always work, so I had to restart the computer to fix it, after which it would work fine again, until the App Store started to download the queue, at which point it would die again.

I'm quite convinced it's a Windows 8 wireless networking bug, because it never happened in Windows 7.

SaT.161 said,
This is not an issue with the Hardware its the Windows Core... i have the same issue with Windows 8 on 6 different computers... and the WiFi signal gets lost , says no DNS or limited connectivity, the real problem is that Windows 8 for some reason tries to get a Dynamic IP even if you set a Static one, so even if your network settings are fine... Windows isn't... so just reboot and it gets rid of the problem for a while then it comes back... FYI this never happened to Windows 7 and i reported this to Microsoft but just like all the other issues they didn't fix it.. i asked why and they said.. the Core networking was not to blame its the new HAL (same reason why IDE DVD-RAM drives during testing never worked) on RTM they just used a quick fix to add legacy support to the HAL and well is not working fine...

I sometimes can't connected at all.
It seems like a regression - allowing unpaid interns to do a man's job or something...

That was VERY NASTRY issue when I upgraded my computers.

I own the Surface RT 32GB and I've never experienced that at all. I sometimes have to put it on Airplane mode because the wifi is always on and is sending me double notifications on the Surface and on my Tablet while at hope.

I've also used this Tablet at several network wifi locations and for sure I've seen no issue. I haven't even had the splitting issue and I'm a careless person. The most damage I received that I'm still questioning is the chip I received on my back of the Surface. I'm pretty sure I wasn't that careless chip it. So I wonder if the coating is the blame or just me.

Yeah, I get this problem with mine as well.
It just goes away after a minute or so. Hasn't concerned me too much but I can see how it could be very annoying.

Luckily Pokerstars hasn't released their RT app yet, otherwise I'd be complaining big time about disconnections.

Since the patches last week, my IE (Desktop mode) freezes a lot!

Commenting is disabled on this article.