Mac users running macOS Tahoe have reported for months that their audio cuts out, freezes, or disappears completely. Threads on Apple’s own community forums have documented this problem since the update’s early builds.
This issue isn’t confined to a single setup or app type. Musicians using plugin synths suddenly lost sound, video editors experienced audio dropouts mid-session, and some users even found their entire Mac unresponsive when the bug hit, with Sound and Bluetooth settings locking up too.
Reports have persisted since Tahoe’s initial release. The issue is still present in version Tahoe 26.5.1, which suggests it’s not a simple glitch a quick patch will fix.
A Bug That Outlasted Several Updates
This audio issue really stands out because it just won’t go away. Reports on Apple’s developer and community forums go back months.
One user triggered the sound issue while running Spotify in lossless mode and simultaneously playing a resource-heavy game. Others noticed the issue tied to specific workflows, like MIDI routing losing its configuration after an update, or native software instruments crashing audio output mid-session on setups that never had problems before.
These varied triggers suggest a deeper problem with the audio subsystem, not just a narrow driver conflict. When a bug appears in music production, gaming, and even everyday playback, the root cause usually lies deeper in the system. It’s likely rooted in the macOS layer that handles all audio streams, rather than in any specific application.
Why System Updates Break Audio This Way
CoreAudio, the framework handling every sound a Mac makes, gets affected by nearly every macOS update. This happens even when Apple’s release notes don’t directly mention audio changes. A shift in how the system manages background daemons, permission entitlements, or driver loading can unexpectedly impact audio, even if it has no obvious connection to what the update was supposed to fix.
This helps explain a pattern several users have noticed on their own. For one person, switching to Low Power Mode fixed the problem. Another user found the issue tied to specific app combinations, not just the update itself. These observations point to a resource or process conflict stemming from changes in how Tahoe manages background tasks, rather than just a broken driver.
Third-party apps that manage their own audio routing add another wrinkle. Bug reports on Adobe’s tracker, for instance, describe Premiere Pro losing audio output specifically when Bluetooth devices are active. Yet, system audio keeps working fine outside the app. Reconnecting the Bluetooth device usually fixes it. This hints that the update changed how macOS hands off audio state to these apps, rather than breaking Bluetooth itself.
First Steps to Try
Most people can fix this audio issue with a few simple steps that don’t involve touching system files. Here’s what to try first:
- Go to System Settings > Sound > Output. Sometimes, updates switch your audio output to a disconnected display or a Bluetooth device that isn’t even paired.
- In Activity Monitor, search for “coreaudiod” and force-quit it. macOS will restart the process on its own, and this simple step often clears up many audio problems.
- Give your Mac a full restart instead of just putting it to sleep and waking it up. Only a complete reboot reinitializes all background audio processes.
- Try disconnecting and then reconnecting your Bluetooth audio devices. This is especially helpful if the problem is confined to a specific app, like a video editor or DAW, instead of affecting the whole system.
- If you’re on a MacBook, switch Low Power Mode off and then back on. One reported case linked the audio issue to power management changes from an update.
These tips resolve the issue for most users. If they don’t work for you, the solution probably involves more than just changing a setting.
When the Basics Don’t Fix It
Persistent issues, especially MIDI configuration resets or plugin instruments going silent, often happen because of corrupted preference files. An update might have written these files incorrectly or didn’t migrate them cleanly from the previous macOS version. macOS keeps this configuration in property list files within the Library folder. If you clear out the ones related to Core Audio, the system will then rebuild them from scratch on the next restart.
This step carries real risk if the wrong file gets removed, since Library folders hold configuration for far more than audio alone. This guide to fix Mac sound not working walks through exactly which files to target and in what order.
What This Means Going Forward
Bugs like this usually clear up through point updates, not a single dramatic fix. Apple released several Tahoe updates since the issue first appeared, but none have fully fixed it. If you’re affected, keep macOS updated. Audio problems from one release often get at least partial fixes in the next point release, even if they aren’t mentioned in the changelog.
To get reliable sound back quickly, start with the basics: check your output device, restart Core Audio, and rule out any app-specific conflicts. Don’t immediately assume a deeper system file is the problem.
Musicians and video editors using specialized audio software should also keep an eye on app-specific bug trackers. Sometimes, what seems like a macOS issue is actually a compatibility gap between the update and third-party tools that hasn’t been addressed yet.
