Determine the DCH (UAD) Realtek driver needed for your Audio

erpster4 said:

that generic UAD/DCH Realtek audio driver from Majorgeeks is the one from pal1000's uad generic driver packages from github, which are NOT official drivers.

I don't know if ddelo's script will work well with pal1000's unofficial DCH drivers - and using those unofficial generic DCH drivers is somewhat risky on older machines



that's because HWID "INTELAUDIO\FUNC_01&VEN_10EC&DEV_0255&SUBSYS_10251039" is only listed in the HDXSST4.inf file for an HDA driver and that ID is not listed in any INF file of many recent UAD drivers - thus UAD/DCH drivers do not officially support that ID. recent UAD drivers from MUC from 6.0.8907.1 & higher no longer include the generic HDXRT.inf & HDXRTSST.inf files (I guess Realtek figured they cut costs by producing new UAD/DCH drivers without bundling those generic HDXRT.inf & HDXRTSST.inf files).

as a last resort you could try v6.0.8904.1 from MUC, which does have the generic HDXRT.inf & HDXRTSST.inf files.

I was thinking that this device simply wasn't going to be compatible with DCH, at least without incurring a major headache. Thanks for confirming that. I might give those 8904 drivers a try but probably better off sticking with HDA - I'm in no rush to update to a newer version of Win.10, so HDA should be OK for a while longer.

<begin rant>IMO the sound device I have is utter garbage and has no place in a supposed gaming oriented laptop. I have yet to find any value in IntelSST and the lack of drivers for it are the only thing keeping me from using Win7.<end rant>

Cheers.

ddelo said:

First of all, let me thank you for posting the screen output, so I could see where the script fails, when running on unofficial DCH installations.
Sorry for the late reply, but I was trying to fix the issues you had with the script.

As @erpster4 already said, the script will not be able to work properly on non-standard/unofficial DCH installations (like the one made from pal1000). The reason is apparent: It's a non-standard DCH driver which is force-installed on systems not designed to use DCH drivers.
Either way, I did try to fix the problems shown on your output (to accommodate other users too) and I have released a newer version of the script.
I would appreciated it, if you could give it a shot and post the screen output.

The most serious problem seems to be in the Software Components detection. I really don't know (as I cannot test it) what are all these [2:10.0,2:6.3,2:6.2,2:6.1,2:6.0,2:5.2,2:5.1] strings. It seems that they must be remnants from an HDA driver installation as they look like Windows version numbers.

Either way, I would agree with the opinion of our Audio driver guru erpster4, that since you have problems with the DCH drivers you should stick with the HDA ones.

No problem for the delay.
I have migrated to some modded drivers (AAFDCH) so I can't run the script ATM. Well, at least can't run it and expect the same results.
When I'm tired of beating my head on these drivers (initially it would only work if I had headphones connected. got that sorted, but the volume is really low and I'm not even sure the effects (atmos, nahamic, et-al) even work - I really can't hear much, if any change between on and off) I'll just go back to HDA.
For the record, I got the exact same errors running the script on HDA drivers as those generic DCH.
Cheers.

hi ddelo

here's a screenshot that generated a log file when I ran your script on my custom built PC with a Gigabyte board that does support UAD/DCH Realtek audio drivers - even includes a pic of DriverStore Explorer (Rapr.exe) which also tells me what INF files used to install the Realtek UAD/DCH driver:



at least the script works on this PC with a Gigabyte board
it's too bad it doesn't seem to work right on Not Bob's machine as I think his PC was made a few years before Win10 first came out and before Reatlek developed the UAD/DCH audio drivers (and perhaps came pre-installed with HDA drivers)

I don't know how you patched your system because you have a mismatched 231 HSA and 234 App.

erpster4 said:

it's too bad it doesn't seem to work right on Not Bob's machine as I think his PC was made a few years before Win10 first came out and before Reatlek developed the UAD/DCH audio drivers (and perhaps came pre-installed with HDA drivers)

The laptop was preinstalled with Win.10, but it is definitely before DCH audio - the Intel video DCH drivers work without a hitch on the other hand.
I can't remember exactly when I bought it, but it was just before the "Anniversary" update - and things went downhill from there.

sandyt said:

I don't know how you patched your system because you have a mismatched 231 HSA and 234 App.

the mis-matched HSAs are a non-issue to me as the Realtek Audio Console 234 app works with the 9034 driver (I kept a copy of the 234 appx file and just re-install it "offline" w/out using MS store to download it again)
I have to remind folks that I always clean install & remove UAD/DCH drivers using its setup.exe program and I NEVER install or remove such drivers using Device Manager (especially the Realtek Device Extension INF files - those specific INF files can never be installed nor removed thru Device Manager)

Not Bob said:

The laptop was preinstalled with Win.10, but it is definitely before DCH audio - the Intel video DCH drivers work without a hitch on the other hand.
I can't remember exactly when I bought it, but it was just before the "Anniversary" update - and things went downhill from there.

most likely either the 1507 or 1511 version of Win10. UAD/DCH drivers were developed either in late 2017 or early 2018 (around the time of the "fall creators" update such as 1709) Realtek UAD drivers support at least the "Creators" update (1703 or build 15063) but nothing before that like the anniversary (1607) update

erpster4 said:

the mis-matched HSAs are a non-issue to me as the Realtek Audio Console 234 app works with the 9034 driver (I kept a copy of the 234 appx file and just re-install it "offline" w/out using MS store to download it again)
I have to remind folks that I always clean install & remove UAD/DCH drivers using its setup.exe program and I NEVER install or remove such drivers using Device Manager (especially the Realtek Device Extension INF files - those specific INF files can never be installed nor removed thru Device Manager)

Except that Microsoft DIDN'T design their DCH driver update process to completely remove old driver and install new driver.

It is completely unnecessary and contrary to Microsoft's DCH driver updating process, where updated drivers are sent via Windows Update as optional updates. Microsoft never designed this process to completely wipe out your old drivers in order to install new drivers.

My updating philosophy has been less is more. The less you diverge from Microsoft's original DCH driver updating process, the safer it is.

It is the fact that you diverge from Microsoft's original DCH driver updating process is what created the mismatch in the first place. You are just reminding the rest of this forum on WHAT NOT TO DO.

The "C" in DCH is Componentized --- there is no need to wipe out your entire driver to update an individual component.