Unofficial Workaround for Microsoft Surface’s Wi-Fi Issues

A few simple steps that could fix your “limited” Wi-Fi connection

By on November 27th, 2012 12:47 GMT

A Wi-Fi issue is apparently affecting hundreds of Surface owners, as their devices sometimes get a “limited” connection error or even fail to connect to a Wi-Fi network completely.

While Microsoft is currently investigating the issue and promises to release a fix soon, users on Microsoft’s support forums have come up with several workarounds and some of them appear to be working.

One of the affected users suggests that a TCP/IP stack optimization tweak could solve the problems, although some others have claimed that it’s still a temporary workaround.

Here’s what you need to do:

First of all, launch a Command Prompt in desktop mode with administrator privileges and write down the following commands:

netsh int tcp set heuristics disabled
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global rss=enabled
netsh int tcp show global (this one is needed to make sure that all the aforementioned settings have been disabled)

Reboot the Surface and everything should work smoothly, without any Wi-Fi connectivity issues.

As said, this is an unofficial workaround, so we cannot guarantee that it solves the problem on all Surface devices. In the meantime, however, customers keep complaining and point out that calling Microsoft for support doesn’t make any difference.

“It takes sometimes more than 10 trials to get connected, and I'm losing the connection in an average of 15 minutes, making the Surface use, a very painful & disappointing experience. I've been in touch with the Microsoft technical support, I've been through all the settings of the box router with Free staff, but nothing we've done ever improved the connectivity,” one user explained on the support forums.

We’ve already contacted Microsoft for an official fix for this bug, but the company is still investigating the issue, so affected users have no other option that to wait until such a workaround comes out.

1 Comment