Why Mac audio sounds quiet after a macOS update

Published September 15, 2026

A·12 Guide
SAME TRACK, QUIETER AFTER THE UPDATE0BEFORE UPDATE0AFTER UPDATEdBFSA stricter output limiter or a reset device selection can hold a Mac well below its previousloudness.

You update macOS overnight, open your Mac the next morning, and the same song that used to fill the room now sounds thin, even with the volume key held down at maximum. Nothing about the file changed, and it’s the same speakers or headphones as yesterday. Something in the chain between the app and the output reset itself during the update, and it is worth knowing exactly what.

What an update actually resets in Core Audio

macOS treats audio output as a small stack of settings and services, and an update is free to rebuild parts of that stack without telling you. The two changes that most often show up as “my Mac got quieter” are the output device selection and the state of any driver sitting in the audio path.

Every time coreaudiod restarts, which happens automatically after most updates, macOS re-enumerates every available output and picks a default. If it doesn’t immediately recognize your USB DAC, audio interface, or a paired Bluetooth device, it falls back to the built-in speakers, which are quieter and thinner by design. You keep pressing the volume keys because the level bar looks unchanged, but you are now listening through a different, weaker output.

The second change is stricter. A HAL audio driver, the kind that sits between an app and your hardware to add processing, runs as a system extension. macOS gates that class of extension behind an explicit approval in Privacy & Security, and a major version update can reset that approval or leave the driver’s helper process unloaded until you reopen the app that owns it. When that happens, audio falls back to a plain, unprocessed path, and any boost or EQ you had dialed in silently stops applying.

WHERE AN UPDATE CAN BREAK THE CHAIN01APP02OUTPUT DEVICE03DRIVER APPROVAL04SPEAKERScoreaudiod rebuilds this path after almost every update. If the middle step drops out,everything downstream reverts to a plain signal.

Getting your volume back

Start with the most obvious explanation before anything else: check which output device is actually selected. Open the Sound pane in System Settings, and if it shows something other than your usual speakers or headphones, switch it back manually. This alone accounts for most “quiet after update” reports.

Check Reduce Loud Sounds. macOS has a built-in limiter for headphone output, and its setting can change during an update. Open System Settings, go to Sound, select your headphones under Output, and look at the Reduce Loud Sounds control. If it is on and set aggressively, it will cap peaks well below what you are used to, no matter how high you push the volume slider.

WHAT A TIGHTENED LIMITER DOES TO LEVEL0BEFORE UPDATE0AFTER UPDATE, LIMITER ONdBFSSame file, same volume setting. A stricter peak limiter can hold the whole track well below itsold level.

Restart coreaudiod. This is the free, general-purpose fix for stale audio state on a Mac, update or not. Open Terminal and run sudo killall coreaudiod. The audio service restarts within a couple of seconds, and every app that was playing sound needs to be reopened or refreshed to reconnect, but it clears whatever leftover configuration the update left half-applied.

Re-approve any audio driver you use. If you run an audio interface, a virtual output, or a system-wide processing tool, check System Settings under Privacy & Security for a pending approval banner. Updates sometimes revoke that permission silently, and until you click allow, the driver is not in the signal path at all.

Check Bluetooth headphones separately. AirPods and other Bluetooth headsets store their own volume offset per device, and a firmware or codec renegotiation after an update can reset it. Forgetting the device in Bluetooth settings and re-pairing it resets that offset cleanly.

PER-DEVICE VOLUME MEMORY020406080100%80Speakers45AirPods70HDMI

Doing it with ZonaReq

ZonaReq’s driver goes through exactly the approval process described above, since it is a Core Audio HAL driver and macOS treats it like any other. If your boosted or equalized audio quietly reverted to plain system sound after an update, this is where to look.

  1. Open System Settings, go to Privacy & Security, and check for an approval prompt for ZonaReq’s driver. If the update reset it, allow it and restart when macOS asks.
  2. Open ZonaReq and confirm the output device shown in the main panel is your actual speakers or headphones, not the built-in speakers macOS may have defaulted to during the reset.
  3. Reselect your EQ preset or boost level once. Settings persist between launches, but after a driver reinstall it is worth confirming the chain picked them back up rather than assuming it did.
  4. If the level is still capped, go back to System Settings and check Reduce Loud Sounds under Sound. That limiter sits after ZonaReq in the chain, on the real output device, so it caps the boosted signal the same way it caps everything else.

What this doesn’t fix

None of this, including ZonaReq, gets around Reduce Loud Sounds if you leave it on, and it shouldn’t. That limiter exists to protect your hearing at genuinely damaging levels on headphones, and disabling it to chase loudness is not a trade worth making as a habit. If your Mac sounds quiet after every single update, the more useful fix is procedural: check the output device and the limiter first, before reaching for any third-party tool.

Keep reading

Try ZonaReq free.

Start with the free version — a 3-band EQ with 5 presets — and unlock the full toolkit whenever you want. macOS 14+, notarized, zero telemetry.

Z·01 Blog by email

Get every guide and story in your inbox.

Guides for your Mac, stories about how records were made and how to listen to them, honest gear advice. One or two emails a week, nothing else.

Confirm your email and one month of ZonaReq Pro for one Mac is on us.

We will send one email to confirm your address. You can unsubscribe from any email. More in the privacy notice. Privacy notice