Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why, oh why hasn't El Capitan fixed Mac's most infamous WiFi issue after all these years!!!
- Thread starter sniffies
- Start date
- Sort by reaction score
YUP! and it might not work properly yet
Good picture!
I'm having massive issues with Yosemite and networking. I finally updated my 2 imacs. Both froze at the same point of the install. Both imacs no longer have functioning wifi or hard-wired ethernet. I tried updating the firmware of the airport but get some mystery error code with no help. I tried downloading Mavericks from a Yosemite computer. Upon opening the installer it says it is too old of an application to be opened by the current operating system. Great big apple fail on all accounts. OS X is the windows XP!
Guess what, the issue is still not fixed in the GM on two of my Macs. Case closed.YUP! and it might not work properly yet
Good picture!
Best bet is to revert to Mavericks, which is tricky.
On a working computer. Go to App Store -> Purchased tab. Re-download Mavericks.
Stick in a USB drive (8GB) with a Volume "Untitled". Execute the following command:
sudo "/Applications/Install OS X Mavericks.app/Contents/Resources/createinstallmedia" --volume "/Volumes/Untitled" --applicationpath "/Applications/Install OS X Mavericks.app"
Wait several minutes for the command to complete.
Stick the USB drive into defunct Yosemite (broken computer) that is turned off.
Turn on and hold the alt/option key.
Select drive Install Mavericks, which takes you to an OS level utility. Click Reinstall OS.
Happy to continue being on Mavericks because I can connect to the internet.
On a working computer. Go to App Store -> Purchased tab. Re-download Mavericks.
Stick in a USB drive (8GB) with a Volume "Untitled". Execute the following command:
sudo "/Applications/Install OS X Mavericks.app/Contents/Resources/createinstallmedia" --volume "/Volumes/Untitled" --applicationpath "/Applications/Install OS X Mavericks.app"
Wait several minutes for the command to complete.
Stick the USB drive into defunct Yosemite (broken computer) that is turned off.
Turn on and hold the alt/option key.
Select drive Install Mavericks, which takes you to an OS level utility. Click Reinstall OS.
Happy to continue being on Mavericks because I can connect to the internet.
I am sorry yo have a/some problems.
Touching wood for luck
. Since Tiger I have had no connection problems with OS X at all; with three modem/router combinations in excess of 12 machines plus the odd iOS jobby.It strikes me that the problems brought forward on this website seem to be entirely individual in nature and must be incredibly frustrating when so many others just connect and get on with life.
Believe me I am NOT saying it is operator error as I am far more guilty then most of UI stupidity (installing OS eight(8) times on the same machine) but surely there must be some reason(s) for these outstanding problems that a relative few seem to suffer.
Before I am jumped on ,'few' is a relative measure.
It just seems that if the majority of OS & iOS users had such problems with their wifi connection then the software would be receiving a huge boot up the bum to put it right - yes?
But from what you are saying it has not.
So why is that so. I very much doubt that Apple or any large software producer is just ignoring it. That would be contra productivity in the extreme.
I am forced to conclude that problems like these are based in the individuals set up. I do not know the how or the why of each case nor do I pretend to be some guru but if all the solutions offered daily on a site like this cannot solve the problem or at least point the way to a solution then the the solution is not available to them but only to the source of the complaint; the individual operator and the individual system concerned.
One lie! My only connection problems have been on public wifi sources where even rebooting after setup has failed I give up and go somewhere else if possible. I think most of these places are in areas of high wifi density with 5+ local wifi setups competing for space.
Just a few thoughts.
Regards
Sharkey
I had the issue after the upgrade from Mavericks to Yosemite. After two clean installs, I gave up and eventually after perhaps the second or third update, it was fixed.
It was annoying enough that I know when El Capitan gets a general release, I'll wait a couple weeks to if anything is broken. (I already the beta though and didn't have issue.)
It was annoying enough that I know when El Capitan gets a general release, I'll wait a couple weeks to if anything is broken. (I already the beta though and didn't have issue.)
Were you running the apple wifi tool that monitors for wifi issues? What did it say.
Probably doesn't make you feel much better but I have the same issue.
And actually El Capitan GM makes it even worst. I now have the infamous message "no wifi hardware installed". Takes about 3 to 5 restarts to make it work again. Issues with wifi started with Yosemite and stopped with one of the Yosemite Updates. Sadly I don't remembered which one. But I almost forget about it since it worked fine for a few Weeks without any wifi hick-ups. Until the following update brought back all the headaches. I have an old mid 2010 Macbook Pro, but since it worked perfectly with that one Yosemite update I don't think it's a faulty wifi-card. Also the apple support forum is full with people having very similar issues.
I'm thinking of buying s usb wifi adapter. I don't want to trash my otherwise still perfect working Macbook
I've never had wifi issues...
Sometimes I wonder how many people really have this. You never see it mentioned in reviews or tech sites. It's pretty much just talked about on here yet some would like you to believe it's a widespread issue...
Maybe it's dependent on your network?
Sometimes I wonder how many people really have this. You never see it mentioned in reviews or tech sites. It's pretty much just talked about on here yet some would like you to believe it's a widespread issue...
Maybe it's dependent on your network?
I have this problem on my 2011 11" MBA but my 2010 15" MBP is fine. It is a persistent issue which I am surprised Apple hadn't fixed by now. Clean installs didn't do anything to fix it. It takes about 5-7 seconds to reconnect to WiFi whenever it goes to sleep. I've tried different settings but problem persists. It's an annoyance but doesn't prevent one from using their machine. Though I agree this really is something Apple should get to sooner than later.
And re: a widespread issue, only a small percentage pf people have had access to El Cap so far, mostly developers and people who know how to deal with Beta releases. I haven't complained on the forums because well..beta and I report these bugs to Apple as we're supposed to do. Meaning just because it's not being discussed to death here, doest mean it isn't a bug that needs attention.
But having installed the GM version they made available to people on the beta and seeing that it hasn't been fixed isn't good. You'll see more instances once it is released publicly worldwide.
EDIT: I see some people had this issue in Yosemite. I have only seen it in my MBA since I started w/ the El Cap betas. My MBA was fine on Yosemite.
Last edited:
Another user checking in verifying the problem does indeed happen.
In my case in one room I have the following computer in use at various times
2014 Retina iMac Yosemite
2012 Macbook Air Mountain Lion
2012 Mac Mini Yosemite
2014 HP Pavilion
The auto connect wifi issue only happens on the 2012 Mac Mini Yosemite and it happens a lot. Side note: its hooked up to my TV but it's literally 4 feet from my router.
Interestingly enough, I didn't have this issue. Then I installed the Gold Master, and now it's happening all the time and annoying the hell out of me.
Just as a matter of interest. How many 'sufferers' have multiple wifi using bits of kit; high density of electrical equipment that also uses radio signals; multiple electrical appliances and are using auto 2.4 to 5.0 Mghz on their hubs? In other words is there a correlation between high electronic radio density and variable performance. Only time I did have a problem at home the cure was to simply only use 5.0Ghz on all OS X and iOS equipment. Only a thought.
I doubt this matters as I have 2 machines in the same room. One is affected, the other is not. Proximity to my Airport doesn't make a difference either.
The counterpoint is why would 1 computer have the issue and other ones wouldn't that are located in the same room. If my Mac Mini goes to sleep i it doesn't auto connect while i have an iMac 7 feet from it that never has an issue, or does my Macbook Air in the same room, or does even my iPhone and work laptop which is a HP model.
Heyo!!! I installed the 10.11.1 update and WiFi connectivity seems to be holding on my MacBook Air. I've put it to sleep a few times to test and seems fixed *fingers crossed*. Hoping it holds and that the others experiencing this issue get it resolved soon with an update.
UPDATE: Nevermind. After an overnight slumber, the MBA still has issues connecting to WiFi on wake.
UPDATE: Nevermind.
After an overnight slumber, the MBA still has issues connecting to WiFi on wake.
Last edited:
Just to be the devils advocate here.
Are your macs all set to 5Ghz?
Do you have a lot of electrical(not necessarily electronic) stuff in your house/room?
Have you set each machine up for fixed 5Ghz usage the machine AND on the router?
All "granny sucking eggs" I know. But! I have said before multi-band routers mac or others if left to themselves can and do get mixed performance in the situations I describe. It has been my only experience of this sort of thing using a 3rd party 2.4/5Ghz router with MacPro/MBP/MB Air/iPhone, third party mobile and home phone with 5 receivers.
Problem solved by only using 5Ghz for all Mac stuff and leaving 3rd party equip on 2.4Ghz. Eventually using a more powerful router with good setup (as before) made the whole thing solid.
If all is set up OK I give in
Are your macs all set to 5Ghz?
Do you have a lot of electrical(not necessarily electronic) stuff in your house/room?
Have you set each machine up for fixed 5Ghz usage the machine AND on the router?
All "granny sucking eggs" I know. But! I have said before multi-band routers mac or others if left to themselves can and do get mixed performance in the situations I describe. It has been my only experience of this sort of thing using a 3rd party 2.4/5Ghz router with MacPro/MBP/MB Air/iPhone, third party mobile and home phone with 5 receivers.
Problem solved by only using 5Ghz for all Mac stuff and leaving 3rd party equip on 2.4Ghz. Eventually using a more powerful router with good setup (as before) made the whole thing solid.
If all is set up OK I give in
Just to be the devils advocate here.
Are your macs all set to 5Ghz?
Do you have a lot of electrical(not necessarily electronic) stuff in your house/room?
Have you set each machine up for fixed 5Ghz usage the machine AND on the router?
All "granny sucking eggs" I know. But! I have said before multi-band routers mac or others if left to themselves can and do get mixed performance in the situations I describe. It has been my only experience of this sort of thing using a 3rd party 2.4/5Ghz router with MacPro/MBP/MB Air/iPhone, third party mobile and home phone with 5 receivers.
Problem solved by only using 5Ghz for all Mac stuff and leaving 3rd party equip on 2.4Ghz. Eventually using a more powerful router with good setup (as before) made the whole thing solid.
If all is set up OK I give in
Good, advice. I'm happy that Apple switched back to mDNSResponder.
I (a CCNA) know you're being general here, but that's not necessarily the case. I've seen my 2015 rMBP wake from sleep and have APIPA addressing, which points to a DHCP failure, BUT the 2015 rMBP is the ONLY device in my household -- and I run a heterogenous combination of Windows, Linux, OS X, and iOS devices -- which fails to get a DHCP lease on wake and defaults to APIPA addressing. Most maddeningly, failure to get a DHCP lease isn't the only way in which my rMBP's wifi fails upon wake from sleep: sometimes it still has a routable (behind PAT) IP address, and I can still ping my router, yet I can't ping anything outside the LAN, i.e. 8.8.8.8 or 8.8.4.4, whether by IP or domain name; sometimes I get the former problem and I option-click the wifi menulet and Internet is listed as "Reachable", other times "Unreachable". The only thing about my rMBP's wifi that consistently works upon waking from sleep is that I can ping localhost, i.e. the Mac is still running the TCP/IP stack. Beyond that, it's all a crap shoot, and I've been pulling my hair out trying to fix the problem. Oh, and sometimes it goes away for a few weeks, only to reappear without any configuration changes.
Sorry to rant a bit here, but I had hoped that the El Capitan release would fix the problem, and it didn't, so I'm once again googling for ideas on how to fix a problem that I as a network engineer have spent months working on. I won't name names, but the defensiveness of a number of the posters in this thread -- that it couldn't POSSIBLY be an OS or firmware bug that Apple is responsible for because they personally haven't experienced the problem -- made me feel disposed for a rant.
Oh and the same problem existed on the 2015 MacBook I had for 10 days or so before exchanging it for the rMBP, so if it's defective hardware, as some have suggested, then Apple's supply chain has some serious quality control issues.
Last edited:
I would posit that you're reading the wrong tech sites then. A cursory google search reveals a lot of ink spilled over the issue. Examples:
http://osxdaily.com/2014/04/24/fix-mac-disconnect-wifi-sleep/
http://blog.chron.com/techblog/2015/06/fix-for-os-x-yosemite-wi-fi-problems-is-finally-on-the-way/
http://www.gottabemobile.com/2014/12/05/apple-rushing-to-fix-os-x-yosemite-wifi-problems/
http://arstechnica.com/apple/2015/0...h-a-pile-of-security-privacy-and-wi-fi-fixes/