HDAUniversal - AppleHDA-like Audio Kext for macOS Tahoe and Hackintosh Systems

[MaLd0n]

Uninstall kext, reboot, install new version with .pkg, take permissions, reboot then extract logs with .command from first post. Use sip on 03080000, no applealc, no voodoohda loaded.

[Droga]

HDAUniversal-Quick-Diagnostics-2026-08-05_20-44-01.zip

[MaLd0n]

After uninnstall, reboot, install new version, u need reboot again then extract.

Big problems in ur pc

/System/Library/Audio/Plug-Ins/HAL/MacAudio.driver / coreaudiod: 42.2% CPU

Error loading MacAudio.driver
mach-o file, but is an incompatible architecture
have 'arm64e', need 'x86_64h' or 'x86_64'

[Droga]

4 hours ago, MaLd0n dijo:

Uninstall kext, reboot, install new version with .pkg, take permissions, reboot then extract logs with .command from first post. Use sip on 03080000, no applealc, no voodoohda loaded.

Hi MaLd0n,

Thanks for checking the logs. Here are clarifications regarding the points raised:

1. coreaudiod CPU usage & MacAudio.driver:
I checked the MacAudio.driver binary directly in /System/Library with the file tool on macOS 26.6 (Build 25G72):

$ file /System/Library/Audio/Plug-Ins/HAL/MacAudio.driver/Contents/MacOS/MacAudio
Mach-O 64-bit bundle arm64e

MacAudio.driver is an official Apple system bundle included in the stock macOS 26.6 Tahoe image, compiled strictly for arm64e. On x86_64 systems, coreaudiod (x86_64) scans /System/Library/Audio/Plug-Ins/HAL/ on startup and logs an architecture mismatch. Because neither AppleALC nor HDAUniversal was loaded, coreaudiod had no active IOAudioEngine output and ran in a discovery loop, causing the temporary CPU spike. Once AppleALC is enabled, coreaudiod binds normally and CPU drops to 0.5%.

2. Installation sequence & kmutil error:
I did reboot after installing the .pkg before running the .command script. The reason loaded_match shows "not_detected" is because kmutil/kernelmanagerd rejected HDAUniversal 1.0.0 at boot with the C++ symbol link error:

Superclass vtable '__ZTV8OSObject' is not exported from 'com.apple.driver.AppleHDA'

Because of this symbol export restriction in macOS Tahoe, kernelmanagerd cannot load HDAUniversal.kext into AuxKC.

Edited yesterday at 02:18 AM by Droga

[MaLd0n]

11 hours ago, Droga said:

Hi MaLd0n

Updated extractor

https://olarila.com/files/macOS-Applications/HDA-Universal/HDAUniversal-Fast-Diagnostics-v2.2-Release.zip

[Droga]

2 hours ago, MaLd0n dijo:

Updated extractor

https://olarila.com/files/macOS-Applications/HDA-Universal/HDAUniversal-Fast-Diagnostics-v2.2-Release.zip

 

HDAUniversal-Fast-Diagnostics-2026-08-06_12-35-03.zip

[MaLd0n]

Seems u have a patcher things there, old applehda, etc

[Droga]

8 hours ago, MaLd0n dijo:

Seems u have a patcher things there, old applehda, etc

Hi MaLd0n,

To clarify for everyone following this thread, this is the exact same system setup as before, only updated to macOS 26.6 (Tahoe) — and it seems all these issues started specifically in 26.6. There are no third-party patchers, OCLP scripts, or modified legacy kexts here.

Here is the exact technical context:

1. System Environment: Running macOS Tahoe (macOS 26.6, Build 25G72) — exact same setup as before, updated to 26.6.
2. AppleHDA Origin: The AppleHDA.kext being used is 100% vanilla, restored directly from Apple's official Kernel Debug Kit (KDK) for macOS 26.6.
3. The AuxKC Issue: In macOS 26.6, Apple restricted legacy kernel extension loading from /Library/Extensions/ and stripped certain export symbols from kernel collections.

When attempting to build the Auxiliary Kernel Collection via kmutil, kernelmanagerd fails with this explicit log error:

"Error occurred while building a collection: Superclass vtable '__ZTV8OSObject' is not exported from 'com.apple.driver.AppleHDA' or its dependencies"

This confirms that the issue is not caused by user patchers or stale files, but by missing vtable export symbols in macOS 26.6's AppleHDA dependency tree when building the AuxKC.

Is there an updated HDAUniversal build compiled specifically for macOS 26.6 KDK symbols? Thank you!

[MaLd0n]

I'm looking at the kext; some security-related aspects ended up being a bit too restrictive. but the kext work nice on 26.6.

[Droga]

Thanks MaLd0n! That makes sense regarding the security restrictions. Looking forward to testing the updated build once you release it.