Wifi disconnects after sleep and takes long time to reconnect with Mavericks

We will keep in mind that external adapters may cause wifi issues and that disconnecting them may stop the issues, thanks

AppleIIme wrote:

I have the same problem detailed here and in 20 other threads. Turning off Bluetooth fixes is, but is not a realistic option.

Can anyone here confirm what I see fixes it, which is:

1. Open the lid (the problem occurs, Wi-Fi doesn't reconnect)
2. Turn Wi-Fi OFF then ON via the menu bar
3. Wi-Fi immediately connects just fine

So it seems a simple workaround is an app or script that does as follows:

1. Detects lid is opened/resumed from sleep
2. Turns Wi-Fi off then on

Comments welcomed.

<Edited by Host>

Doesn't fix mine. Can't even click the Wi-Fi on the menu bar, the wheel comes to stay. Taking about 5 minutes to connect/unfreeze at the moment after sleeping/booting. Really really thinking about throwing this from the window and buying a proper computer. Well, its me to blame, since I choose to hit the update button....

we keep in mind that you havent any solutions doable 🙂
I solved by two week at least without $$. 😉

External adapters may cause wifi issue, noise HF.

Hi...

Peter of iMore solved this problem. It posted on the iMore web and this is the link http://www.imore.com/how-fix-mavericks-wi-fi-zapping-bluetooth#comment-form

It just works! 🙂 Thanks Peter Cohen.

This is not a full solution because if you connect a bluetooth device such as a speaker and sleep your mac then unpair the bluetooth device, this issue will occur again when u wake your mac. Try it. Here is what I said about it a few pages back:

2) MEDIUM - Delete the plist and reboot your mac (Open finder, select ‘Go’ at top menu bar, ‘Go to folder’ > Library/Preferences, delete this folder if you have it: SystemConfiguration (if you have it) and this file: com.apple.systempreferences.plist (More info https://discussions.apple.com/docs/DOC-4301)

Test it works: Turn Bluetooth on, close lid, open, and surf web

Disadvantage: Issue returns if after doing this fix, you disconnect a Bluetooth device while the mac is sleeping.

Success Count: 1 ie there is some low confidence that this method works, need more people to chime in

Fail Count: 0

@ andybarton1

andybarton1 wrote:

I've got a mid-2013 MacBook Air that had no Wi-Fi Connectivity problems until recently. I'm on Mavericks 10.9.2.

My issues now is that whenever I start my MBA it really struggles to connect to Wi-Fi - generally I turn off & turn on Wi-Fi manually & this sorts it. But I do have Bluetooth turned on by default as I use an external Apple Trackpad.

So following ths thread, I've turned off Bluetooth & restarted. Miraculously Wi-Fi now connects up instantly.

A pain that Bluetooth has a bug but thahks guys, Wi-Fi connectivity much more important.

I had the exact same problem on my 2012 Macbook Air ever since upgrading to Mavericks, I was so frustrated and I finally called Apple (who knew you get free 90 days support when you upgrade the OS).

Long story short, they told me to:

1) Turn off bluetooth and wifi

2) Navigate to /MacintoshHD/Library/Preferences and delete com.apple.Bluetooth.plist

(take a backup of the file for good measure)

3) empty trash and reboot

This fixed it for me. It's only been 1 day since the fix but it seems to be working normally now. Let me know if that helps.

Thanks for this.

Fixes it for me too.

This fix is mentioned on every page of this thread, and it will not solve the problem permanently. It will re-occur eventually I'm affraid.

Thanks,

At least it's better than continually having to switch Wifi off and on every time my MacBook goes to sleep. Even if its only for a few day!

I've proceeded as you instructed. I feel that the issue has been solved. Many, many thanks.

Thanks, mgorgun

That fixed the problem for me as well. For some reason I had the issue with just one particular Wifi access point, but that was annoying enough. If Apple knows about the issue, why has it not been fixed in a patch..?

@ n808n808

I think Apple has tried to fix it many times over the years. The problem has come and gone with OSX point revision updates, without my doing anything.... so I assume they made some kind of changes to the code. The problem, it seems, is that when they do so, it creates the problem for some other set of users, so obviousily they've never gotten to the core of the problem.

It seems the same this time (from here and vaious other threads). Some saw the problem go away with the 10.9.2 update, while others have appeared claiming the probem appeared after the update. And, IMO, the network stack for OSX has always been a bit problematic, so it's probably a mess of coce they are dealing with.

Steve Wilkinson wrote:

@ n808n808

I think Apple has tried to fix it many times over the years. The problem has come and gone with OSX point revision updates, without my doing anything.... so I assume they made some kind of changes to the code. The problem, it seems, is that when they do so, it creates the problem for some other set of users, so obviousily they've never gotten to the core of the problem.

It seems the same this time (from here and vaious other threads). Some saw the problem go away with the 10.9.2 update, while others have appeared claiming the probem appeared after the update. And, IMO, the network stack for OSX has always been a bit problematic, so it's probably a mess of coce they are dealing with.

This makes sense, since the "fix" proposed didn't work for me. Extremely annoying to wait 5-10 minutes to use the computer everytime it sleeps or reboots. Hopefully Apple can do something in the future.

My situation is somewhat different than most of you given that I'm on Snow Leopard and have an iMac. However, here's how I now avoid the problem...

I set my energy settings to have the computer never go to sleep. At the end of each day I do a shutdown.

That's it. No more waiting for connection. Maybe there's cons to keeping the computer awake, but I'm not going back now that the constant aggravation is gone.

Deleting the .plist file worked for me, too. Thanks!