New realtek audio chip device id

[shibajee]

As from 8874.1 HDA WHQL realtek added a new chip id "HDAUDIO\FUNC_01&VEN_10EC&DEV_0245". Just wanted to know u about this. How do u put this in UAD hdxrt without breaking the whql now, r u going for self certified solution ?

[pal1000]

I think I'll have to wait to have access to updated copies of HDXRT.inf, HDXRTSST.inf and HDX_GenericExt_RTK.inf. I'll have good copies of HDXRT.inf and HDXRTSST.inf eventually, but the one that really worries me is HDX_GenericExt_RTK.inf. I was unable to update it beyond 6.0.8824.1. In 6.0.8825.1 HDXRT.inf and HDXRTSST.inf hashes have been moved to HDXRTU.cat. As for HDX_GenericExt_RTK.inf nobody knows what happened with it, it's just gone. Without it or a replacement of it, even with good codec INFs, audio enhancements and Realtek audio control app won't work.

I added this known issue to release notes.

[DooGie666]

The new install working fine here. No problems whatsoever.

[epman100]

I have just registered a while ago and it looks like Microsoft has just posted the generic 8874.1 UAD driver on the MS Update Catalog site today: https://www.catalog.update.microsoft.com/Search.aspx?q=6.0.8874.1

this one does include updated HDXRT.inf & HDXRTSST.inf files with new IDs "HDAUDIO\FUNC_01&VEN_10EC&DEV_0245" & "INTELAUDIO\FUNC_01&VEN_10EC&DEV_0245"

The status for HDX_GenericExt_RTK.inf is uncertain and only Realtek knows whether or not they created a new version of it

[pal1000]

HDX_GenericExt_RTK.inf being out of date has the effect of extension component not installing on systems with sound cards with those hardware IDs. With extension component missing, the other extra components won't install either. So no audio enhancements or Realtek Audio Control app, just the codec.

What I actually need even more to escape this is a .cat file containing the hash of a newer copy of HDX_GenericExt_RTK.inf or a replacement of it. With that I can try guessing updated HDX_GenericExt_RTK.inf or it's replacement content.

This guessing was working well before 6.0.8825.1.

[epman100]

a follow up on my previous post

It appears that support for DEV_0245 seems to be added about as early as 8868.1 for UAD as MS has just posted a generic 8868 UAD driver in the Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=6.0.8868.1

[shibajee]

spcust@ftp3.realtek.com password is changed, do u have the new password ? @pal1000

[pal1000]

No, that's why I stopped at 6.0.8900.1. Passwords rating for it and most other accounts on that server are falling here

[shibajee]

Ahh, what we will do now ? That pass worked like last 4 years. I hope @alanfox2000 have something.

[DooGie666]

The same thing happened a few years ago and the problem got resolved. However these days there are more devs modifying Realtek driver files which they won't be too happy about. I have a feeling that this time rhe details for ftp access won't be so readily obtained. I wish pal1000 every success in the future also alanfox22000. The best of luck to them.

[shibajee]

told u that @alanfox2000 will find something @pal1000

[epman100]

that's the good news, shibajee the bad news is that alanfox2000's realtek hda repository recently got taken down by the DMCA

[djmevans]

@epman100 @pal1000 @shibajee By sheer luck, I had cloned @alanfox2000's repository right before the DMCA takedown. Unfortunately, that clone didn't include the Wiki.

Questions for you:

• Is there any way that would help you at all? If so, I'll upload it for wherever you would like.
• Is there any way I can access the Wiki page even if through a cache for it? The best I was able to find was http://webcache.googleusercontent.com/search?q=cache:https://github.com/alanfox2000/realtek-universal-audio-driver/wiki
• This is more of a subjective question, but if they are willing to do a DMCA takedown on a GitHub for their drivers because so many people have issues with them, wouldn't that tell them they need to provide better access to their drivers?

[pal1000]

@epman100 @pal1000 @shibajee By sheer luck, I had cloned @alanfox2000's repository right before the DMCA takedown. Unfortunately, that clone didn't include the Wiki.

Unfortunately GitHub wikis aren't integrated into repositories. That's why it's gone. Questions for you:

* Is there any way that would help you at all? If so, I'll upload it for wherever you would like.

@alanfox2000 posted archives of his repositories on his My Digital Life profile page so this was dealt with already.

• Is there any way I can access the Wiki page even if through a cache for it? The best I was able to find was http://webcache.googleusercontent.com/search?q=cache:https://github.com/alanfox2000/realtek-universal-audio-driver/wiki

I don't know.

• This is more of a subjective question, but if they are willing to do a DMCA takedown on a GitHub for their drivers because so many people have issues with them, wouldn't that tell them they need to provide better access to their drivers?

Long term Realtek should provide a portal where you input your hardware ID and Windows version and bitness and get the latest WHQL final UAD package generated on fly with necessary components and the correct HDA package for your hardware. Short term, extension components should appear on Microsoft Update Catalog. That would help me and fix this issue report.

[epman100]

a follow up on an old post regarding the addition of HWIDs HDAUDIO\FUNC_01&VEN_10EC&DEV_0245 & INTELAUDIO\FUNC_01&VEN_10EC&DEV_0245

It appears that it was added in generic uad v6.0.8867.1, which MS posted recently: https://www.catalog.update.microsoft.com/Search.aspx?q=6.0.8867.1

Edited 3/28 - and it appears that MS finally posted a generic UAD v6.0.8865.1 version (the 10.7Mb cab download) which is the last one without the addition of DEV_0245: https://www.catalog.update.microsoft.com/Search.aspx?q=6.0.8865.1

[pal1000]

Unfortunately the lack of an updated extension component causes equalizer and other enhancements to be unavailable for the aforementioned hardware IDs. That's why this issue is still open.

[epman100]

see my previous comment which was edited recently

indeed it seems Realtek is not making anymore new WHQL'ed HDX_GenericExt_RTK.inf files greater than 8824. and if they were, they're not sharing it and may have a different catalog hash file which also again is not being shared.

[epman100]

No, that's why I stopped at 6.0.8900.1. Passwords rating for it and most other accounts on that server are falling here

and it appears that these logins & passwords for various Realtek LAN drivers (not just for Realtek audio drivers) have stopped working as of April 2020

[epman100]

8911 uad has been posted on ms update catalog wed 4/22 but no longer includes the generic hdxrt.inf & hdxrtsst.inf files. that was also the case with 8907 uad on ms update posted several days ago that excludes those generic INF files. last uad version that had ms whql certified hdxrt.inf & hdxrtsst.inf files was 8904.

looks like the force updater method of installing newer unofficial generic uad drivers will pretty much be the long term solution as realtek seems to have ceased development of new versions of generic hdxrt.inf & hdxrtsst.inf files along with the ceased development of the HDX_GenericExt_RTK.inf file as well (I'm not sure if that is either a temporary or permanent basis)

[epman100]

for your eyes only, pal1000 :) - I'll let this pic or this one do the talking want it? get it from here

[pal1000]

@epman100, where did you find codec component update? I am curious where it appeared first.

hdxrtsst.inf fails WHQL validation, so it's broken. I think I'll have to stuff both 6.0.8924.1 and 6.0.8904.1 in the package.

[epman100]

@epman100, where did you find codec component update? I am curious where it appeared first.

hdxrtsst.inf fails WHQL validation, so it's broken. I think I'll have to stuff both 6.0.8924.1 and 6.0.8904.1 in the package.

yeah I checked the hdxrtsst.inf file in there and it didn't work on an HP laptop using an SST based Realtek HD audio device as Device Manager rejected that INF file. I found that it needed the additional new SSTPPCfg GUID entries that were added into other SST based INF files.

try this new one with the updated hdxrtsst.inf file - file size of the revised hdxrtsst.inf file is 84933 bytes. tested the newer hdxrtsst.inf file on the HP laptop several hours ago and Device Manager finally accepted it.

btw, generic 8934 HDA & higher added hardware device IDs "HDAUDIO\FUNC_01&VEN_10EC&DEV_0897" & "INTELAUDIO\FUNC_01&VEN_10EC&DEV_0897" but there's no generic UAD equivalent for 8934 & greater. so DEV_0897 is completely unsupported

[pal1000]

@epman100 it worked now. Updated release. I personally use Driver Store explorer to validate INF files as it has a GUI and it can validate INFs even if there is no hardware ID matching. My open-source setup uses pnputil to validate INFs as it's a CLI tool, comes with Windows and validates even when there is no hardware ID matching.

FYI pnputil was stating that hdxrtsst.inf was corrupt.

[yhd12138]

It seems that the hdxrtu.cat only contains HDXRTSST.inf now. HDXRTSST_v6.0.9268.1

[epman100]

It seems that the hdxrtu.cat only contains HDXRTSST.inf now. HDXRTSST_v6.0.9268.1

happy new year 2022. actually, this started with the 6.0.9264.1 UAD HP driver on ms update someone else found where only the hdxrtu.cat & HDXRTSST.inf files were brought back but not HDXRT.inf.

so pal1000 has to continue to use the 8924.1 versions of the hdxrtu.cat, HDXRT.inf & HDXRTSST.inf files in his driver packs.

edit - since my brother's HP Spectre x360 15 df 2020 laptop uses an Intel SST based Realtek audio device beginning with "INTELAUDIO\FUNC_01&VEN_10EC&DEV_0285", I can use the generic HDXRTSST.inf file to update the driver to either 9264 or 9268.

[pal1000]

@yhd12138 @epman100 I looked at HDXRTSST.inf in both 6.0.9264.1 and 6.0.9268.1 HP packages and there are some disturbing changes that may ruin force updating completely:

• PnpLockDown is set to 1;
• Default destination directory ID changed from 10 to 13.

I created a pre-release with updated base SST Codec but I imagine force update to 6.0.9282.1 will fail on systems with INTELAUDIO devices when using this pre-release. Feedback is welcome to know for sure as I don't have any INTELAUDIO devices.

[epman100]

HOLY CRAP, pal1000!

MS recently released a 6.0.9275.1 UAD driver package on 2/3/2022 that seems to include the hdxrtu.cat file but didn't include the updated hdxrt.inf & hdxrtsst.inf files. I'm not sure if those files can be re-created for 9275

[pal1000]

For hdxrtsst.inf it should work pretty easy since we have a recent copy, but for hdxrt.inf it will be very difficult if not impossible due to our copy being pretty old and the number of changes in hdxrtsst.inf was significant and it's expected that the same happened for hdxrt.inf.

[epman100]

@yhd12138 @epman100 I looked at HDXRTSST.inf in both 6.0.9264.1 and 6.0.9268.1 HP packages and there are some disturbing changes that may ruin force updating completely:

* [PnpLockDown](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-version-section) is set to 1;

* Default destination [directory ID](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/using-dirids) changed from 10 to 13.

I created a pre-release with updated base SST Codec but I imagine force update to 6.0.9282.1 will fail on systems with INTELAUDIO devices when using this pre-release. Feedback is welcome to know for sure as I don't have any INTELAUDIO devices.

it looks like HDXRTSST.inf is not the only INF file that uses PnpLockDown=1 If you download the 9275 uad driver cab file from Microsoft I mentioned last time, the HDXSSTIntelRVP.inf file uses it as well - open that file in Notepad and you will see it, along with using the DriverStore destination folder path 13. HDXSSTIntelRVP.inf has been around for a few years.

and I'm afraid the generic hdxrt.inf file for 9275 also uses them too, along with the 9275 hdxrtsst.inf file.

[pal1000]

I created a pre-release with updated base SST Codec but I imagine force update to 6.0.9282.1 will fail on systems with INTELAUDIO devices when using this pre-release. Feedback is welcome to know for sure as I don't have any INTELAUDIO devices.

Force updater indeed fails silently without any error as I expected. Tested with HDXRT.inf v6.0.9275.1 which I was able to generate by patching its old version using HDXMSI.inf v6.0.9275.1 and HDXRTSST.inf v6.0.9268.1. Slowly patching in the changes and still not passing validation resulted in the end on PnpLockdown enabling being the only change left to apply. Patch it in resulted validation to pass.

it looks like HDXRTSST.inf is not the only INF file that uses PnpLockDown=1 If you download the 9275 uad driver cab file from Microsoft I mentioned last time, the HDXSSTIntelRVP.inf file uses it as well - open that file in Notepad and you will see it, along with using the DriverStore destination folder path 13. HDXSSTIntelRVP.inf has been around for a few years.

Found it in HDXINTEL.inf as well if I recall correctly.

and I'm afraid the generic hdxrt.inf file for 9275 also uses them too, along with the 9275 hdxrtsst.inf file.

Generation process proved this is indeed the case.

There is hope on defeating PnPLockDown by overwriting RTKVHD64.sys and RTAIODAT.DAT as SYSTEM user.

[pal1000]

Here is the generic UAD 6.0.9275.1 codec Codec_9275.zip

[epman100]

Here is the generic UAD 6.0.9275.1 codec Codec_9275.zip

thanks

here's the 9275 UAD codec from GD - same thing as your codec pack except the hdxrt.inf & hdxrtsst.inf files have the correct/fixed date & time stamps of Dec. 2, 2021 {corrected the date/time stamps of the inf files using the attribute changer app} - need to match the date & times of the other 9275 INF files

with this, I think I may permanently switch to UAD drivers on all my Win10 machines since HDA FF00 driver releases are getting fewer and fewer lately (to a point that there may be a drought or shortage of new HDA driver releases) and many pc manufacturers using onboard realtek audio are implementing UAD/DCH drivers on modern systems as those kinds of drivers have gone mainstream in the past few years

[pal1000]

v6.0.9301.1-2 is the first release where force updater is capable of defeating PNP lockdown protection.

[epman100]

@pal1000 might want to re-release your latest UAD driver pack and include v9305 of the hdxrtsst.inf file from this 9305 driver cab pack from MS.

[pal1000]

@pal1000 might want to re-release your latest UAD driver pack and include v9305 of the hdxrtsst.inf file from this 9305 driver cab pack from MS.

It's not worthy it to re-release as the only change to hdxrtsst.inf is date and version bump and kernel driver is updated to an even newer version by force updater. It will be present in the next release though.

[epman100]

@pal1000 might want to re-release your latest UAD driver pack and include v9305 of the hdxrtsst.inf file from this 9305 driver cab pack from MS.

It's not worthy it to re-release as the only change to hdxrtsst.inf is date and version bump and kernel driver is updated to an even newer version by force updater. It will be present in the next release though.

aww never mind. I recently happen to find this 6.0.9329.1 UAD HP driver from Microsoft (which was released a few days ago around mid-May 2022) that also contains newer hdxrtu.cat & hdxrtsst.inf files (of course the hdxrtu.cat signature file only mentions about hdxrtsst.inf and not hdxrt.inf)

[pal1000]

@epman100, hdxrtsst.inf v6.0.9329.1 only bumps date and version number and for unknown reasons it drops support for no less than 14 hardware IDs. Definitely I'll stick to 6.0.9305.1 WHQL base for INTELAUDIO for the time being.

[epman100]

happy new year 2022. actually, this started with the 6.0.9264.1 UAD HP driver on ms update someone else found where only the hdxrtu.cat & HDXRTSST.inf files were brought back but not HDXRT.inf.

I was wrong about this as I found an older UAD HP driver from MS that does bundle the hdxrtu.cat & HDXRTSST.inf files - v6.0.9210.1 only those two files were revived unexpectedly in that version

however, this 9210 UAD HP driver from MS was listed in ms update catalog (MUC) searches around near end of 2021 or sometime in Jan. 2022 - wasn't listed or didn't turn up in any MUC searches around late summer or autumn 2021

might have to change the description to read "Force updater is now capable of defeating PNP lockdown protection. This is required to successfully force update from WHQL codec v6.0.9210.1 or newer"

[epman100]

check out this page of Realtek HD Audio driver versions from the Treexy.com web site, pal1000 (might take a while to load on slow PCs running Firefox).

the page appears to mention a 6.0.9356.1 version of the hdxrt.inf file dated May 23, 2022. unfortunately, I won't be able to obtain that specific version yet as that requires using a paid version of Treexy's Driver Fusion Premium app to actually update the hdxrt.inf file from 6.0.9275.1 to 6.0.9356.1 :(

edit - no matter, one day I'll just buy a license for the Driver Fusion Premium tool and use it to fetch the updated 9356 hdxrt.inf file since no other 3rd party driver update app can find/offer a newer hdxrt.inf file (a 1-yr license is less than $20 so money is not an issue for me)

[lucasfuzzersodre]

check out this page of Realtek HD Audio driver versions from the Treexy.com web site, pal1000 (might take a while to load on slow PCs running Firefox).

the page appears to mention a 6.0.9356.1 version of the hdxrt.inf file dated May 23, 2022. unfortunately, I won't be able to obtain that specific version yet as that requires using a paid version of Treexy's Driver Fusion Premium app to actually update the hdxrt.inf file from 6.0.9275.1 to 6.0.9356.1 :(

edit - no matter, one day I'll just buy a license for the Driver Fusion Premium tool and use it to fetch the updated 9356 hdxrt.inf file since no other 3rd party driver update app can find/offer a newer hdxrt.inf file (a 1-yr license is less than $20 so money is not an issue for me)

Did you get that file "hdxrt.inf" 6.0.9356.1? Could you make it available for free download? My old laptop needs this update, the latest drivers I can't install, it gives an error.

[epman100]

Did you get that file "hdxrt.inf" 6.0.9356.1? Could you make it available for free download? My old laptop needs this update, the latest drivers I can't install, it gives an error.

unfortunately I was unable to obtain the 6.0.9356.1 hdxrt.inf driver package due to important personal & family matters outside the computing world

plus you did not specify what kind of old laptop (name brand & model) you were using and what version of Windows you have on that laptop.

back then in late November 2022 when I made that previous comment, I was enthusiastic on getting that generic 9356 driver package. but several weeks later in late December 2022, one of my aunts unexpectedly passed away and her funeral took place in early February 2023 and my family & I are still dealing with the loss.

so my plans on getting that generic 6.0.9356.1 driver pack thru the Driver Fusion Pro app are placed on hold indefinitely as I recently don't have the time right now (money is not the issue for me in paying the license for Driver Fusion Pro; it's the time & commitment)

[zertyuiop]

I'm not sure if this can be of any use, but here's what I found using one of the driver update programs: https://www.upload.ee/files/15262161/RTK.7z.html

[pal1000]

HDRT.inf Codec 6.0.9310.1 is good to go and I already picked it for next release but an even newer version 6.0.9356.1 is available if you buy a driver downloader license. Unfortunately @epman100 gave up on downloading it for me due to personal reasons.

As for HDXRTSST.inf I have doubts updating it to 6.0.9329.1 is worthwhile.

[epman100]

HDRT.inf Codec 6.0.9310.1 is good to go and I already picked it for next release but an even newer version 6.0.9356.1 is available if you buy a driver downloader license. Unfortunately @epman100 gave up on downloading it for me due to personal reasons.

As for HDXRTSST.inf I have doubts updating it to 6.0.9329.1 is worthwhile.

I was kinda emotionally & mentally drained at at that time, but I am considering getting the 6.0.9356.1 hdxrt.inf file either in June or July, but I'm not sure if you really want to have the 9356 version of hdxrt.inf as that new version may possibly do the same thing as the 6.0.9329.1 hdxrtsst.inf file (drop/subtract support for several older DEV IDs like DEV_0260 & DEV_0272)

however, I have recently made this 9310 codec pack that has both the updated generic hdxrt.inf & hdxrtsst.inf files with the corrected/fixed date & time stamps.

btw, this site appears to have that 6.0.9310.1 hdxrt.inf file package; not sure when that site obtained it

so it's best to stay with the 6.0.9310.1 generic hdxrt.inf & hdxrtsst.inf files as newer versions beyond 9310 seem to have dropped support for several old & ancient IDs like DEV_0260, DEV_0272, DEV_0660, DEV_0882, DEV_0883 etc. which those IDs were around the time when the HDA standard first came out.

and now that leaves us without a new version of HDX_GenericExt_RTK.inf as Realtek isn't making & sharing anymore new versions of that INF file beyond 6.0.8824.1

[pal1000]

@epman100 I am curious where did you find HDXRTSST 6.0.9310.1?

[jmnielsen7]

Does anyone actually know what Realtek chip that DEV_0245 indicates? It doesn't appear that there is an ALC245 chip, from extensive Googling, for example. Would that require emailing Realtek itself to get an answer, or has anyone ever laid eyes on their Realtek chip to make a physical/visual correspondence to verify what it is? I ask because I have a laptop with this DEV ID and I can't dissect it without voiding the warranty.

[epman100]

@epman100 I am curious where did you find HDXRTSST 6.0.9310.1?

I did not really have to "find" v6.0.9310.1 of the hdxrtsst.inf file. the 1.66Mb size hdxrtu.cat signature file for 9310 mentions both hdxrt.inf & hdxrtsst.inf files. so I figured the hdxrtsst.inf file for 6.0.9310.1 is about the same as the 6.0.9305.1 version other than the obvious date & version build bump.

Unfortunately @epman100 gave up on downloading it for me due to personal reasons.

indeed I eventually "gave up" on getting 6.0.9356.1 of the hdxrt.inf driver package but not just for the reasons that you would expect. there were also different reasons - the major one is that I did make few attempts in early June to purchase a license for that driver fusion pro app but errors occurred during the ordering process on their web site (either my card declined/rejected the charge or would not accept my online payment method).

but anyways, I'm perfectly happy & satisfied with the 6.0.9310.1 of the hdxrt.inf file and I no longer need newer versions. and it appears (from the oem versions of the hdxrt.cat & hdxrtext.cat signature files) that 6.0.9314.1 is the very last version to retain support for those old realtek audio chipsets like DEV_0272, DEV_0882 & DEV_0883. those appear to have been dropped or removed starting with 6.0.9316.1 (don't know about 6.0.9315.1 though) as they're no longer being mentioned in the signature files & in the inf files.

[epman100]

Does anyone actually know what Realtek chip that DEV_0245 indicates? It doesn't appear that there is an ALC245 chip, from extensive Googling, for example. Would that require emailing Realtek itself to get an answer, or has anyone ever laid eyes on their Realtek chip to make a physical/visual correspondence to verify what it is? I ask because I have a laptop with this DEV ID and I can't dissect it without voiding the warranty.

according to this DriverAgent.com listings link about DEV_0245 (or just 0245), the only computer manufacturers that use such realtek audio chipset appear to be Acer and Hewlett-Packard (HP).

also, certain Realtek chipsets like 0245 (or ALC245) are given directly to computer manufacturers like Acer & HP; that's one big reason why you won't find any info about it anywhere. you could try emailing either Realtek or the PC manufacturer of your laptop about it. if you decide to email Realtek, do NOT expect an immediate response.

what kind of laptop are you using, jmnielsen7? it would be best to obtain and use the realtek audio drivers direct from the laptop manufacturer rather than use any of pal1000's unofficial uad generic drivers as the manufacturer based drivers have full support for DEV_0245 while the unofficial uad generic drivers have only "partial" and incomplete support for DEV_0245. a newer HDX_GenericExt_RTK.inf file is needed for the unofficial uad generic drivers to fully support 0245 but the last version of that specific INF file made was 6.0.8824.1, which lacks support for DEV_0245 and Realtek don't seem to be making any more new versions of it (or at least not giving it out publicly).

[lucasfuzzersodre]

If it helps, the Hardware ID of my Realtek chip is DEV_0255. Notebook Acer Aspire E5-574-78LR.

[epman100]

If it helps, the Hardware ID of my Realtek chip is DEV_0255. Notebook Acer Aspire E5-574-78LR.

both original/official realtek uad/dch acer drivers and unofficial realtek uad generic drivers work just fine with DEV_0255 for your Acer laptop. so you are good to go, lucasfuzzersodre

[epman100]

it looks like HDXRTSST.inf is not the only INF file that uses PnpLockDown=1 If you download the 9275 uad driver cab file from Microsoft I mentioned last time, the HDXSSTIntelRVP.inf file uses it as well - open that file in Notepad and you will see it, along with using the DriverStore destination folder path 13. HDXSSTIntelRVP.inf has been around for a few years.

it looks like PnpLockDown=1 is now included (seems to be standard) in all base codec INF files since 6.0.9527.1 (check this 9527 uad codec driver cab download)