When an Apollo Twin won’t show on Mac, the fix is usually the Thunderbolt chain, macOS driver approval, or a stuck audio device choice.
When you plug in an Apollo Twin and nothing happens, it feels like the interface is dead. Most of the time it isn’t. The Apollo is powered, but the Mac never completes the data handshake, or macOS blocks the driver after an install. You can fix that faster by testing the connection in a strict order, instead of reinstalling at random.
This guide walks you through a clean, repeatable set of checks. You’ll confirm the cable and adapter path first, then handle macOS security approval, then finish with Console and DAW routing. If your symptom is “apollo twin not connecting to mac”, you’ll hit the common causes early.
Apollo Twin Not Connecting To Mac Fast Checks First
Start here if the Apollo powers on but doesn’t appear in UAD Meter, Console, Audio MIDI Setup, or your DAW. These checks separate a physical connection problem from a driver approval problem.
- Power-cycle the Apollo — Turn it off, wait 10 seconds, then turn it on and let it finish booting.
- Restart the Mac — A restart forces Thunderbolt to re-scan devices and reloads drivers after installs.
- Connect direct to the Mac — Plug the Apollo straight into a Thunderbolt port first and remove docks, hubs, and adapters you don’t need.
- Swap Thunderbolt ports — Try another Thunderbolt port on the Mac, then reboot once more.
- Read the UAD Meter message — “Driver Not Yet Allowed” points to macOS security steps; “No Devices Found” points to cable, port, or compatibility checks.
Universal Audio’s own troubleshooting flow starts with power and connection checks, then moves to macOS security configuration and cable verification. Use that same order here so you don’t chase software while a cable is the real blocker. Source
If you want a quick confirmation that Thunderbolt is seeing anything at all, open Apple menu > About This Mac > System Report, then look under Thunderbolt.
Cables, Ports, And Adapters That Trip Up Apollo Twin
Thunderbolt is not the same thing as “USB-C shaped”. Many cables that fit a MacBook pass power and basic USB data, yet fail a Thunderbolt device. That’s why the Apollo can light up but stay invisible.
Confirm You Have A Mac-Compatible Apollo Model
Apollo Twin Thunderbolt models connect to Mac through Thunderbolt. Apollo USB desktop models are Windows-only and will not connect on macOS. UA states that Apollo USB desktop models are not compatible with macOS in its system requirements notes. Source
Use A Real Thunderbolt Data Path
Check the entire chain from the Apollo to the Mac. One weak link can break the handshake.
- Use a Thunderbolt cable — Look for the Thunderbolt logo on the cable and avoid charge-only USB-C leads.
- Use the right adapter on USB-C Macs — UA notes that Macs with Thunderbolt 3 via USB-C need a Thunderbolt 3 to Thunderbolt adapter for Apollo Twin and Twin MkII connections.
- Flip Thunderbolt 2 ends — UA notes that on Thunderbolt 2 cables, the Thunderbolt logo must face up at both ends or the device may not be recognized.
- Remove hubs and docks for testing — UA warns that many hubs and docking stations can complicate device detection, so remove them until the Apollo shows up.
UA’s Apollo Twin Mac compatibility page lists Thunderbolt port types that work and calls out the adapter requirement for Thunderbolt 3 USB-C Macs. Source
Keep Thunderbolt Daisy Chains Simple
If you run more than one UA Thunderbolt device, connect them in a single chain from one Thunderbolt port on the Mac. UA notes that UA Thunderbolt devices should be daisy-chained from a single Thunderbolt port, and that connecting through hubs can create complications. For troubleshooting, unplug everything except the Apollo and the Mac, get a stable connection, then add devices back one at a time. Source
| Mac Symptom | Likely Cause | Next Move |
|---|---|---|
| Apollo powers on, not listed anywhere | Cable, dock, or adapter issue | Use Thunderbolt cable direct to Mac, then swap ports |
| UAD Meter shows “Driver Not Yet Allowed” | macOS blocked the driver | Allow UA software in Privacy & Security, then restart |
| Device appears, DAW still uses built-in audio | DAW device selection cached | Switch to built-in audio, apply, then switch back to Apollo |
| Works until sleep, then disappears | Thunderbolt bus stuck after sleep | Restart Mac, then keep sleep off during sessions |
If you tried a direct Thunderbolt connection with a known-good cable and you still see “No Devices Found”, move to the macOS security steps next. That’s the next common blocker.
macOS Security And Driver Approval Steps
On modern macOS, installing UAD software is only half the job. You also have to allow it to run. If you skip this step, the Mac can act like the interface is not connected even with a perfect Thunderbolt chain.
Allow Universal Audio Software In Privacy And Security
After you install the latest UAD software and restart, open System Settings, go to Privacy & Security, and scroll to the Security area. UA instructs you to click Allow for Universal Audio software, enter your password, then restart again so the driver loads. UA also notes a time limit: the Allow step must be completed within 30 minutes of the installation, so a reinstall can be needed if you missed the window. Source
- Install the latest UAD software — Run the installer from UA and restart when prompted.
- Open Privacy & Security — Scroll until you see the Allow button tied to Universal Audio.
- Click Allow and authenticate — Enter your Mac password, then restart again.
If you don’t see an Allow button and UAD Meter doesn’t show “Driver Not Yet Allowed” or “Click Allow in Privacy & Security”, the driver may already be allowed. In that case, focus on the Thunderbolt chain and app routing. If you missed the time window, reinstalling is the usual way to bring the Allow prompt back, since UA notes the 30-minute window after installation. Source
Apple Silicon Macs Need One Extra Setup Layer
On Apple silicon Macs, UA says extra configuration is required for UAD-2 hardware like Apollo and Satellite. The steps happen in macOS Recovery and include a security policy change, so plan a few minutes to reboot.
- Start macOS Recovery — Shut down the Mac, then hold the power button until startup options appear.
- Set the security policy — In Startup Security Utility, choose Reduced Security and allow user management of kernel extensions from identified developers.
- Install and allow after reboot — Back in macOS, install UAD software, then do the Allow step in Privacy & Security and restart again.
UA also notes that UAD software must be installed on an internal system drive on Apple silicon Macs, and that the security policy settings must remain in place for the driver to keep loading. Source
Fixing Apollo Twin Connection Issues On Mac After Sleep Or Updates
If your Apollo works, then vanishes after sleep or an OS update, treat it like a re-detect failure. The device may be fine, yet the Mac doesn’t bring it back cleanly.
Start by updating UAD software after a macOS update, then restart and check for any driver approval message in UAD Meter. UA’s macOS guidance centers on installing the latest UAD software and completing the Allow step when prompted. Source
- Update UAD software after macOS updates — Install the current UAD release, then restart.
- Keep sleep off during sessions — Let the display sleep, but keep the computer awake while recording or mixing.
- Do a full shutdown if it won’t return — Shut down the Mac, power off the Apollo, then boot the Mac and Apollo fresh.
UA’s connection troubleshooting page also calls out a hardware reset step for Apollo interfaces when the device won’t initialize cleanly. Use UA’s exact button sequence for your model if basic power cycling didn’t change anything. Source
Apollo Twin Not Showing In Console Or Your DAW
Once the Mac can see the interface, audio routing becomes the usual snag. This is the “it’s connected, but I still hear the laptop speakers” phase.
Confirm The Interface Is Selected In macOS
Open System Settings and set Apollo as both Sound output and Sound input. Then open Audio MIDI Setup and confirm it appears as an audio device. If it’s listed there, the data link and driver are working, and your remaining work is routing.
- Select Apollo for output — Route system audio through the interface so you can hear playback.
- Select Apollo for input — Route microphone and line inputs into apps that use system audio.
- Match sample rates — Set the same sample rate in Console and in your DAW to avoid device errors.
Check Mic Permissions For The DAW
If input meters stay dead, macOS may be blocking microphone access for the app. In Privacy & Security, enable Microphone access for your DAW and any voice apps you’re using. Quit and reopen the app after you change the setting.
Force The DAW To Refresh Its Device List
Many DAWs cling to the last audio device choice after a sleep drop. A fast reset is to switch away from Apollo, apply, then switch back.
- Switch to built-in audio — Apply the change so the DAW clears stale device references.
- Switch back to Apollo — Re-select Apollo as input and output, then reopen the session.
- Pause Aggregate testing — Aggregates can hide the real issue; get Apollo stable first.
If you still find yourself saying “apollo twin not connecting to mac” while Audio MIDI Setup lists it, the issue is almost always app selection or permissions, not Thunderbolt.
Compatibility Checks When Nothing Else Works
At this point, stop changing five things at once. Run a clean compatibility check, then swap one item at a time.
- Confirm Thunderbolt exists on the Mac — Apollo Twin Thunderbolt needs a Thunderbolt port; a plain USB port will not work with cable tricks.
- Verify macOS and model compatibility — UA lists current macOS versions and connection notes for Apollo Twin and Twin MkII on its compatibility page. Source
- Rule out the USB model mismatch — UA states Apollo USB desktop models are not compatible with macOS. Source
- Test with a second Thunderbolt Mac — A quick test on another Mac with a known-good Thunderbolt cable tells you whether the issue lives in the Mac setup or the interface path.
- Re-check Apple silicon setup steps — If you’re on an Apple silicon Mac, confirm you completed the Recovery mode security policy steps that UA documents. Source
Once the Apollo appears reliably, add your dock, extra Thunderbolt devices, and sleep settings back one at a time. If the problem returns, you’ll know exactly which change triggered it.
