Latest Realtek HD Audio Driver Version

Page 2 of 296 FirstFirst 12341252102 ... LastLast

  1. Posts : 89
    Windows 10 Pro
       #11

    ComputerGeek said:
    I found 7 INFs commented with Hardware ID Locking including (not the complete list)
    Code:
    Creative MB2 Hardware ID locking
    D-company X-Fi MB3 Hardware ID locking
    SoundBlaster Cinema 3 Hardware ID locking (M-company ESS case)
    I also found this from thread Unlocked Realtek HD Audio Drivers Windows 7, 8 and 8.1 (With Dolby Digital Live and DTS Interactive)


    Sounds like some Realtek drivers include licensed features that only run on specific h/w (maybe locked based on audio chip h/w id?). Do you have any of the licensed features? Sounds like the bundled the driver files together into a single INF but licensed features only available from specific h/w ids.
    As far as I know, it does not have any of these licensed features; just a Creative software bundle that adds some audio processing functions (if you choose to install it). I guess the real question is why have Realtek stripped away some of the driver components that were in version 8010 and earlier? Whatever it is they have removed, it seems to have broken compatibility with my motherboard.
      My Computer


  2. Posts : 268
    Windows 10 Pro x64 v22H2
       #12

    wiggly1uk2000 said:
    If I try to install 8018 or 8023 as an upgrade over the standard MS supplied high definition driver then the board will not produce sound and simply gives a Code 39 in Device Manager. However, if I upgrade to 8018 or 8023 from a previous installation of 8010 then it will work, but only because it retains the Creative driver components from 8010 in the upgrade process.
    > Do you still have Code 39? When you do, in DevManager right click the device->Properties->Details tab. Use the pulldown and look if either Class uppper filters and/or Class lower filters exist. If yes, then post their values.
    > Which version of the audio driver do you currently have installed?

    Again, right click to Properties->Details tab
    1. Use pull down menu to look for two items: inf name and something like matching device id. Post the result
    2. Windows renames the original INF to oem.nnn. We want the original name. From command prompt

    Code:
    disk /online /get-drivers
    The output shows oem vs. original filename pairs. What's the original filename of the INF used to install your Realtek audio driver?
    Latest Realtek HD Audio Driver Version-filters.jpg
      My Computer


  3. Posts : 89
    Windows 10 Pro
       #13

    ComputerGeek said:
    > Do you still have Code 39? When you do, in DevManager right click the device->Properties->Details tab. Use the pulldown and look if either Class uppper filters and/or Class lower filters exist. If yes, then post their values.
    > Which version of the audio driver do you currently have installed?

    Again, right click to Properties->Details tab
    1. Use pull down menu to look for two items: inf name and something like matching device id. Post the result
    2. Windows renames the original INF to oem.nnn. We want the original name. From command prompt

    Code:
    disk /online /get-drivers
    The output shows oem vs. original filename pairs. What's the original filename of the INF used to install your Realtek audio driver?
    Latest Realtek HD Audio Driver Version-filters.jpg
    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
      My Computer


  4. Posts : 89
    Windows 10 Pro
       #14

    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.
      My Computer


  5. Posts : 268
    Windows 10 Pro x64 v22H2
       #15

    wiggly1uk2000 said:
    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!

    You got where I was going on your own and ahead of me! :)

    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
    Last edited by ComputerGeek; 06 Jan 2017 at 09:16.
      My Computer


  6. Posts : 3,506
    Windows 10 Pro 64-bit 21H1 (May 2021 build 19043.1083)
       #16

    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.
      My Computer


  7. Posts : 89
    Windows 10 Pro
       #17

    ComputerGeek said:
    Excellent, EXCELLENT job!

    You got where I was going on your own and ahead of me! :)

    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

    Also, IMHO
    Troubleshooting documentation about filters usually advise deleting class upper and lower filter keys if found in the registry. I disagree! That can fix one problem but cause another. There can be one or more upper/lower filters in either key. Deleting the key removes ALL the filters defined in the key - some of which can be for products you're still using and now they can starting having problems because their driver filter has been deleted. Filter keys are text strings. Simply edit the string to remove the offending filename reference. (of course, always creating a system restore point prior to a regedit)

    /* EDIT */
    Only edit the filter filename out of the key if there's more then the one filename in the key. Otherwise, delete the key. I also found a case where a filter key existed in the registry with no filter names defined also cause problems (i.e. the key just contained any empty string)

    /* EDIT 2 */
    If you do delete the an upper/lower filter registry key which included a filter for a program still needed, uninstall / re-installing the program should cause it to put that filter needed back in the registry
    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.
      My Computer


  8. Posts : 3,506
    Windows 10 Pro 64-bit 21H1 (May 2021 build 19043.1083)
       #18

    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.
      My Computer


  9. Posts : 89
    Windows 10 Pro
       #19

    spapakons said:
    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!
      My Computer


  10. Posts : 19,516
    W11+W11 Developer Insider + Linux
       #20

    spapakons said:
    Then I'm afraid you are stuck with the older version until something better comes out.
    Yup, that's called AM4 motherboard with Ryzen processor.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:39.
Find Us




Windows 10 Forums