Determine the HDA Realtek driver needed for your Audio

youzername said:

AH, that takes care of errors, still it misidentifies the audio codec. It detects


Audio device Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438724&REV_1000
Realtek Audio CODEC : ALC1168

The Audio device is controlled by Realtek Audio driver version 6.0.9071.1 (HDA) with No Integration (Generic)
Proposed HDA driver : FF00
INF needed for installation: hdxrt.inf


ALC1168 is incorrect, it should be ALC1220 in my case.


Also re: RealtekAudioDriverCompatibility.ps1

It says


PS D:\Downloads> .\RealtekAudioDriverCompatibility.ps1

No '.inf' file found in the provided location, for the Audio device: HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438724


However in the path it requests contains HDXRT.inf and it inded supports my card which is HDAUDIO\FUNC_01&VEN_10EC&DEV_1168

"Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_1168

I was indeed running as admin this time on both scripts. Hope this is helpful for you to debug issues.

First of all, glad we took care of the errors due to non-elevated powershell console.

Now let's start from the end.

The RealtekAudioDriverCompatibility.ps1 script correctly reports that the HDXRT.inf does not contain your "complete" HW Id (HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438724) as it contains the generic HDAUDIO\FUNC_01&VEN_10EC&DEV_1168 id. Meaning that the driver is a generic one and you might lose some functionality if you force install it, as it doesn't pertain to your Asustek (Vendor id:1043) board.

Now regarding the ALC code, the script reads the ALC code from the HW Id and not the chip itself.
If there is a connection between ALC1220 and ALC1168, the script has no way of knowing, neither do I, as I don't have and cannot find the Realtek ALC1220 specification datasheet, to check if Realtek considers the DEV_1168 string of the HW Id as ALC1220 codec.
If you happen to have it, you can pass it over to correct the script.

@ddelo Thanks again

First of all, glad we took care of the errors due to non-elevated powershell console.

I could suggest that the scripts do a check if the console is/not elevated privileges, as it required the script should tell users what it needs.

From Powershell 4.0 and up it can be added to top as

#Requires -RunAsAdministrator


But that may just close the powershell if not,so a more robust solution may be needed if you decide to add that support.

Write-Host "Checking for elevated permissions..."
if (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(`
[Security.Principal.WindowsBuiltInRole] "Administrator")) {
Write-Warning "Insufficient permissions to run this script. Open the PowerShell console as an administrator and run this script again."
Break
}
else {
Write-Host "Code is running as administrator — go on executing the script..." -ForegroundColor Green
}


That seems to be doing it, probably better ways to do this also. Just a suggestion.

Now regarding the ALC code, the script reads the ALC code from the HW Id and not the chip itself.
If there is a connection between ALC1220 and ALC1168, the script has no way of knowing, neither do I, as I don't have and cannot find the Realtek ALC1220 specification datasheet, to check if Realtek considers the DEV_1168 string of the HW Id as ALC1220 codec.
If you happen to have it, you can pass it over to correct the script.

I can only go by what the manufacturer docs say the Asus TUF z270 mark 1 has, and by what the Realtek info dialog reports.

Asus said:

TUF Z270 Mark 1 features Realtek S1220A, an audio codec developed by Realtek especially for ASUS.

The closest I got to any info about the codec is SupremeFX CODECs S1220 and S1220A; what's the difference - Page 3 which says its a custom 1150 device (hence 1168, I suspect), but datasheets dont exist outside Realtek/Asus. So you may just take Realtek at their word that DEV_1168%26SUBSYS_10438724 = ALC1220 (there are many different SUBSYS for DEV_1168 (and IDK if they are all 1220 or not - there are 17 hits on the 6.0.8963.1 HDXASUS.inf with diff SUBSYS)

However that driver is bare

Also, if uninstalling and cleaning out all old drivers and associated elements (until windows has no drivers but the generic with driver autoupda, its possible to install (not forced) http://download.windowsupdate.com/c/...2cf70e7dee.cab which is a full driver 6.0.9071.1 pack at 146MB works better here.

No big deal if script ID's my chip as Realtek does, you could maybe add some note about it, it may confuse others that have similar codecs. I wanted to test the actual scripts to see what info it would provide, but I can say with great certainty that the very latest driver available for the ALC1220 from Asus is 6.0.8963.1 found at the Microsoft update catalog site, anything else is not for Asus, unless its a modded generic driver.

https://www.catalog.update.microsoft...UBSYS_10438724 and toggle the last updated section.

Any other drivers are generic and like you said installing them will likely lose some functions.

Thanks again and take care.

Thanks for the info and the suggestions. @youzername

The latest HDA driver for HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438724 is not 6.0.8963.1 as this is a DCH (UAD) driver.
HDA drivers are large files (> 130MB) as they contain all required components in one file, whereas DCH driver updates ard smaller files (< 10MB) as they contain the update to a specific component, i.e basic driver or software components needed for the driver to function properly.
The latest FF00 HDA driver is 6.0.9071.1 and can be found in this thread: Latest Realtek HD Audio Driver Version [2]

Regarding the ALC1220/1168 codec, I could search for the string DEV_1168&SUBSYS_1043 and report that this is an ASUS ALC1220 codec, but it might be misleading.
To be honest I never liked the interpretation of the DEV_XXXX string to a named codec, as it has a lot of exceptions, which are only known to Realtek (and I have no connection to Realtek, to substantiate their naming conventions)
I think it will be better if I take it out of the script, or find another way to report codec name, which currently I have no idea how to do it in Powershell, as the proper way to do it is to read the ‘Get Parameters’ verb of the chip, to get system information and the function capabilities of the HDA codec.

Hi all, I ran the script and this is the log, which driver should I install on my huawei matebook D15? (AMD version)

RealtekAudioDriverIntegration.log

Realtek Audio Driver Integration log information

Device HWID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0256&SUBSYS_19E53229&REV_1000
Audio CODEC: ALC256

Realtek Driver Version: 6.0.8804.1 (UAD)
Proposed UAD driver : -
INF needed to install : hdxhaphuawei.infRealtekAudioDriverIntegration.log

New version of the PowerShell script uploaded in Option Two of the first page.

Release Notes of version 2.1 (30-Jan-2021)

• Removed identification of Audio CODEC, as there are several exceptions to Realtek's naming convention.

amymor said:

hello
i have Gigabyte H170-Gaming 3 with Realtek ALC1150:
GA-H170-Gaming 3 (rev. 1.0) Overview | Motherboard - GIGABYTE Global

as you mentioned i installed the driver from Gigabyte supports page and then ran the powershell script. here is resault:

Code:

Audio device Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0900&SUBSYS_1458A0B2&REV_1000

The Audio device is controlled by Realtek Audio driver version 6.0.1.7727 (HDA) with Multiple Integrations [FF01-FF06-FF10]
Proposed HDA driver        : Customized Gigabyte Technology Co., Ltd. specific
INF needed for installation: hdxmb3h.inf

so now where i can find latest update for my audio driver?

thanks

Since you have a specific, to your board, driver from Gigabyte, you can update it only from Gigabyte, to retain the existing functionality.
If Gigabyte doesn't offer a newer customized driver, your only option is to use a generic FF00 HDA driver, but you should be aware that you might lose some of the functionality you currently have.

Before proceeding though, you need to have a clear picture of why you want to upgrade. If the reasons to upgrade are compelling, then you have to take the risk and go with a generic FF00 HDA driver. If not, stay with the driver provided by the the Manufacturer.

The latest HDA driver is 6.0.9038.1 and can be found in Microsoft Update Catalog
You need to get the 146Mb version of the driver, which is HDA. The smaller ones are DCH (UAD) drivers and won't work with your board.

ddelo said:

Since you have a specific, to your board, driver from Gigabyte, you can update it only from Gigabyte, to retain the existing functionality.
If Gigabyte doesn't offer a newer customized driver, your only option is to use a generic FF00 HDA driver, but you should be aware that you might lose some of the functionality you currently have.

Before proceeding though, you need to have a clear picture of why you want to upgrade. If the reasons to upgrade are compelling, then you have to take the risk and go with a generic FF00 HDA driver. If not, stay with the driver provided by the the Manufacturer.

The latest HDA driver is 6.0.9038.1 and can be found in Microsoft Update Catalog
You need to get the 146Mb version of the driver, which is HDA. The smaller ones are DCH (UAD) drivers and won't work with your board.

i have a problem.yesterday i noticed the audio of my speaker (rear panel) is mono. at that time i was using 6.0.90xx.1 driver (i dont remember the exact version) which is installed with the Snappy Driver Installer Origin. at first i thought the problem was with the driver so i uninstalled it and then installed the gigabyte one. but after some tests i realized that problem was with the speaker and i solved it. now my speaker(rear panel) works like before and audio is stereo. but i noticed the audio of my headphone (front panel) is mono. when i test left headphone with the Realtek HD Audio Manager i hear a mono loud sound and when i test the right i hear a mono low sound. i have not used the front panel for a long time so I dont know if it is ok or not. also my headphone work correctly in rear panel. any idea?
thanks
sry for my bad eng

Edit: i solved it but i dont know how. i just plugged the speaker into the front panel and then unplugged it and then plugged the headphones into the front panel. so i think my problem is with the front panel or the headphone plug.