Latest Realtek HD Audio Driver Version [2]

  1. MoKiChU's Avatar
    Posts : 20
    Windows 10 64 bit
       #3221

    Andy Roid said:
    Now I'm counting days till I'll boot machine and have no sound.
    There is no reason for Windows Update to try to touch your drivers knowing that you have the latest drivers suitable for your hardware. So, for the next drivers packages that I would release, you will can directly follow your UPDATE process and you will have no worries.
      My Computer


  2. Posts : 8
    Windows 10 Professional x64 Version 1909
       #3222

    MoKiChU said:
    There is no reason for Windows Update to try to touch your drivers knowing that you have the latest drivers suitable for your hardware. So, for the next drivers packages that I would release, you will can directly follow your UPDATE process and you will have no worries.
    I didn't turn off internet because WU, it never touched any of my drivers (actually only once, when Windows updated and was incompatible with Intel gfx driver so I didn't have output on HDMI, only DVI). I disconnected internet simply to avoid getting older Audio Console (for v8750) after complete rollback, then getting it back when reinstalling.

    What worries me is that I possibly can not install HDA v9126+.
      My Computer

  3. MoKiChU's Avatar
    Posts : 20
    Windows 10 64 bit
       #3223

    Andy Roid said:
    What worries me is that I possibly can not install HDA v9126+.
    Even though they keep updated from time to time, HDA drivers get depreciated over time, so what you see doesn't really surprise me, given that your motherboard is UAD compatible, it's UAD drivers that must take over from your HDA drivers (the only reason why you don't have UAD drivers in your motherboard support page is that your motherboard is EoL).
      My Computer


  4. Posts : 8
    Windows 10 Professional x64 Version 1909
       #3224

    MoKiChU said:
    Even though they keep updated from time to time, HDA drivers get depreciated over time, so what you see doesn't really surprise me, given that your motherboard is UAD compatible, it's UAD drivers that must take over from your HDA drivers (the only reason why you don't have UAD drivers in your motherboard support page is that your motherboard is EoL).
    Yes, it is EoL'd but I hate artificial obsolescence, and it obviously was artificial as some boards got UAD at the beginning of 2018, I got Firmware update due to Spectre and Meltdown exploits mid 2018 and they never touched anything else after that, except useless AppShop.

    - - - Updated - - -

    I found some info on Microsoft Docs page about Hardware IDs and will quote one part of it:
    "pnp-hardware-id"
    This value specifies a PnP device hardware ID. The hardware ID must be enclosed in double quotation marks (").

    The hardware ID can be fairly generic, such as PCI\VEN_1234&DEV_1234, or very specific, such as PCI\VEN_1234&DEV_1234&SUBSYS_12345678&REV_01.
    After all, it seems that .inf files support various degrees of generic HWIDs.
    So basically if the HWID is HDAUDIO\FUNC_01&VEN_10EC&DEV_1220&SUBSYS_18491220, the line:
    Code:
    "Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_1220&SUBSYS_18491220
    should work just as the line:
    Code:
    "Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_1220
    The second line is more generic and Device Manager probably looks first for the most specific HWIDs, then more generic ones until it either finds match and proceeds according to that .inf, or returns error if there is no match.

    Of course, this is just my theory I can't confirm yet...
    Last edited by Andy Roid; 1 Day Ago at 20:12. Reason: new info
      My Computer

  5. ddelo's Avatar
    Posts : 2,228
    Windows 10 Pro x64
       #3225

    Andy Roid said:
    The second line is more generic and Device Manager probably looks first for the most specific HWIDs, then more generic ones until it either finds match and proceeds according to that .inf, or returns error if there is no match.

    Of course, this is just my theory I can't confirm yet...

    To my knowledge so far, I don't think that Device Manager goes past the check of the entire HWID. i.e it doesn't look further if it doesn't find the complete HWID, the one that includes the SUBSYS_XXXXXXXX part. If it doesn't find the entire HWID in any inf file, it reports that the most recent driver is installed.

    To install the more generic one, the one without the SUBSYS_XXXXXXXX string, you need to force install it, using pnputil.
      My Computer


  6. Posts : 8
    Windows 10 Professional x64 Version 1909
       #3226

    ddelo said:
    To my knowledge so far, I don't think that Device Manager goes past the check of the entire HWID. i.e it doesn't look further if it doesn't find the complete HWID, the one that includes the SUBSYS_XXXXXXXX part. If it doesn't find the entire HWID in any inf file, it reports that the most recent driver is installed.

    To install the more generic one, the one without the SUBSYS_XXXXXXXX string, you need to force install it, using pnputil.
    Thanks ddelo for your valuable input, I was afraid my "theory" has a hole. I now remember looking at pal1000's unofficial drivers and there is an extension inf file with short HWIDs which is force updated and I wondered why... now I know. Maybe I should take a look at your power shell scripts for HDA and UAD suitability.

    Anyway, my v9137 UAD stopped working today (5th day since install) after reboot as WU installed a cumulative patch. Don't know how to tell if this is HW of SW issue except going back to HDA - maybe my board is just not compatible with UAD drivers?
    BTW, I never booted into Linux without sound or lost sound while working under it.
      My Computer

  7. ddelo's Avatar
    Posts : 2,228
    Windows 10 Pro x64
       #3227

    Andy Roid said:
    Thanks ddelo for your valuable input, I was afraid my "theory" has a hole. I now remember looking at pal1000's unofficial drivers and there is an extension inf file with short HWIDs which is force updated and I wondered why... now I know. Maybe I should take a look at your power shell scripts for HDA and UAD suitability.

    Anyway, my v9137 UAD stopped working today (5th day since install) after reboot as WU installed a cumulative patch. Don't know how to tell if this is HW of SW issue except going back to HDA - maybe my board is just not compatible with UAD drivers?
    BTW, I never booted into Linux without sound or lost sound while working under it.
    You're most welcome.
    I really don't know if you need to go back to HDA drivers, which is what I would recommend, if you hadn't got @MoKiChU opinion that you have a UAD capable board.

    MoKiChU said:
    Even though they keep updated from time to time, HDA drivers get depreciated over time, so what you see doesn't really surprise me, given that your motherboard is UAD compatible, it's UAD drivers that must take over from your HDA drivers (the only reason why you don't have UAD drivers in your motherboard support page is that your motherboard is EoL).
    MoKiChU is a well respected expert and his opinion matters.
      My Computer


  8. Posts : 8
    Windows 10 Professional x64 Version 1909
       #3228

    ddelo said:
    You're most welcome.
    I really don't know if you need to go back to HDA drivers, which is what I would recommend, if you hadn't got @MoKiChU opinion that you have a UAD capable board.



    MoKiChU is a well respected expert and his opinion matters.
    Yes, I am aware of both things, really. I already switched to UAD v9137 supplied here by MoKiChU.

    But as I mentioned, my audio was OK when I booted PC today, then Windows Update came with cumulative update so I confirmed installation and rebooted when prompted. After that the audio was muted and I had to reboot once more. Four days UAD was working fine, failed on fifth. It really drives me crazy, as I don't know how to determine where is the fault.

    There is one other issue I had that illustrates how things are not simple. I have a "backplate" with 4 USB ports on outer side, the inner side has thick plastic which holds the ports. There is a thick cable with connector going into motherboard USB 2.0 header. So basically, I have 4 USB 2.0 ports that I use for keyboard, mouse(s) and particular USB stick. That stick was used on 30th Jan to install 480 MB of Chrome Portable and mid Feb to create 2.5 GB live Linux media. A couple of weeks later, I tried to reinstall the very same Chrome on stick, but the stick disconnected. When I tried to extract archived version of it, the stick again disconnected. In short, copying anything bigger than 20 MB would cause stick to disconnect mid writing.
    I looked up for solutions and they were "disconnect all other devices to prevent voltage drop", "disable USB suspend in power plan", "untick power control on Power Management tab in device manager for USB Hub", "your board has aged caps and voltage is not stable". All nonsense, as that stick worked month ago...
    I booted Linux, created 480 MB file and copied it to stick. The 'cp' ended instantly due to write buffers so I quickly typed 'sync' to force writing and expecting I/O error. But the copy succeeded. I did another 'cp' without forcing immediate write buffer flush but it again succeeded.
    So what can I conclude from this? Linux can write on stick which started confusing Windows in the last couple of weeks. I would bet there is no hardware issue, there was another cumulative update in between, who knows what it changed.
    Heck, I have Windows Spotlight showing me an infamous "lake and red backpack" picture 5 out of 7 days. I'm pretty sure mid-school student would program it right.

    So, it's very hard for me to tell why UADs keep failing on my board. The above problem is somewhat off topic but is a good illustration that one has to be careful saying "the board is bad".
    I apologize for the length of the post...

    - - - Updated - - -

    MoKiChU said:
    Either he does not try to update his drivers and in this case he switches to the HDA drivers from the support page of his motherboard (or the last ones containing his HW ID)
    My board is supported up to v9116, support page has v8051. A big difference, like 4 years.

    MoKiChU said:
    Either he tries to update his drivers and in this case, he must use the UAD drivers as I explained to him previously.
    I did everything "by the book"... literally. Second attempt and running UAD v9137.

    MoKiChU said:
    If Windows Update is in error concerning your audio drivers, it is because your drivers configuration is exotic as I explained previously (HDXAsrok.inf as main driver & HDX_WhiteExt_RTK.inf as extension driver), and Microsoft package the Windows Update/MUC full drivers packages independently for the WHITE Realtek audio drivers (with HDXWHITE.inf as main drivers and not HDXAsrok.inf which you need, hence the loss of sound), example : http://download.windowsupdate.com/c/...1843d5ff7d.cab
    Windows Update doesn't interfere with my drivers, it never did. I have no problems whatsoever caused by Windows Update when it comes to audio drivers. It's not the issue for me. That link is for UAD v9098, I still have v9137 installed, it wasn't touched by WU in any way.
      My Computer

  9. ddelo's Avatar
    Posts : 2,228
    Windows 10 Pro x64
       #3229

    @Andy Roid

    I would have gone back to the latest HDA drivers, accepting the fact that I have an older board and UAD drivers might not be the best solution for me.
    But, that's only my opinion!
      My Computer


  10. Posts : 8
    Windows 10 Professional x64 Version 1909
       #3230

    @ddelo

    Yes, that was my idea since the first post, I was asking about most recent ASRock HDA drivers, hoping that ASRock haven't discontinued support for my board (there is really no technical reason for that). But it turned out two latest ASRock HDA drivers already removed my board, quite too soon...
    My sister has MSI H81M-E33 board from 2013 and she got Utility updates two days ago, Realtek Ethernet driver was updated 21st Jan this year... it's still not EoL'd.
      My Computer


 

  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 04:03.
Find Us




Windows 10 Forums