u/IcarusPilot

Just a follow up on my days long frustration here but I can't get the kext extension to post and persist regardless of any relaxed csrutil settings and I'm becoming increasingly skeptical that this is possible in 26.3. It seems possible that it allows the kext db from a Sequoia install to persist when an update to Tahoe is performed, but I'm curious if anyone has successfully installed and connected a twin X to a computer in 26.3.

For the record:
-TB4 cable for sure (tried multiple)
-system info shows the device connected via TB at 40Gbps - not a hardware problem.
-UAD Meter said "Connect UA Device" indicating permission is granted, but invisible to UA software
-I have gotten the "allow" button in Priv and Sec multiple times through multiple instals and panic-medics and UAD Meter seems to be "happy" but not seeing the device.
-I have relaxed security boot settings in recovery disk startup and through terminal directly with the nuclear csrutil disable command.

My thought is that Tahoe is stripping the kext from the queue on restart, putting it in this doom loop of enabling the extension, doing a restart to secure it during boot, and then on reboot its security feature is stripping it before it can post in the kext database. Anyway, I'm over my skis at this point but trying everything I can before I give up on this and go back to an interface with native processing with a different interface.

I just really want this to work. Hopefully someone has an answer.

Update 2: Still no joy. Here is everything I've tried:

-Multiple legit, real, TB4 cables.
-Hardware resets of the apollo
-Manually white listing 4KAC9AX6CG in registry in recovery terminal per another reddit users success
-Recovery Terminal commands:
--kmutil trigger-panic-medic --volume-root "/Volumes/Macintosh HD"
Force kext reset:
--sudo kmutil load -p /Library/Extensions/UAD2System.kext

It shows up on System Information as a thunderbolt device, connected at 40Gbps. It is there, visible and connected. But yet "Connect UA Device" is all I've seen.

Guys, I'm really trying but this seems out of bounds. I had a conference call with two dudes from Universal Audio and even though they were super helpful and tried, their only solution after seeing everything via screen share was "try a different cable which I did.”

I'd say this thing was bricked if it wasn't literally visible in system info as a device. What's next here?

Update: Credit where it's due, Drew from UA just spent a bunch of time trouble shooting with me. Still no joy but definitely have a few possible solves left. Gain try a different TB cable which I'll have to go buy, and if that isn't it, it's likely a hardware defect and I'll be going back to GC anyway. Thanks again Drew. Likely that I beat my head against a wall trying to fix the drivers when looks like that isn't the root cause.

This is insanely frustrating and I'm about to return this thing... I've tried literally everything on the install guide multiple times, which is absurd that any of that is necessary at all, and even some terminal commands from some random post that said it helped to get the kernel extension to work. Am I doing something stupid or is it actually this cumbersome. Sunk cost may be getting the best of me and I'm about to give up but I keep hearing this thing is the best audio interface ever so here we are beating my head against the wall.

Basic facts:

Apollo Twin X, macOS Tahoe 26.3, M2 MacBook Air. Kernel extension not installing. systemextensionsctl list returns 0 extensions. Recovery Mode completed, Reduced Security set, Allow user management of kernel extensions enabled. Malwarebytes removed. Clean install of iLok and UAD software attempted multiple times. Hardware appears in System Information at 40Gb/s Thunderbolt 3 but Console shows Connect UA Device. UAD Meter & Control Panel not appearing in Privacy & Security Microphone list after install. No Allow button appearing in Privacy & Security Security section after install.

Edit to add I just did the whole thing again after full uninstall of everything with app cleaner and installed again in safe mode and still no joy, but now back to pace error banner in UA Connect which I thought I’d licked with the iLOK forced spyware nonsense. How is it possible this thing is so cumbersome to get working?