Windows 10: Latest Realtek HD Audio Driver Version

**AndreTen** · 09 Feb 2017

CountMike said:

Just tried newest from SI but same story, they are all generic Realtek drivers.
Andre, I don't get all that and that's what I'm after. I'm sure I had it just like that on my previous Gigabyte MBs. I also downloaded some older drivers from Gigabyte. Just about to try them too.

I've downloaded from Realtek second from top.

**CountMike** · 09 Feb 2017

Yes, those are newest, had that too. Right now I went back as far as this CODEC chip is supported and same thing.
I'm not complaining about drivers, sound is same quality which ever I tried just no system wide adjustments. Getting different sound in different programs. Watching TV (pass thru from sat receiver) and online video like You tube, base is too strong and need constant adjustment on the amp (Sub-woofer) itself but than music and movies sounds wrong.

**ComputerGeek** · 09 Feb 2017

CountMike said:

Just tried newest from SI but same story, they are all generic Realtek drivers.
Andre, I don't get all that and that's what I'm after. I'm sure I had it just like that on my previous Gigabyte MBs. I also downloaded some older drivers from Gigabyte. Just about to try them too.

@CountMike
It's all about the Hardware and Compatible IDs for your audio card. Windows will only provide a driver matching those IDs. If you want to try AndreTen's installation, we need to know the matching ID and the Original .inf file used for the install.

@AndreTen
Could you:

Right click your audio device->Properties->Details tab. Select Matching device id from pull down menu. Copy/paste result into your next post
Next select Inf name from pull down menu and jot down the oem inf filename
Open an admin command prompt. Type dism /online /get-drivers
Search the result of 3) for the oem filename in 2).Tell us the Original File Name

@CountMike
The Andre's Original File Name inf is the one you want try and hack

**CountMike** · 09 Feb 2017

HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A132&REV_1000
HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A132

Inf File = oem14.inf
Those all stay same which ever driver I install.

**AndreTen** · 09 Feb 2017

ComputerGeek said:

@CountMike
It's all about the Hardware and Compatible IDs for your audio card. Windows will only provide a driver matching those IDs. If you want to try AndreTen's installation, we need to know the matching ID and the Original .inf file used for the install.

@AndreTen
Could you:

Right click your audio device->Properties->Details tab. Select Matching device id from pull down menu. Copy/paste result into your next post
Next select Inf name from pull down menu and jot down the oem inf filename
Open an admin command prompt. Type dism /online /get-drivers
Search the result of 3) for the oem filename in 2).Tell us the Original File Name

@CountMike
The Andre's Original File Name inf is the one you want try and hack

Matching device id: hdaudio\func_01&ven_10ec&dev_0885&subsys_1458a002

Inf_name: oem9.inf

Published Name : oem9.inf
Original File Name : hdxcr.inf
Inbox : No
Class Name : MEDIA
Provider Name : Realtek Semiconductor Corp.
Date : 05. 01. 2017
Version : 6.0.1.8036

@ComputerGeek, we have a bit different chips 889A vs 889, one is on Intel Board, second AMD

**CountMike** · 09 Feb 2017

Can't choose individual .inf file. With 80036 .inf file is oem41.inf this time.

**AndreTen** · 09 Feb 2017

Did you try with this driver? It supposed to be for Windows 8.1 from softpedia - it is for rev 3.1, so no exactly the same board (if you spec are correct)

**ComputerGeek** · 09 Feb 2017

CountMike said:

Can't choose individual .inf file. With 80036 .inf file is oem41.inf this time.

oem filename is irrelevant. It's a pseudo-random name generated by Windows (it merely picks the next number in sequence), the name is local to your machine. That same oem inf filename can be assigned to any driver of any device class. To know what's been installed you want know

The Original inf filename (see prior post)
The matching device id (can show whether the driver installed was hardware specific or a generic/compatible driver)
Driver version number also helpful if you want to compare

When you download from Realtek or MUC, you download a driver with close to 100 different INF files. You need to know the Original filename to understand what was actually installed

Based on the hw ids you provided earlier, my guess is you installed HDXPCEEF.inf. (you should double check). AndreTen installs HDXRC.INF. At least one of the (big) reasons you see different results.

**AndreTen** · 10 Feb 2017

Thanks for explaining it in details @ComputerGeek

Good to know

**CountMike** · 10 Feb 2017

ComputerGeek said:

oem filename is irrelevant. It's a pseudo-random name generated by Windows (it merely picks the next number in sequence), the name is local to your machine. That same oem inf filename can be assigned to any driver of any device class. To know what's been installed you want know

The Original inf filename (see prior post)
The matching device id (can show whether the driver installed was hardware specific or a generic/compatible driver)
Driver version number also helpful if you want to compare

When you download from Realtek or MUC, you download a driver with close to 100 different INF files. You need to know the Original filename to understand what was actually installed

Based on the hw ids you provided earlier, my guess is you installed HDXPCEEF.inf. (you should double check). AndreTen installs HDXRC.INF. At least one of the (big) reasons you see different results.

What I meant, I was unable to choose any specific .inf file from driver folder because I was going wrong way about it. Now I remembered how to do it so I will try later on. I have that HDXRC.INF in the folder with driver.

Windows 10: Latest Realtek HD Audio Driver Version

Posting Permissions