Windows 10: Latest Realtek HD Audio Driver Version

The output shows oem vs. original filename pairs. What's the original filename of the INF used to install your Realtek audio driver?

[/quote] I no longer have the Code 39 error in Device Manager because I've removed the 8023 driver and reverted to 8010, which works perfectly with my system.

In 8010 I have an Upper filter which is named MBfilt (mbfilt64.sys) . This is one of the Creative Labs drivers and is missing from the Realtek 8023 driver package. The Class upper filter is ksthunk. I imagine it's the omission of mbfilt64.sys in 8023 that's causing the problem.

The original INF file used to install my drivers is hdxmb3h.inf with the following Hardware IDs:

HDAUDIO\FUNC_01&VEN_10EC&DEV_0900&SUBSYS_1458A0B2&REV_1000
HDAUDIO\FUNC_01&VEN_10EC&DEV_0900&SUBSYS_1458A0B2

 

UPDATE: For anyone remotely interested I managed to get 8023 working by editing the hdxmb3h.inf file and removing the following lines:

[Creative.FilterHW.AddReg]
HKR,,"UpperFilters",0x00010000,"MBfilt"

By removing this reference to the MBfilt Upper filter the driver will install correctly and produce sound.

I don't make a habit of editing INF files and I'm by no means certain that the driver will be stable like this but from a diagnostic point of view it has proved useful.

I still have no idea why the INF was referencing a filter driver that was omitted from the driver package. I'll be very interested to see what changes in upcoming driver releases.

 

Excellent, EXCELLENT job! *Thumbs *Thumbs

You got where I was going on your own and ahead of me! *Smile

Device error code 39 , not always, but i've often seen caused by driver filter issue. One cause of Code 39 is when driver files defined in the registry reference a file no longer on disk. No surprise Windows can't load the device driver. A file is missing!
Usually, i see this problem arise when a 3rd party uninstaller, removes the disk file but not the registry reference it added during install. But YOU found a genuine bug in the Realtek driver! Great job.

As to your solution, must admit I'm surprised you could edit the INF file to make this work. Any change to the INF breaks the digital signature so Windows will no longer install it as it's become an unsigned driver.

My own advice around this problem (if you can't edit the INF) is editing the registry to delete the offending filter file reference. Note to the reader:

• It's class upper/lower filters that may be the problem (not device upper/lower filters). There's a difference
• When troubleshooting, check the Provider of any filter files in question. Microsoft filters are fine. It's those 3rd party filters that can be problematic

 

Not relevant to Realtek, but relevant to filters, I once had an issue with my old ATAPI DVD-RW drives connected to an IDE/SATA PCI-E card with JMICRON JMB36X chipset. The DVD-RW would show a yellow exclamation mark (problem) in Device Manager and won't let me use them. At first I suspected the JMICRON controller. I tried many drivers without success, when I read somewhere about deleting the upper filters in Registry. Bingo! The drives now work perfectly and I haven't noticed any side-effect by deleting them. Of course I have kept a backup of the relevant key just in case.

 

The Realtek installer rejected my modified INF but it installed okay via Device Manager (Update Driver). Not the most elegant solution considering that I have no idea what functionality the MBfilt64.sys driver offered in the first place. Still, I'll bet it's nothing I really need!

Thanks for your assistance.

 

The "filt" in the filename suggests some audio filter (digital sound processing or audio effect). In the worst case this can be some environmental audio effect (eg auditorium or whatever) that is now missing. Big deal. You can do the same with appropriate plugins in Windows Media Player or WinAmp or whatever media player you are using.

 

The mbfilt64.sys file is only 41kb in size so I wonder if it's just there to enable installation and use of the optional Creative software suite. As I understand it, the Creative software bundle that I received with my motherboard requires that you install the Realtek driver first. I've had a few bad experiences with Creative software in the past so I can't say I feel inclined to try it!

 

Give the Ceasar's to the Ceasar, meaning I would use Creative software only with genuine Creative hardware (Audigy, X-Fi etc), not with anything else.

 

I think that's sound advice. No pun intended!

 

How do I install this ? Can't figure out

 

Go back, few pages, it's been explained several times. Basically, you un-archive the. cab file and point driver update from Device manager to that folder.

 

Couldn't find it in this thread but nevermind, google helped me

 

Use WinRAR or other archiver to extract the files in the CAB into a folder. Then from Device Manager, Update Driver and browse to that folder.

 

Since Realtek's FTP site disappeared I (like many others I'm sure) have been using the Windows Update Catalog to track development of the Realtek High Definition audio driver. On a couple of occasions I've noticed that CAB files for a particular release have changed over time. The latest release (8029) is a good example. I downloaded this as soon as I saw it and my CAB filename was this:

312dab0c-4146-434c-8530-3cf03064e06a_864a79a7ecf81dc0d0f882892d2dd9fa2aca1f4f.cab

Then, the next day I checked again and it had changed to this:

4bbf4a99-74a3-4163-91fb-db3d585440a0_3effc5fa3eb35d40a07a57221d5ae8dc7d1cd5b0.cab

This is for the exact same 8029 (x64) driver release. What's more the CAB contents have changed too. The original version worked fine on my system and does not have the missing mbfilt64.sys file that I mentioned in an earlier post. The revised version has that file omitted and other changes too, including to INF files themselves.

I'm trying to understand how WIndows Update Catalog works and why these changes are occurring after a driver has been released to the catalog. Any ideas?

In the meantime I'll keep watching in case the CAB file for 8029 changes again! It will help these cold, winter days to fly by. *Wink

 

Thank you. First post updated. *Smile