It's hard to call Surface Pro 3 anything other than a success: once seen as a side-story to the Surface mini, Surface Pro 3 has exceeded all of Microsoft's internal expectations and has singlehandedly turned around the business. But there's one big problem with Surface Pro 3 and it's been lingering, malignantly, since the product launched this past summer. The device has had rampant Wi-Fi issues, and despite several updates aimed at fixing them, nothing has worked. So this month, Microsoft is going to try again.
Will Microsoft ever fix the Surface Pro 3 Wi-Fi issues?
The worry is that they cannot, that the problem is endemic and related to a hardware flaw that would require a new device version if not a recall of the original. Obviously, Microsoft would like to avoid that. But the firm is also stretching the bounds of credibility when it comes to getting this issue fixed. It would be funny if it weren't so frustrating for the people impacted by the problem.
Just documenting Microsoft's failed attempts at fixing the Wi-Fi problems is daunting. Here's a short and possibly incomplete version:
With its July 2014 firmware update, Microsoft "improved some Wi-Fi connection scenarios" in Surface Pro 3 and promised further fixes. It then released a second out-of-band fix in July which "further improved Wi-Fi connection and throughput scenarios." Then in September it issued a fix for "Wi-Fi stability," which was supposed to correct what I called "a lingering Wi-Fi problem." And in October it delivered a fix that "improved Wi-Fi throughput, especially after rebooting with Bluetooth devices that are paired, enhances power consumption situations, and addresses instances of system instability."
Problem solved, right?
Nope.
In a blog post—which, oddly, is on TechNet and not the Surface Blog—Microsoft explains that it will try again to fix the rampant Wi-Fi issues that are dogging Surface Pro 3 users. A new Wireless Network Controller and Bluetooth driver update will "enable better throughput after waking from sleep and connecting to an 802.11AC network, ensure Infra scan list is not empty while connected to a wireless display adapter, resolve an issue connecting to Cisco 1242 access points, ensure the device reconnects properly to a hidden SSID using a 5GHz DFS channel after waking from sleep, and add customer-requested functionality to prefer 5GHz connections when both a 2.4GHz and 5GHz connection are present with the same SSID."
Whew.
So will Microsoft ever fix the Surface Pro 3 Wi-Fi issues?
Discuss this Article 63
This is clearly terrible for all those affected, and cuts to the very essence of the device. But it should also be noted that not everyone has experienced this problem. I have two Surface Pro 3s in my family both exclusively using different wifi setups and neither have had any wifi problems, that we were aware of or noticed in using them.
I'll quickly find a bit of wood to touch.
I've only had mine a week, but I have connected to various wi-fi networks and apart from my office at work I haven't had any problems.
I fixed it in my SP3. Uninstall the hardware, and let the system re-install it. Worked magic.
Let's not over-state this problem. A majority of people don't seem to be experiencing significant issues. I've had a few issues where it takes a few seconds to reconnect to Wi-Fi after waking up, but they're mostly gone after the last update. It was never a significant bother to me. And yes, I use a Wireless AC network at home, N at work. Things are mostly fine.
I'm sure it's frustrating for those that are more affected than most, but to read this article would lead people to believe nobody can reliably connect to Wi-Fi with a Surface Pro 3, and that's just not even remotely true.
Thanks for that. I was going to ask how bad it actually was. I think the article merits an edit stating that most users are fine. He's made it sound like not a single SP3 can connect to wifi reliably. That doesn't help anyone.
No problem with my i7 SP3, but my daughter did have a couple of hiccups with her i5 early on. Required reboot to reconnect. Haven't had a problem in a couple of weeks.
At least MS is trying to resolve the issue. Lenovo on the other hand seems to be ignoring the issues altogether and they use an Intel chipset.
Perhaps the question isn't if MS will fix THE wifi problem, but when will they fix all of them. I think they are gradually knocking them down one by one on a monthly basis.
It's always easier to fix a problem that you can reproduce. I had a lot of issues with Surface 1 and 2, but rarely do I have issues with Pro 3. Probably because there are many different types of routers out there, and some probably have more issues with this particular chipset than others.
But I agree, after reading about yet another Wi-Fi firmware update, I feel sorry for the folks that are obviously still dealing with this issue.
Poor wifi seems to be a feature of Windows machines these days. My Acer W8 tablet had very poor Wifi out of the box though thankfully a driver update mostly resolved it. My wife's Vaio had terrible problems which we couldn't sort out and I had to resort to using a cheap USB dongle. Searching for the problem threw up plenty of other problems with different brands too.
Dell Venue 8 Pro also had this problem. 2 MS KBs seemed to be responsible, and blocking their install kept the limited connectivity issue at bay. Maybe it's inside Windows 8 somewhere?
Strange I have no such issues with my SP3.
Is only an issue with AC networks? I've not encountered an AC router yet, only B, G and N routers, and have not seen a problem yet.
Nice job with Photoshop ;-)
Yes. They will call the fix Surface Pro 4 :-).
Seriously, though, I'm sure they are using off the shelf components for Wi-Fi. If so, they should be able to resolve with software.
Let me guess: Broadcom chip???
Ha! No kidding. But Marvell in this case.
I can verify this issue does exist. I lost count of the number of times I've had to reboot to get the Wifi to work. I've noticed the problem mostly occurs when moving from home to work networks or vice versa. Now, if Microsoft would also fix the squirreliness of the trackpad, I could actually like this computer
Personally, I've found the trackpad to work great after adjusting to the different right-click behavior. If you do a two-finger *tap*--rather than a *click*--it works just fine. Same goes for one finger, actually--tap instead of click. I think the only time the click is really necessary is when you have to drag something.
Paul.. sometimes you just go WAY over the top... this being one of those cases.. Geeze man.. really? For all intents the SP3 wifi works fine .. Yes in some convoluted circumstance of stars aligning you may have to restart to fix a limited connectivity issue.. but you're over dramatizing something that is the 3%. We have NUMEROUS (20?) SP3's deployed (I'm an IT manager).. and so far NONE have reported this issue. Slow news day any? Peace.
Let's not forget the other possibility... With every update, Microsoft is gambling that it won't break what does work. Especially since the Bluetooth driver is coupled with the WiFi. I initially had trouble getting my SP3 to stay connected to my Bluetooth speaker setup. And the device was one of the reasons I decided to get the setup. Thankfully, the issues were fixed by the September update, but after the most recent one, I experienced the issue again for a short time. I heard the ominous disconnect noise from the speakers several times. Nearly threw something out the window. It has since gone away again.
conspiracy theory here? mag vapor case isn't wifi friendly. why doesn't every PC oem using the same cards have these problems? maybe the signal is so degrated by the time it reaches the antenna that MSFT has to play firmware tricks to clean it up leading to horrible stability.
That's like putting a piece of paper in front of your face to block sound. Doesn't work. The mag vapor case is not the problem.
It isn't wifi friendly. That is why there is a plastic bar running across the top of the computer ;)
Another 'wireless performance improvement' update, thought the last one fixed things... ;-)
My SP2 received numerous similarly worded updates, until they gave up -- there's an issue with the combo Bluetooth/WiFi chip that can't be resolved with updates. As of the last update, I still experience the 'known-issue' of WiFi speeds being reduced by half if Bluetooth is turned on. At least I have a workaround, turn off Bluetooth -- kind of an inconvenience though when using Bluetooth speakers while streaming Netflix or Amazon :-(
I purchased my Surface Pro 3 at the Microsoft Store in Atlanta the day they were introduced on June 20th. At home I have a NetGear AC 1900 router on a Comcast cable modem. I've never seen any WiFi problems whatsoever. Testing on my home setup with an AC connection, my ping averages 10 sec, my download speed averages 30 Mbps and my upload speed averages 6 Mbps. Those results are very consistent. I connect with no problems to WiFi wherever I go throughout the Atlanta area. Speeds vary of course, but connections have been reliable. I've connected without problems to WiFi at the public library, the bookstore, several restaurants, the doctor's office, the dentist's office and several shopping malls.
Hopefully that's a 10 ms ping! :)
I was recently provisioned a Surface Pro 3 at my day job. I really, really like it BUT, the Wi-Fi does have issues. My current sense of the Wi-Fi problem is multi-mode environments and 'perceived' signal strength. I think the crux of the problem is that whatever the issue is, the speed and reception is just down right inconsistent and for a device of this cost, that is completely unacceptable.
If Microsoft does not resolve this issue by the end of the year, I would propose a class action law suit be initiated to inspire Microsoft to deal with this issue sooner rather than later. If I were the manager at Microsoft in charge of dealing with this issue, I would do the following...
1) Clean slate redesign of the Wi-Fi (wireless) components.
2) Test, test, test.
3) Repair of existing stock of Surface Pro 3's
or begin new production run of 'corrected' units.
4) Begin recall and swap defective units for defective units.
My thoughts are that Microsoft has probably not sold so many units they could not afford to make good on this product, especially if they ever want to sell more hardware in the future. Otherwise, this could very well be the last tablet (or mobile device) Microsoft ever sells. I am very disappointed in Microsoft and this product. If I had spent my own hard earned money, I would have already taken this unit back or started talking with my attorney friends about getting them some new class action business.
I think the problem with you third step is SP3's almost complete lack of serviceability / repairability, to the point where basically every unit exchanged will go to recycling. (at best)
Fixing this issue is therefore a two-for-one deal for Microsoft, and that can quite quickly escalate into RROD-like territory in terms of cost.
I thought Microsoft fixed everything they create,in the 3rd version.. I guess I'll wait for Surface Pro 4 then :)
Never had Wifi issues on my SP1, SP2, or now my SP3 but I always hear a vocal minority complaining. Guess I'm lucky?
If you look at Ifixit's teardown of the SP3, you'll clearly see why Microsoft will do everything in their power to "fix it in software" - there is not fixing the hardware without a full revision, giving everyone complaining a fesh SP3, and dumping all the old ones in a landfill.
I agree with those suspecting this charade to continue until SP4 comes out, hopefully featuring working hardware, and SP3 will be forgotten.
Would now be the appropriate time to mention that WLAN is largely a solved problem for the very OEMs Microsoft tried to school with the Surface line?
I had WiFi problems on the SP1, SP2, and now the SP3. In all fairness, the SP3 is a little better than the other two, but still wonky at times. I strongly believe this is their insistence on using the Marvell wireless card, and CANNOT be fixed absent a recall or all of us moving on to the SP4 WITHOUT the Marvell card. I have been scolded at various websites that this is not the case, but when it is the sole common thread among all three models.
It's off topic, but I didn't find more than 1 answer in months:
Who thinks that using a fan to not throttle the surface pro 3 could damage the hardware?
https://www.youtube.com/watch?v=uC8rCeDMqFw
I get good results with the fan and can play my favourite game on low/medium settings with good framerate. Any comments on the possiblity that this might damage parts of the device? The creator of the youtube video seems to know what he is talking about, ... but I want to be sure.
I've worried about this too as the screen gets hot. But I've also used the computer for CPU intensive tasks, not Graphics intensive. The screen gets nearly as warm as during a fanned-graphics test but does not throttle under full load (100% x 4 threads @ 2.5GHz) without a fan. If it can support the high-T high-CPU load I think it will be ok.
From day 1 I've always said that "802.11 was never ready for prime time!" It's a much maligned standard with too many folks trying to make it better, instead of making it work! Of course they usually fail tremendously. Heck, even Apple's having WiFi issues on it's latest OS and hardware.
My particular WiFi problem is 100% software. I use hidden SSD networks, and often the Surface 3 (and other machine BTW) can't connect and ask for the info again. I end up with a slew of copied WiFi profiles of the same name, but numbered. "Hidden" turns in to "Hidden 1", "Hidden 2" etc etc until I get a ton of them. Cleaning up this mess is a pain, and even Microsoft Support couldn't answer why or how to handle better.
Or better yet, how about the plethora of aweful Consumer WiFi routers out there that usually end up eating themselves with high heat or poor firmware updates! Nobody is safe in this problem, as there is no company that can produce a router that won't have issues for some if not all of their users.
WiFi stinks, always has, always will.
Paul,
I think the accepted behaviour in the "mobile" industry is to be an apologist. This narky approach is so 90's.
Paul, the bright side of this is that they are *delivering* fixes.
With most other Windows laptops, they're left to rot by the OEM after a half-hearted attempt or two to fix the issue. I've seen models silently drop Broadcom (ugh) cards in favor of Intel, and then still have 200+ pages in forums about WiFi issues with no further driver/firmware updates. I've seen the same Intel models have trouble across different laptop models and OEMs. In many cases, tweaking the power management settings resolve it, but do you think those OEMs could be bothered to offer even that simple workaround? It seems like once they ship a model, if it doesn't work on release day... sucks to be you.
I agree with others that these claims make it sound like the WiFi is nonfunctional, which is simply not accurate. I can only imagine the complexity of trying to work reliably with such a broad mix and level of quality/maturity of consumer and commercial WiFi gear. That's not to say Microsoft should get a pass on this, but the fact that they are delivering a steady stream of updates and not stamping the issue as "fixed" after driver release 2 is cause for applause.
Unlike the OEMs that dump hundreds of models into sales channels each year, there is value in the small number of SKUs approach.
I rather doubt this is an irreparable hardware problem. The Marvell card used is not exclusive to the Surface and if it was causing the same problems everywhere would be making news in the EE trades.
Also, that list of existing issues includes some somewhat obscure situations. This doesn't strike me as a seriously troubled product so much as the focus that comes from having a single model (aside form CPU) that is widespread as opposed to the myriad models in most companies' laptop lines. You see similar attention when there is a problem with a Macbook model.
I have one of the original Surface RTs. I recall it going through similar months of updates and patches, only to have it require a reboot to connect when pulling out from my bag. I truly am considering the Pro 3 as a replacement for my i3 laptop. But I need more reliable connectivity. My RT- seems ok now, but it was a long time to get to this point.
I've had my SP3 since day one and the only time I have had any WiFi issues was when I turned on Hyper-V. I think that is where the core of the issue is. I had to disable Hyper-V and have not activated it since.
I have an I7 without a problem, and a co-worker with an I5 that did have the problem, not able to connect to the same router that I was on after wake. When that surface died from a problem with the keyboard connector, it was replaced by a new one by Best Buy under their extended warranty, and the replacement one has not had the problem at all. A third co-worker with an i5 unit also has no problems. It is my opinion (based on nothing more than my experiences, I worked a couple of days on trying to fix the one I5) that there is a hardware glitch in some of the chips. No fix MS released, nor rolling the unit back would help the problem. Better testing by the mfg of the chip required?
Honestly, are MS really calling the SP3 a success, or are they do desperate for a 'hit' they're fudging the figures. The last MS earnings call showed revenue on the Surface line which, roughly translated to under 1m sales in the last quarter. Nobody these days would call that a 'success' - certainly not in Apple or Google's eyes. Maybe it is a 'success' for Microsoft, but the whole Surface venture is still losing money hand over fist, and with ongoing Wifi problems that they don't appear to be able to fix, it doesn't help with the Surface reputation. As an IT professional, I still haven't seen a single Surface of ANY description in the wild.
It convinced HP to copy it almost exactly with their new Envy x2. I'm assuming before HP started manufacturing they double checked with MS on sales. It is the point of the SP3 after all to be a reference design for hybrid computer.
I'm having a strange wifi problem with my pro 3. Since last evening, I don't see the home-office wifi network in the "available" list! But I'm able to connect to my Android phone (tethering mode). Restarting, re-installing the drivers didn't help!
After the Nov update I still have a limited connectivity problem and slow throughput. It only happens at my local library public access network. No problem with my home WiFi connection.
I have a work around in which I use an external Netgear adapter. I noticed thou that sometimes I have a problem even with the Netgear adapter. The problem seems to solved if I pull it out of the USB port and reinstall it. For that reason I am inclined to think the problem is not just with the internal WiFi adapter.
The workaround is not an acceptable solution as I have lost the use of the USB port.
I really love my I5 SP3 but I still have major wireless issues. Every time I reboot, resume I have to disconnect from the any previously connected wireless network, then reconnect. Sometimes it takes a few tries to reconnect. This is not a an acceptable end-state.
I had a SP2 and it had no wireless issues running on the same network that the SP3 can't seem to reconnect to
I have a Surface Pro 3 i5. I am IT Consultant, so I have to hibernate or put it to sleep between customers and I also do it frequently at home. I am sure there are major issues with the WiFi adapter. I installed the updated drivers from November, fingers crossed, but with no success. The adapter needs to be re-connected and even be disabled-enabled so that it wakes up after a hibernation or sleep mode.
It is very annoying, sometimes I need to connect very quickly to solve some client's stuff but the lack of WiFi is a very huge issue. Taking into account that this device does not have a wired Ethernet port, the issue is still worse.
I am not sure if you all are having it, but I do have it, and I love the device, but this only issue drives me crazy sometimes, at the point at which I think I would sell it.
:(
This is definitely a real problem and I am the fool who proves it. I am on my fourth surface pro. After two 2's I gave up. Got an early three and it crapped out on wifi in five days. Waited for three updates and tried again. It worked until the updates came today. The browsers don't work. Explorer funds msn once and can't even bing search after that. Rebooting is not the cure. It it turns out like before I will have to revert the wifi driver and block updates. I just wish this had happened in the first 30 days and I would have returned the unit. All Apple devices work perfectly on the same wifi.
I must be incredibly lucky. As an early adopter I bought the SP 1 quickly followed by the SP2 (sold the SP1 on Ebay) and then as soon as the SP 3 came out I gave the SP2 to my son as a birthday gift. I have not had an ounce of problems with any of the 3 versions and I have never had to change out any of my computers. I can only sympathise with those people who are experiencing problems.
For the record, I run Office 365 where I am a heavy Excel user and Adobe Lightroom and Photoshop CC again with no issues.
With respect to the reported WiFi issues, I can also report that I have not had a single issue. My house and office have strong WiFi signals and when I travel I have an AT&T MiFi so I am always close to strong signal sources so maybe this is why I have no issues.
My son, on the other hand, is complaining that his WiFi reception is poor with my old (trouble free SP2). BUT he is at present travelling in India and at a Camel carnival in Bikaner where they use camel dung for fuel which may, just may have something to do with his lack of signal strength.
Seriously - I am so unhappy with my Surface Pro 2 - I've had it since the 256GB version was released and it's fine with known wireless networks. It seems for some inexplicable reason to "panic" whenever I put the machine to hibernate in one environment with a known wireless network and wake-up in another environment with an unknown wireless network. Typically, I'll be at home working away, put the machine to hibernate and awaken the machine at the airport or some coffee shop intending to do some more work and it will "freak out". Sometimes it will try to join the network and do so but then the network is "limited" when I'm literally 10feet from the router. I try all the recommended steps: turning off/on the wifi, disabling/renabling wifi adaptor, rebooting, reinstalling drives, etc - NO JOY. The slap in the face is that my Windows Phone can connect to these networks with (almost) never any issues. Other times it will complain that the "network cable is unplugged" for my Mavell vEthernet adaptor. Seriously, what gives? I've been in to see the folks at the MSFT store numerous times about this (and other issues) and quite frankly, I'm done. The surface was a great idea on paper but wifi issues and battery issues and pen issues and everything else has burned me so bad that I'm going back to a brain-dead simple laptop (I hope the Dell XPS-13 2015 or the Lenovo Thinkpad X-1 Carbon 2015). I don't even care about the touch-screen. I'm so over it. The Wifi issue is the icing on the cake for an always-on/always-connected device (or the straw that broke the camel's back). Great idea - lousy execution. It's 2014/2015 for crying out loud - how hard is it to get a device to connect to a wireless network?