Q: OSX Yosemite Wifi issues

A workaround that has worked for me was to turn personal hotspot in my iPhone and connect my MBP to that instead of my usual wifi SSID. Of course my iPhone is the one that is actually connected to my local wifi.  The first page that I browse to would take a bit longer to load but afterwards its as if I'm directly connected to my wifi in terms of speed.

Trying to understand if I got that right. So, your iPhone is connected to the wifi router and you share the internet connection with your macbook. Is it correct?

Could  you tell me please, how you do it? I do know that it is possible to share 3G or 2G mobile-internet using so called "Personal Hotspot" that may appear if you type something in a "username"field which is in Cellular Data Network -> Personal Hotspot. But I dont know how I could share the WiFi connection using only WiFi-internet on my phone without any cellular data traffic.

May I ask you to tell me what and where I should press to activate this wifi-sharing?

Solved the problem by down grading my 2014 MacBook Air back to OS X Mavericks. 

I'm tempted to do the same to be honest, but with a fix hopefully due in the next couple of weeks (Apple has history of releasing a .1 1 month after), is it worth the effort?

If 10.10.1 doesn't work, then I will be rolling back.

I just want to register here that I'm having the same issues as everyone else, however, only on on my late-2012 iMac.  I also upgraded my 2014 rMBP to Yosemite and the WiFi has been working fine on that machine.  I even have Handoff working between my iPhone 5 and the rMBP without issues.

That being said, both have been having Bluetooth issues, so I'll add my vote to the theory that Bluetooth is part of the problem here.  On both machines I use an Apple BT keyboard and BT Magic Mouse (different ones for different machines).  Sometimes on both machines, my mouse and/or keyboard will go haywire (slow response, pointer jumping around, ghost keys getting pressed).  Doesn't happen too often on the rMBP, but this started happening like crazy on the iMac at roughly the same time the WiFI issues started. 

I've been an Apple user for almost 30 years and although the OS keeps getting better in terms of features, it also gets more and more buggy with each release.  It's really disappointing that something as fundamental as WiFi/Bluetooth (in this era of computers without Ethernet ports!) would be buggy in Yosemite.

This needs to be fixed.  It's pretty ridiculous.

Fortunately, I have an Ethernet powerline adapter setup in the house, so I was able to turn off the WiFi in the iMac and connect to my router via Ethernet (over powerline).  So far (an hour or so), no drops in connection. 

And also no Bluetooth funkiness with my keyboard or mouse!  That being said, I also turned off the Handoff feature at the same time, so the Bluetooth stability might be due to either Handoff or WiFi.  And of course I want to use the Handoff feature (a major reason I upgraded to Yosemite in the first place), so this is less than ideal.

If something changes, I'll update here.  I really appreciate those who have posted various fixes and have been in touch with Apple.  Come on Apple; I'm hoping you listen to your customers here...

I'm sure they will come up with a fix but the question is when.  This is not happening to everyone, if it was they would have millions apon millions of complaints and would be all over the news.  Going forward I will definitely question any updates they provide before downloading, Ipad updates are on revision 3 with 8.0.1, 8.02. and 8.1 all not working. 

Exactly the same for me. At work with some random router connection drops. Disabling and re-enabling wifi sometimes does the trick, but not always. Rebooting OS X sometimes does the trick, but not always. At home I have a Airport Extreme and no issues at all.

When as you said being the operative word. I am literally on the verge of tears all day, as I have clients waiting for drawings, and no way to communicate with them. Deadlines that come and go and I am powerless to do anything about it. October is my busiest month of the year, and carries me through when things slow down to a crawl in the summer. (Event industry)

I really cannot carry on like this much longer, but all of my software is for the Mac and it would be impossible for me to replace it all for a PC. I am at my absolute wits end.

I am not sure why I'm bothering to continue to post here, after 3 separate calls to AppleCare, that resulted in no real fix. Even though there is 47 pages of posts here, and news articles detailing the problem and creating click bait with, here are the fixes, Apple is still silent to the issue. But I will provide some additional details that might help if somebody over there is actually paying attention.

I rolled back to Mavericks after 5 days, none of the 30 different fixes helped, because they only seemed temporary, after a reboot or a sleep, the Macbook would  go back to only staying connected (although displaying still connected just fine). Ive been back on Mavericks for a week, and not a single issue to speak of. Works flawlessly.

Shortly after the Yosemite release and press conference, my girlfriend ordered a brand new macbook pro from Apple. She wanted to wait until after the announcement to make sure she wanted the pro instead of the iMac.

The laptop was delivered yesterday, brand new out of the box, with Mavericks installed. Worked great. We discussed that if she wanted to make the jump to Yosemite she should do it without making too many custom changes to the machine because I really had my doubts it would work after the upgrade.

Last night we upgraded to Yosemite, and after about 10 minutes, THE EXACT SAME BEHAVIOR as my 1 year old Macbook Pro. This machine was 2 hours old out of the box, and not tainted with any other software, it was simply placed on the wifi network. Which really has me believe that the problem is not with the local machine, but rather with the machine interacting with the wifi router/gateway in the house, it is the only common piece between 2 completely separate machines.

I am running a Netgear R7000, and have 34 other devices on the wifi (that is not exaggerated number its actual) and the device is running the most up to date firmware. I am 100% confident the issue does not lie with the router, but what I do find in reading a lot of these posts, there have been a few people that have gone out and bought airports and they work just fine. So I am throwing out there that no matter what everyone keeps trying with these hacks to clear this out and reset that or turn bluetooth off this, run this crap tool here. That those who are still fighting with this issue, and like me, have tried all those fixes while still wasting time here on this board hoping for something new fix we haven't seen yet, that it has to do with the interaction of your wifi device, and your Yosemite install, and until Apple acknowledge it and comes out with the fix, I feel we are all wasting our time.

I rolled her brand new computer 4 hours out of the box back to Mavericks last night. She's been using it all day without a single care about wireless connections.

Just registering that I am have Serious WiFi issues with my Yosemite upgraded 2013 MBP, but only when I am at work. Doesn't drop at home. I have been trolling this and related threads, and have tried most everything I have seen posted. Nothing seems to stick. IT at work "doesn't support Apple products" so I am on my own to find a solution. Still waiting for Apple to officially chime in...

I got excited a couple of minutes ago, App Store was showing 1 update.....

Disappointment came when I found it to me Remote Desktop.

If Apple keep to the schedule, the we have 2 more weeks of **** before there's a possible update released, that may or may-not fix the problem.

I did a clean install of mavericks and updated to Yosemite....install all applications one by one..and my wifi worked for 5 hours..again the same issue...it really *****.....!!!!!!!

At least there is a positive, you can't be hacked or catch a virus, as you can't remain online long enough for anybody to do any damage.

I guess I'm just trying to get this out into the record as to my experience:

I can connect fine to a wifi hotspot mobile device (my work Windows Phone)...I can keep a constant connection. It works great.

My wifi at home, stinks! Drops every few seconds. Have to reconnect. I had a "wake from sleep" connection issue with Mavericks, but just thought that was how it worked...didn't realize that was a bug...other than that, never had one issue with Wifi on Mavericks.

The "Looking for Wifi" or whatever is always running even when connected to a network..so there obviously is some type of recognition thing which the problem then the connection times out and disconnects.

Funny thing is though, at home, sometimes, I um, download large files from the internet...um...and well, when I do this, i can download for hours. So, as long as data is moving, the wifi maintains. But if I'm just browsing the internet, and stopping to read...then, it drops.

So, in summary...

1) There was a bug with Mavericks for me where wifi would drop when the laptop was sleeping (I lived with it though).

2) Wifi connected to my mobile device hotspot works fine it seems.

3) Wifi connected to my home router drops when there is no data being sent downloaded/uploaded.

4) Wifi connected to my home router keeps my connection when i have a large file being downloaded and there is a constant stream of data passing.

I've tried all the fixes and none work. This really is a bummer. Its the first issue that is a make-or-break issue for me that I've had in my Apple relationship that goes back to the Apple IIe...But mainly picked up again with the original iPhone. I'm all Apple now, multiple laptops, iPHone 6 Plus, 5, 4. Ipad Air...shame.

I love my apple, but please do fix this...or at least just tell me how to fix this. It is a problem and it did start with Yosemite..It's real and I hope there is a solution soon.

Thanks!

I found that having my macbook pro plugged in to a power source (not an ethernet cable) fixes the issue...