One of Apple’s focuses with the recent 10.10.2 update was for Wi-Fi reliability; however, given that in doing so Apple adjusted the code for its Wi-Fi services, some systems that had stable Wi-Fi connections before the update might now experience problems. In addition, as with any update, sometimes those with ongoing problems may see them persist. If you are experiencing Wi-Fi problems after updating to OS X 10.10.2, then there are some things you can try to stabilize your connection.
General “blind” approaches
These routines are general and non-specific approaches for addressing many problems in OS X, where they may or may not help, but they can’t hurt to try. They also will address problems without changing too many settings:
- Reset hardware settings on your system, including the PRAM (see here) and System Management Controller (see here).
- Restart in to Safe Mode (hold Shift at startup), and then restart normally again.
- Run a permissions fix on the boot drive using Disk Utility.
- Disable any security software, including the OS X firewall in the Security system preferences.
- Restart your router, and update its firmware, if applicable.
OS X supports separate network configurations in profiles called Locations, so you can use this to create a new Location to bypass some possible configuration errors with the current one. To do this, open the Network system preferences where you will see a Location menu at the top of the preferences pane. In this menu, select Edit Locations and then click the plus button in the drop-down panel to create a new location. Call it whatever you want, and it will be populated with the system’s default hardware network ports (Ethernet, Wi-Fi, FireWire, etc.). Click the Wi-Fi port, and ensure it is on and connected to your preferred Wi-Fi network. Then click Apply to save your changes.
Another setting you can try adjusting is your Wi-Fi’s Maximum Transmission Unit size. Networks send data in small separate packets, and this is the maximum size that will be sent for each packet. If for some reason your router and other network hardware is not accepting the default packet size of 1500 bytes, then trying another smaller value may help. To do this, select the Wi-Fi port, then click the Advanced button. In here, go to the Hardware tab and select Manually from the Configure menu. Then select Custom from the MTU menu, and try one of the following packet sizes: 1456, 1453, 1492.
For each of these sizes, click OK and try accessing network services and the Internet to see if your Wi-Fi connection is more stable. Note that by reducing the packet size with a smaller MTU setting, you will increase your network overhead (network throughput used for headers and other non-data communication); however, unless you need maximum performance for computer-to-computer communication on your local network, then a difference of under 50 bytes for the MTU setting will not be notable, especially if it stabilizes the connection.
Rebuild your Mac’s entire network configuration
While changing your network location will apply new settings to your Mac’s network configuration, it still uses the same configuration files and does not replace them. To fully reset your network configuration, go to the Macintosh HD > Library > Preferences > SystemConfiguration folder, and then remove the following files. Note that when doing so you may have to authenticate to delete these files or move them out of the SystemConfiguration folder, and when done you will need to re-visit the Network system preferences to set up your locations and Wi-Fi settings again, but hopefully this wil clear your problems.
Would any of these “fixes” work for the text lag in typing in Apple Mail?
You too? I get even worse lags on IOS8..I believe it is in part due to bad uplink and down links to the Apple server as your texting is being read for spell errors and so forth and is this a two way highway..or it sounds like..a country lane.
“Restart in to Safe Mode (hold Shift at startup), and then restart normally again.”
I believe that restarting normally after the login prompt of safe boot does the trick. I mean, not need to login as safe mode. Right?
It’s nice, I suppose, that there are some strategies that may work to restore WiFi reception to OS X 10.10.2. These could help some desperate users who too quickly migrated their systems to Yosemite and have no easy way back – that is, no viable backup. I could repeat how foolish that approach was, but that’s water under the bridge at this point. However, the question remains, why should they have to try one fix after another, with no notion that any of them might actually work?
A more straightforward and less problematic solution would be a clean install of Yosemite. Test that install to see if it works with your router/network configuration. If it does, then you know that something from your previous version of OS X is conflicting with the new one. You could gradually reinstall your software. If at some point WiFi breaks again you will have a better idea where the conflict lies. Apparently finding that something is what’s plaguing Apple at this point because there are certainly way too many possible variations for Apple to test them all. Apparently their ongoing beta program has failed to find many of them as well. Indeed, the variety of conditions under which the problems occur indicates that it was Yosemite that is, in some as yet undiscovered way, incompatible with earlier versions of the operating system – and/or software that people commonly run thereon.
This is hardly the first time that an OS X update or upgrade has broken WiFi reception for some people. But this is clearly the worst it’s ever been and the longest it’s taken Apple to fix it. It appears there is something in the network infrastructure of Yosemite that Apple changed and considers too important to roll back in order to make OS X 10.10 work properly for all its users. Indeed, this could be the crux of the problem. Apple might know what’s wrong but is unwilling to do what’s necessary to fix it. So they’re trying workarounds that just aren’t doing – and may never do – the job.
By the way, my clean install of Yosemite works fine with the WiFi setup on my 2014 iMac. But that’s on a test partition, not on my everyday working system. I’ve only installed some third-party software on the test system, primarily those programs I use that have been Yosemite certified. I could test the Yosemite upgrade on a copy of my Mavericks system, but I don’t need Yosemite badly enough to make the effort. In fact, I don’t “need” it at all. The knowledge that Yosemite is still broken for an unprecedented number of users does not encourage the effort. I’ll no doubt make the move when OS X 10.10 truly is fixed, as determined by a consensus of those currently having trouble with it. But certainly not before then.
And I will continue to advise everyone I know to avoid Yosemite, just as I advise them against Windows 8. Perhaps we’ll have to wait for OS X 10.11, just as Windows users are waiting for Windows 10 – a sad prospect indeed. Microsoft and Apple have finally achieved true parity – with a botched version of their respective operating systems.
Sorry for the rant. But what else can one do? The situation seems so intractable.
Did a complete format and reinstall on my 2014 MBP. The wifi problems still persists.
I have a new Macbook Pro retina and updated to Yosemite 10.10.2 as soon as it was available and found it to make my wifi issues worse. I found this page and did the PRAM reset. I’m pleased to say that after a day of work it seems to have solved the issue! Thanks!
I had wifi issues with our 2 macbook pro’s 2009 with the wifi dropping off or not connecting after booting. The only fix that worked was to disable the 5ghz in the settings. BT Homehub’s 4 & 5.
Can you please guide me step by step, I encountered with the same issue and gave up on Mac. Then I found this new OS 10.10.2 but still disappointed me. It’s the same from 2009 what a coincident ! The wifi showed No hardware installed. T.T.
March 10th 2015, huge issue after 10.10.2 Yosemite upgrade, the wifi… totally wrecked. Apple’s implication on this issue is a must do!
This situation is intolerable, to have to resort to ‘fixes’ to get a delivered system working is rubbish. Here we are looking to find a solution to our individual problems, while Apple is staying quiet.
The solution, bombard the media with descriptions of the inability of Apple to fix this.
Compromise the share price, then we might get service. And for info, I bought my third MacBook last week, and on 10.10.2 it is stand alone, no wifi connection.
Shades of MS !
Running a Macbook MacBook Pro (Retina, 15-inch, Mid 2014) with a Airport Time Capsule and have no problems with WiFI. No problems backing and also have iPhone connected to it as well when in the office. At home have it connect to a Airport Extreme that at times has a MacBook Air, Macbook 17″ and the MacBook Pro (Retina, 15-inch, Mid 2014) connected to it and still no issues.
Running an IMAC (21,5 Inch, Late 2013). After having upgraded (only today – hoped that issues would have been solved by now…my wifi speed is horribly slow! My EPSON printer is not working any longer and my attached (via wifi) Synology NAS is also useless! Thanks APPLE! Put too much work in developing the I-watch???
Thanks Topher, the suggested chnage of the Wi-Fi’s Maximum Transmission Unit size did the trick. My Epson printer is working again on wireless. Wish everythign could be solved so easily…
Still having issues. For the first time I am starting to hate Apple. Tried everything, wifi keeps getting OFF. There should atleast be an option to go back to previous OS (maverick). I am stuck now with useless mac book pro
Which one is better..?? OS X Yosemite or OS X Maverick..??
I DIDN’T have any WiFi issues until my 2012MBP updated to 10.10.2, now it can’t connect to my regular or 5G home network despite trying numerous “fixes”. Not the end of the world because I mostly keep it at a work station and can use ethernet, but this is absurd. I knew immediately this morning when my 3 year old $50 smartphone was having no trouble connecting to the network that this was a Yosemite issue.