Q: Late 2013 Macbook Pro Retina 13'' Wifi Issues

I have the same problem with my late 13", where it won't autoconnect and it will reconnect if I disable and re-enable WIFI.  My firend has the same computer, same problem, and this is my 2nd one.

I noticed that it doesn't have any problem with open WIFI netowrks (no password).... seems odd

can somebody please try this on windows?

im really curious if the wifi issue appear there as well.

Tried windows 7 / internet explorer on my late 2013 mbpro 15 inch. Same WIFI problems.

Now this makes me think it is indeed a hardware issue.......

Are there any mbpro users who returned their machines and had this solved in a new one?

thanks for testing. Now it depends on the driver. Maybe windows is using the same faulty driver, which is provided by Bootcamp. Not sure about this. What about these UEFI / EFI installation types, these have no direct access to apple's driver, do they?

Otherwise it might really be a hardware thing.

If only there was a single MBPr 13" Haswell User reporting of a perfectly normal WiFi on his machine?

I got a brand new ipad air 128 GB wifi/4G and a new macbook retina 13" with a 1 TB SSD. Same problems. I think it is hardware related and I'm sure apple is aware of that. But they can't admit that because of politics or anything else. Let's say a chip in the macbook is crap, what are they supposed to do? They can't replace the chip on every macbook to satisfy all customers. It would be a financial disaster. They would rather do nothing and something like "we don't know anything regarding your problem" as enough people already experienced at the apple stores, or genius bar or the hotline. It's totally stupied.

Together with my iphone 5s I spent about 5k because in the past, apple equipment satisfied all my needs and there was this "it simply works" thing. But at this time i'm very disappointed and angry. It's annoying.

It would be a financial disaster in the long run if Apple pretends nothing is wrong.

This was my first Mac in 19 years and it will be my last one forever if all quaily problems are not addressed.

This problem has to be carried outside this forum. So if you run a (tech) blog, portal, magazine, whatever – post about it and make people aware of the wifi problems and put some more pressure on Apple.

And as far as i know, the WiFi Adapter is one of the few parts that can actually be replaced!

I will contact apple after the holidays. Not looking forward though to lots of discussions and maybe a new machine with the same issues.

this might be a silly question after reading this post for a couple of days but my late 2009 pro is on his last meters ...and there is a big need for a new one ... i guess i should hold of with that ?

Or is there anybody around who can say he is sattisfied?

My main concern for my mac is use of the internet, with constant browsing through thousands of pages due to my job ....

Is it a bad decission to go for one at the moment ?

There are a few workarounds to the latency issue.  I think the dropping issue was totally resolved with the latest driver.  I'm quite a heavy user and it took me quite some time to even notice it.  It's nocticable when pinging anything in terminal.  There are a few workarounds to that if you need consistent pings.  (I'm a network engineer so I do need that consistency.)  For msot users, they probably won't notice it.

I'd gesture to say that even a Mac with some issues, it's still far better than Windows.  I jut helped someone work on a windows 7, then a (nightmare) windows 8 machine....THAT was a nighmare!  So much that it went back for a refund.  No Mac in the world could be nearly as bad as that.  And if you've been on your Mac for a while, you'd go nuts trying to go back to Windows.  Wait for a bit, but definitely get a new Mac.  Even if you buy one right now, it's an annoying thing IF it happens to affect you.  Normal browsing and applications, I doubt you'd even see it. 

CMCMC wrote:

 

I'd gesture to say that even a Mac with some issues, it's still far better than Windows.  I jut helped someone work on a windows 7, then a (nightmare) windows 8 machine....THAT was a nighmare!  So much that it went back for a refund.  No Mac in the world could be nearly as bad as that.

Sorry, but we are talking about a 13" notebook (good WiFi being one of the most important features on such a machine), which looses its WiFi every couple of hours and won't reconnect. Honestly, i couldn't be worse.

Let's quickly look up someting: Oh, no Internet. Wait, disconnect WiFi, reconnect WiFi, wait again..

I totally agree with you!

It's really annoying to have problems with basic internet usage.

Yes - think you are missing the point - there is a problem - if you are not noticing a problem, you have the wrong discussion!

ok me again so i went out this morning and got my self a new retina 13" ... an hour in wifi hasn't dropped or anything... it's snappy and works fine so far ... i'm still cautious ... but i will keep posting how it goes.

It appears my wifi adapter on my new retina macbookpro is falling asleep if not used at an interval of less than a second.  I think this is exactly the latency issue i've been seeing when connecting to remote terminals.  The more remote shells I run the less this seems to be an issue.  However one remote ssh connection is not enough to keep the wifi adapter from going into some sort of sleep mode.  Below are the results of pinging at a 0.2 sec (200ms) interval vs pinging at a 1s (1000ms) interval.

ping -i 0.2 192.168.1.1

PING 192.168.1.1 (192.168.1.1): 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=38.522 ms

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.136 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.149 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.075 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.156 ms

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.025 ms

64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.139 ms

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.166 ms

64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.195 ms

64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.059 ms

64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.133 ms

64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.065 ms

64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.605 ms

64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.638 ms

64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.224 ms

64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.076 ms

64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1.026 ms

64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.169 ms

64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1.128 ms

64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=1.760 ms

64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1.112 ms

64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=1.051 ms

64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=1.255 ms

64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=1.055 ms

64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=1.117 ms

64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=1.173 ms

64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=1.126 ms

64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=1.289 ms

64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=1.153 ms

64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=1.255 ms

64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=0.975 ms

64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=1.114 ms

64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=1.672 ms

64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=1.598 ms

64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=1.153 ms

vs

ping -i 1 192.168.1.1

PING 192.168.1.1 (192.168.1.1): 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=259.458 ms

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=180.414 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=100.878 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=22.095 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=249.786 ms

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=170.507 ms

64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=91.480 ms

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=11.999 ms

64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.183 ms

64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=160.052 ms

64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=79.727 ms

64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.630 ms

64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=35.497 ms

64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.881 ms

64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=69.822 ms

64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=106.626 ms

64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=130.952 ms

64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=137.781 ms

64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=58.795 ms

64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=204.236 ms

64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=207.971 ms

64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=1.166 ms

64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=48.795 ms

64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=276.781 ms

64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=197.100 ms

64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=118.236 ms

64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=38.446 ms