Wifi problem since 10.11.2

Good to know. At least it's something. I've been having issues for months now and have been following this thread the whole time and nothing has worked. To solve the issue I just ran a LAN cable into the room for now. I couldn't deal with the lack of Wi-Fi.

Just wanted to chime in....glad I found this thread.

I thought I was going crazy for a second. Late 2013 Macbook Pro. I upgraded a little while back and then restored from backup almost immediately. Luckily I have a similarly configured work issued early 15 MBPR running .2 and could immediately tell the difference in speeds.

My girlfriend made the mistake of scheduling my upgrade while I was away from my computer and I no longer have access to that backup. So it's either wipe clean back to .1 or suffer in silence.

So I guess a USB wifi dongle is a immediate solution while we wait for Apple to stop denying that the problem is a driver?

Also something that I noticed is that my upgrade from .1 to .2 did not cause an issue. But a clean wipe to 10.11.2 DID cause the issue. So I'm guess if the driver exists .2 does not touch it during the upgrade process...but whatever driver is included in .2 is the problem.

Sorry for the long diatribe. Just extremely frustrated.

Too late to edit so I'll just note....5ghz works fine.

The USB dongle has been a godsend. I travel for work and not having wifi renders my $1600 macbook pro into a paper weight. Also I have submitted developer bug reports for it as well. To no avail. The tickets just eventually close. Apple is slowly becoming Microsoft of the 90s. Too big to care.

Yes, I've been using WiFi dongle too to fix this problem for now

But right now I've installed 10.11.5 public beta 1, took out the dongle and native Wi-Fi seems to be working fine. Will post more later.

Has anyone tried this?

P.S. The funny thing that the bug was also gone on 10.11.4 public beta 1, but came back in subsequent releases, so there's some kins of pattern there )

Unfortunately, the bug is still there ;( Maybe it is less frequent, but still WiFi drops

Nothing better with the 10.11.5 ß2.

Just hearing this makes me want to scream. So in other words Apple doesn't care that many of us are having issues. Fantastic.

Not so fast, they might need more time to figure it out.

Let's keep fate! 🙂

WiFi problems have been apparent with MacOSX since 10.10 - albeit in 10.10.0 is was slow to connect, and transfer speeds were slow, it's now evolved into disconnects.

I have tried just about everything, right from changing the router to TKIP rather than AES, static IP addresses, even have upgraded to a full IPv6 connection.

Nothing has made any difference what-so-ever, still get the disconnects, once it starts doing the disconnects, rebooting works for a while - if you don't reboot then the disconnects just get more frequent.

Had 20 of them today - the router is keeping a nice little log for me 🙂

Maybe I should phone apple support and raise a case each time it disconnects, wonder how many tickets I could have raised 🙂

On a more serious note, let's hope that the past 18 months of sticking by apple when they have been going through a tough time with WiFi will pay off, I'm giving it a few more weeks otherwise machine will be on eBay and I'll get myself a shiny new HP or IBM (Really considering this as although I've been an apple fan for years, there is only so much I can take!)

I'm missing e-mails as a result, as mail will refuse to connect to the server, cannot stay connected to a VMWare View host for longer than 10 minutes at a time, RDP sessions disconnect blah blah blah.

Error from mail as an example: -

There may be a problem with the mail server or network. Verify the settings for account “iCloud” or try again.

The server returned the error: Connections to the server “p17-imap.mail.me.com” on the default ports timed out.

Luckily I have the RJ45 adapter so have been using that when in the office, not ideal or possible at home though (well not without drilling a few holes!)

Here's to hoping 10.11.5 will fix it, if not I'm out of the apple camp.

I just upgraded yesterday to this crappy El Something....Since then I got at least 30 wi-fi drop.Actually , The longest time without a drop was about 2 minutes!!!!!!! I have a problem with the desktop images too and suddenly the autocorrect starts and it give only creepy suggestions.I am really ****** off.. I paid a pile of money on this mac and "all that you need to do is to enjoy" ,said those sales men. Well I did enjoyed recreating my network, rebooting ten times in one hour,getting an network OsX expert. Is this the mac quality? Shame on you.

Hey there! For those of you who are experiencing problems with their Mac Mini (late 2014 and others) after upgrading to El Capitan I have found the only sure solution that worked for me after days of exhausting myself trying recommendations from Apple and others. Getting rid of El Captian on your Mac Mini and downgrading it back to Yosemite fixes this problem. Create a USB boot disk with OSX Yosemite on it, and install it. This is the ONLY thing that will definitely fix your wifi issue. Apparently El Capitan breaks the wifi and most of the proposed fixes online are bogus. Apple is NOT properly addressing this issue by offering workarounds. The average person doesn't know how to go in and reconfigure their network and doesnt know half the computer language to understand what they are actually doing with the workarounds. Apple should just come out and say El Capitan causes wifi issues with some Apple devices and we don't rdcommend updating until we fix it or offer a patch...DONE DEAL! Yes Apple, El Capitan breaks wifi on certain Apple devices. Not upgrading is the solution at this point. It's that simple.

I am also having Wi-Fi issues (for months) with MBP 2014 and I found a temporary solution to the problem, but one that really works. I have tracked down the problem to be or kernel or driver implementation bug with 802.11n (the important info here is the "n"). I have an Airport Express and inside the configuration for Wireless (Radio Mode) you can choose for 802.11n with 802.11b/g compatible and a lot of other options. if you have one two, before clicking the dropdown hold ALT(option) to show more options and select 802.11b/g only, if not look for this inside your router/access point. You can check what type of mode you are using holding ALT(option) and clicking on the Wi-Fi icon at the menubar (the same place as the clock), at the bottom you will see PHY Mode, and check there the mode you are connected if is 802.11n or 802.11g. You need to be using 802.11g (or other letter but not "n"), and see if your connection will drop.

I am using 802.11g for a while now (two weeks) and no driver crash (everything is rock solid, good speed). When the driver crashes the only way to reset automatic is to restart the network interface and turn it on again, that's why the Mac do it, but when it returns the bug continues (it can't communicate to the router and no connection is made) and you have to turn Wi-Fi off and on. But it continues because there is a problem with 802.11n. So we have to wait for Apple to fix it and I have been waiting for a long time and no solution yet!

Just to add info, I have tried everything you can imagine, El Capitan fresh install, do all sort of configuration, disable energy options, set IPv6, change Hz, disable bluetooth and etc. but nothing seemed to work for me. (even the AWDL).

Please give me a feedback if this works for you. Thanks.

I guess it's not just the MacBook Pros then if you are seeing it on your Mini.

anyway, 10.11.5 was just released Perhaps it will fix everything and make like wonderful again in the world of OS X.

Seems like a lot of work just to have the latest OSX running properly. This all happened over the weekend So I had upgraded to the latest version of El Capitan. The only thing that worked after 2 days was just putting the Mac Mini back to Yosemite. El Capitan wasnt worth the headache. My Mac Mini is running great now and wifi is super strong with no drop outs or anomalies with wifi. Do yourselves a favor and stick with Yosemite until Apple owns up to this. Apparently it only effects certain devices. I had this problem with a top in the past and they said it was my logicboard. Turned out the new OSX didn't like my laptop. I downgraded the OSX and BAM..worked again like a charm.