Are you having any issues with the Wi-Fi on your Surface Pro 3?

Microsoft released its Surface Pro 3 last week and so far, there do not appear to be any major hiccups with the launch. And while most users appear to be having no issues with their devices, a thread on Microsoft's support forums states that some are having issues connecting to Wi-Fi after waking up the device from sleep.

The thread states that users are waking their device up from sleep and then receive a 'limited-connection' error when trying to use a Wi-Fi network that they were using prior to putting the device to sleep. There appears to be a known issue if you have Hyper-V enabled and Visual Studio 2013 installed but many of those reporting the issue do not fall into this category.

There does not appear to be perfect fix for this issue as some reported that a re-install of Windows fixed the issues while others say that a simple re-install of the driver has fixed the issue too. Whatever the issue is, a small minority of users are experiencing the problem.

Admittedly, it is a bit hard to gauge how wide-spread the issue may actually be as we don't know the sales figure for the launch weekend of the device. More so, there are likely users out there who are experiencing this issue who have not posted in the support thread on Microsoft's website.

While we have not experienced this with our Pro 3, we do wonder if any of you who bought one have faced this issue? If you have, let us know in the comments below and if you were able to fix the issue, what steps you took to remedy the error.

Source: Microsoft Support Forums | Via: Softpedia

Report a problem with article
Previous Story

Samsung Gear Fit Review

Next Story

June AdDuplex : New OEMs and new devices come to Windows Phone

43 Comments

Commenting is disabled on this article.

I am not sure if this limited WiFi issue is with InstantGo. I was going through the other article related to sleep study and thought it might be connected to it. I tried the following command in cmd prompt: "powercfg /a" and found StandBy(Connected) was disabled. Futher reading through the article I found out if HyperV is installed it turns off InstantGo. So, I disabled HyperV using the following command in CMD Prompt(Admin mode): "bcdedit /set hypervisorlaunchtype off" and restarted my Pro3 and tried - "powercfg /a" and this time it showed InstantGo was enabled. From then on, everything started working without any issue from then on. Probably, it is worth to give it a shot and try on your end and see if that resolves the issue. Articles: http://winsupersite.com/mobile...yper-v-vs-connected-standby

Edit: Looks like this is already a known workaround for the issue. Anyways, you can try it if nothing else works.

Edited by PMMSPRO, Jun 29 2014, 3:30am :

This happens with my MSI Laptop and Windows 8.1. I close the lid and reopen later to find a limited connection. I've always fixed it by disabling the adapter and enabling it. I rarely put it to sleep anymore though.

Former Softie here...bought my SP3 last week and ran into same issue. Talked to an old buddy and there should be a hotfix for the wifi issue in July's patch cycle. Not so much a Wifi issue but more a power management, connected standby issue trying to optimize and squeeze every area where battery life can be extended. Hellava task to transform an all purpose full OS like Windows and dress it up like an iPad but feature rich in capability and universal apps on the way. If the next iPad drops iOS and runs OSX with Pen input, touch, usb 3.0, AppStore and SD storage, I'm game...

Temp fix: Enable Hyper-V to expose the advanced power options settings. Open power options, click change plan, click change advanced power, find wireless adapter settings, change to max performance. Then disable hyper-v and restart. Now connection speed will register properly on battery and connect to networks as expected. After hotfix, I'll revert back the wireless power setting to maximize battery life.

Had the issue of limited connectivity, random missing network adapter, and type cover not responding...still, i know how to rectify these and love my Note Pro 12.2 replacement. Hopefully these get fixed in a software update at some point. I would like to point out that my issues are few and far between and completely random. The adapter went missing only once.

I had this issue on day 1, the wifi issue, then I installed hyperv and the issue increased + I was not able to put it to sleep anymore and it had to fully start every time

There's something very wrong, either with the stuff they use in the Surface devices, or the OS. Also had issues with the wifi in SP2.

Yes. I am experiencing this issue rather frequently. I have even experienced instances where Wi-Fi had dropped to limited during the time I was using the Surface. My best tarecollection is that when this has occurred, I was on battery, but active, not coming out of standby. While I find this to be irritating and disruptive, it only takes a few seconds to swipe in the charms, disconnect and reconnect the connection. I read through some of the "fixes" suggested on the forum. I prefer to wait for a firmware or software update fix than go through the process of disabling and reinstalling drivers, etc. It is annoying, but not so much so as to detract from my workflow and appreciation of this superb machine.

I have the same problem too....the wireless totally disappear and it wont even show in device manager. The only way to fix it is restarting the SP3. Other issue that I have also found is that if you leave the sp3 keyboard connected, and you lock the sp3 or you shut down when it comes back the track pad doesnt work you have to attached and detached the keyboard. Also, I don't know if this is just coincidence but I passed the SP3 thru TSA scanning after the scanning I turn on the sp3 and nothing happen...i had to push the on button for 10 seconds and then hit again to force shut down. Then a second TSA scan.....after the scan, i hit the power button...the loading screen that says "SURFACE" appears and then it went directly to the surface bios. Looks like the x-rays have some negative effects on the surface. Any one else have issues thru TSA scanning at air ports?

Wall-swe said,
AS usual when its concerning Microsoft nothing is acceptable and people wildly complain and techblogs report on the case. But when Apple and it's MBP pro is affected, its silent even though the issue thread has almost 3000 responses and half a million views...
https://discussions.apple.com/...481839?start=0&tstart=0

Apple gets their fair share of egg on the face on Apple fan sites - of which Neowin isn't really big on that. Thought that was obvious...

With that said, this article has nothing to do with Apple.

No this article isn't about Apple and that's my point, only problems concerning Microsoft hardware seem to be a subject for techblogs.

Thankfully, none of my Surface devices (RT, Pro, Pro 3) have had these issues. I certainly hope this continues to be the case. And, I certainly hope MS gets this fixed.

neonspark said,
it's the curse of the wifi and surface. they have been fixing this since surface pro

Not true. I have the original Surface and never had this type of issue.

Gergel7077 said,

Not true. I have the original Surface and never had this type of issue.

you should meet more Surface users. there's threads upon threads of people with the issue.

and hey, not knocking the surface. I've owned the original and now the Pro 2. there have been wireless issues since day 1 - or have you not paid any attention to the firmware updates they've released over the past year to "try" and resolve the issue? they weren't releases those just because they could - people had problems.

http://www.microsoft.com/surfa...activate/pro-update-history

http://www.microsoft.com/surfa...tivate/pro-2-update-history

And there will be a link for the pro-3 as well and in the future will also have all the wonderful firmware/software updates to patch the wireless. :)

Tarrant64 said,

you should meet more Surface users. there's threads upon threads of people with the issue.

and hey, not knocking the surface. I've owned the original and now the Pro 2. there have been wireless issues since day 1 - or have you not paid any attention to the firmware updates they've released over the past year to "try" and resolve the issue? they weren't releases those just because they could - people had problems.

http://www.microsoft.com/surfa...activate/pro-update-history

http://www.microsoft.com/surfa...tivate/pro-2-update-history

And there will be a link for the pro-3 as well and in the future will also have all the wonderful firmware/software updates to patch the wireless. :)


I don't need to meet more Surface users. I personally work with several Surface users at my job plus know a couple of friends that own Surface Pro's as well. None of which complain about this issue.

Sorry if you have had issues but fortunately for myself and those that I know, we do not. BTW, in case you haven't noticed, all hardware of this type have issues, ALL. I should know as I work in IT and deal with this tech all the time, especially Apple products.

has anyone had the similar issue but with the micro SD slot after waking up from sleep or reboot? I would have to remove and reinsert the SD again. It worked fine on the SP2.

I've had the Surface Pro and currently have the Surface Pro 2. Both had the wireless issues. At first I thought it was the hardware but a lot of Windows 8 PCs I've used have had issues with network drivers in general, more commonly the wireless ones though. I'm surprised though that for this hardware to come out of a Microsoft shop - that it doesn't work.

To me personally Surface & Wireless Not Working stopped being news a year ago. lol. It is however interesting to see that the Pro 3 is plagued by the same problems...

Yep. Happens on my SP3 every time I put it to sleep. It wakes up with limited connectivity.

I just toggle wifi off and back on again and it works, but it's annoying.

There is absolutely an issue here. For myself it is not persistent but has happened a few times. On Surface 1 this was a constant issue until they finally fixed it. Not so much on my Surface 2. Surface 3 I have had this issue a few times. It has nothing to do with my Hyper V cuz it's not enabled. No I have not had to reinstall Windows. For myself a simple reboot fixes the problem.

I have also had some strange stability issues, maybe a half dozen or so. Once again, reboot fixes.

Other than this stuff, I am blown away by this device. Call it the Pro for a reason, it's for those of use that actually know how to use computers and technology. This pen input is seriously cool and the pen allows the effective use of real desktop applications on a tiny screen. Applications that one could not possibly use on a dumbed down tablet experience are fully usable with the aid of the pen as a pointer when in a mobile situation. Fantastic OneNote experience. And Outlook 2013 which was not so attractive to use on the Surface 2 is perfect on the larger screen here. Far Far exceeding my expectations for my use.

Yep, i get the limited message sometimes when I allow my system to go to sleep and then wake it up -- but only when it is tethered to my Galaxy Note 3. Otherwise it's fine. I just boot my phone and it's fine once again.

I have wifi issues with windows 8.x in general. A lot of them get an error where they can't find any network. Have to restart wifi adapter to fix.

I have this issue too. I can get WiFi going again by toggling the WiFi option off then on, or by restarting the SP3.

With regards to Visual Studio 2013 and Hyper-V disabling the connected-standby mode, a BCDEdit of the hyper visor launch type *fixes* this sort of. With it disabled, I can't run the Windows Phone emulator. See Paul Thurrott's site for details: http://winsupersite.com/mobile...yper-v-vs-connected-standby


This appears to be a problem with Windows 8.1 and all newer wireless drivers. I've had that issue using the Surface Pro 3, Surface Pro, Asus Zenbook UX301LA, and various other newer devices.

My resolution has always been very similar:
•Uninstall any wifi drivers via Programs and Features. Sometimes the drivers have extra software, so this is always the first step.
•Go to Device Manager and uninstall (including the driver) for the WiFi card
•Have Device Manager search for devices and let it automatically install the driver, or go to the manufacturers website, and install the latest version (especially in Intel's case)

A simply uninstall of the driver and reinstall has fixed it on almost every device I've used.

I have the original Surface Pro. It's now happening a lot more frequently (once a week) when I wake the device from sleep, it cannot detect the wireless card. It just doesn't even exist in Device Manager, and scanning for hardware changes won't detect it. The only way to bring it back is to restart, and 20 seconds later it works again.

I suppose your Pro is over 1 year old outdated piece of crap, so you supposed to buy new thing to let the consumer society spinning and spinning and spinning and...

</cynical sarcasm>

I had and have this issue sometimes, although not very frequent on all Windows 8.x laptops and tablets I've used and am using. I also had a very bad experience when I was in a conference hall and my laptop wouldn't connect to WiFi. I had a Linux on another drive, and I was getting WiFi on Ubuntu, but not on Windows 8.1. :(

I had this issue. In device manager disabled all power management options on wifi and restart. That fixed it

Sikh said,
I had this issue. In device manager disabled all power management options on wifi and restart. That fixed it

I did that on your advice... causes mine to blue screen when resuming from sleep.

Seems fixed now, though, after toggling it back.

Why do these guys have so many issues with this thing? Are they just over reported or is there something that Apple seems to have no trouble with and Microsoft has lots?

babyHacker said,
Why do these guys have so many issues with this thing? Are they just over reported or is there something that Apple seems to have no trouble with and Microsoft has lots?

Apple has also had issues with WiFi connectivity across their entire range of products. Pretty much every manufacturer has.

If it uses a broadcom chip, I'm not surprised at all. The new broadcom chips and drivers have been horrendous when it comes to WiFi and every so often my laptop (and thousands of others that have the same chip) will do the exact same thing. But if I swap it to another manufactuer then I lose bluetooth since the new broadcoms have combined bluetooth and wifi on the same chip.

Don't get me started on the # of times I have crashed iPads etc. on and on. But yes in this instance, there is a bug in the Surface, bugs get reported and hopefully fixed.

YES! I have this issue! I haven not attempted any fix yet. Reinstalling the same driver doesn't seem like it'd do anything , but I suppose it is worth a shot. Reinstall Windows seems absurd.

I usually reboot, or I just wait 2 minutes and it seems to come back.

On my (non MS) win 8 tablet I was getting a limited network issue every 20-30 mins and after much painful searching finally reinstalled the (same) driver and not had the same problem since.

Mine is working fine but a friend of mine was complaining that when he switches between wireless networks the Surface "hangs on" to the previous network (for example, his work network when he's home).

not really I usually had to press disconnect then it would usually realize & connect to the correct network

it didn't happen all the time but that's what i had to do when it did