It's bad, the driver doesn't work properly for my device.
I used the DDU tool to clean up the audio driver before installation, then when I installed the AAF Optimus driver, everything went well, but it reminded me to restart my computer, when I finished restarting my computer I found that I could not see any newly installed audio driver, only the NVIDIA audio driver showed up in the control panel, maybe this is a compatibility issue, can you help me fix this problem?
My audio hardware ids are as follows
Audio driver name: Realtek(R) Audio
Compatible IDs:
HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_A348&VEN_10EC&DEV_1168&REV_1001
HDAUDIO\FUNC_01&CTLR_VEN_8086&VEN_10EC&DEV_1168&REV_1001
HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&REV_1001
HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_A348&VEN_10EC&DEV_1168
HDAUDIO\FUNC_01&CTLR_VEN_8086&VEN_10EC&DEV_1168
HDAUDIO\FUNC_01&VEN_10EC&DEV_1168
HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_A348&VEN_10EC
HDAUDIO\FUNC_01&CTLR_VEN_8086&VEN_10EC
HDAUDIO\FUNC_01&VEN_10EC
HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_A348
HDAUDIO\FUNC_01&CTLR_VEN_8086
HDAUDIO\FUNC_01&GF&VEN_10EC&DEV_1168&SUBSYS_10438723&REV_1001
HDAUDIO\FUNC_01
Matching device ID:
HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438723
Hardware IDs:
HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438723&REV_1001
HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438723
I don't know where to start, because a couple things are wrong as to explain why it isn't working after you restart. WEll, lets tackle what comes first chronologically, you having to clean all the Dolbys and DTS and Realteks drivers with DDU, as you said it, so, why is the driver named Realtek?
Is that like, BEFORE deciding to to download AAF pack and install? because even if the INSTALLATION succeeded, you'll be installing AAF package on top of High Res Windows Audio generic controller/driver, not a realtek one (IDK what windows you have, nor if the new AAF software blocks the autoupdate feature by changing policies/registry/etc); for Windows Update to not silently install an arbitrary Realtek Driver, indeed something must be done, I myself went through with group policies, changed the "do not allow windows update [...]" entry to enabled and specified the hardware ID so it remains untouched; Maybe the new AAF package does that for you, IDK i've been with AAF for a couple years and then many stuff we had to tune and click manually, now it follows a smooth script, so If AAF doesnt, you going and clicking in "do not auto-install drivers" checkbox in Windows' Control Panel -> System or "view advanced system settings" -> "device installation settings" under the Hardware tab -> check the "NO" answer to auto-install/update devices if you got admin reach <----- This won't be enough, check forums and messageboards Win 10 never respected this setting, I dont wanna keep on talking but thats what pops in my mind at first glance, ofc i dont have enough data on your OS, the timeline, what do you mean when you say X, etc.,.. not enough info for troubleshooting, because If we had that, then I'd say It's irrelevant to look for matching IDs and models and numbers, because since it's all based on a built in Windows driver, its universal, one size fits all (for good or bad, AAF also has the "USB" version package that does use REaltek just so you know, im sorry if I overwhelm you