Wi-Fi is unstable after macOS Tahoe update on MacBook Air

I tried everything said here even set static IP for my devices but both my iPhone SE 2020 and my. Mackbook Air 2020 M1 are having problems with my home wifi...

Is there any other fix I can try?

I'm still keeping a close eye on this thread. It is unbelievable to me that this type of regression exists, but it's very present for me and very painful to work with at times. I SSH into a number of devices in my home for various reasons and the latency and packet loss makes that experience maddening.

Not sure what more to try at this point. I'm presently testing with 5Ghz disabled across the four APs I have in my home. Wondering if the same behavior still occurs on 2.4Ghz. Shows how desperate I am for a fix, I suppose.

FWIW, this is my machine:

- **Model Name**: MacBook Pro

- **Model Identifier**: Mac15,9

- **Chip**: Apple M3 Max

- **Memory**: 48 GB

- **macOS Version**: macOS 26.2 (25C56)

Have you updated to Tahoe 26.2 today. Not that I think it will help the problems you are having since it is beginning to sound more like a faulty hardware problem. Hardware does fail on Mac's like on anything that man builds. On a old Mac I had some years ago the Bluetooth module went south on me.

I would suggest that you first download EtreCheck and run it to see if it can find anything wrong with the Mac

. It's free to use. https://etrecheck.com/en/index.html. Here is a link written by some with a lot knowledge about using it. Once you have run it you can post the results (In Etrecheck, click Share Report > Copy Report,) to a comment

Crazy — I had the exact same issue after updating to macOS Tahoe. My Wi-Fi would constantly cut out and sometimes wouldn’t detect any networks at all. I ended up factory-resetting my 2019 MacBook Pro back to macOS Catalina, which meant wiping everything on my laptop (super upsetting), but once I did that my Wi-Fi worked perfectly again with no issues. So I’m guessing the new update has some kind of glitch.

SO, in even MORE annoying news, here's my latest attempt at a fix:

• create a new APFS container on internal SSD & install Tahoe 26.2
• set up "as a new mac" and then use Migration Assistant to bring over ONLY the affected user account, not the Applications folder or anything else

Problem still persists, exactly the same stupid behavior. So it's a user account issue that persists across volume migration.

So the only possible solution I can think we're left with is to create a fresh new user account and manually transfer over every single thing, which I'd very much rather NOT do, that sounds incredibly annoying.

OR to start going through every single random user Library folder and wiping out everything we can in the hope we catch the culprit??? That sounds equally bad.

Does anyone know the best path for getting some higher-level Apple engineer involved in trying to find a fix? I'm envisioning hours of dead ends talking to low-level support / genius bar people telling me to wipe and reinstall my OS for the 10th time.

Similar issues on a 2020 Intel MBP running Tahoe 26.1. Wifi will connect, then drop, reconnect once I select the network, then drop again. This will repeat two or three times after startup or waking from sleep before it seems relatively stable. I updated to 26.2 and the issue is still present, but I didn't see this before 26.1 at all either.

So for me, after having everything switched back on, it worked for about 1 day and then started having the same problem again. So I switched everything back off but it didn't fix right away, then after a restart with everything still off it started working normally...not sure if the settings or the restart made the difference. I'm testing just leaving them all off for now to see if it seems stable long-term. If so I'll start re-enabling things one by one.

It worked fine for a couple days, then I needed to use Airdrop for something so I turned it on to Contacts Only, and left it on to see what would happen. After a few hours the issue came back. I left Airdrop switched on and rebooted, and now it's been working fine for about a day or so. I expect it is likely to come back as long as I leave Airdrop on, but good to know that a reboot seems like a workable temporary fix.

Thank you! Fingers crossed, this appears to be the fix for me as well.