Windows 10: Latest Realtek HD Audio Driver Version
Well, Creative started all sound card trend with first Sound Blaster. I had me one of those first ones, it included connector for proprietary CD player. Sound was lousy and noisy as hell but it worked. Couple of interesting programs came with it, Dr Sbaitsu and Parrot.
In those early PCs AT keyboard controller was actually a sound chip, there was a driver for Windows 3.1 to use it as default sound device thru speaker connected to MB and used as POST sound device.
Only after few years came out outrageously priced Turtle Beach and others.
Interesting stuff regarding Creative/Realtek and a good explanation of the hardware ID locking but I'm still confused as to why the 8023 drivers are missing the Creative driver components. Whilst I'm quite sure that many Realtek audio codecs don't require these Creative drivers, my motherboard seems to be mute without them! And yet, it does not contain any Creative hardware, just a Realtek ALC1150 with the option to run additional Creative audio processing software (bundled with the motherboard but never installed since I don't need it).
Oh well, back to 8010 until I can find the answer. Perhaps I'll keep trying each new driver release until I find one that works.
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.
> 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
- Use pull down menu to look for two items: inf name and something like matching device id. Post the result
- Windows renames the original INF to oem.nnn. We want the original name. From command prompt
The output shows oem vs. original filename pairs. What's the original filename of the INF used to install your Realtek audio driver?
disk /online /get-drivers
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:
UPDATE: For anyone remotely interested I managed to get 8023 working by editing the hdxmb3h.inf file and removing the following lines:
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.
Last edited by ComputerGeek; 06 Jan 2017 at 09: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.
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.
Hello : I have my realtek driver tweaked in windows 7 , I have it set in the registry to have 2 outputs , instead of one - will the new win 10 driver be able to be adjusted ...
I have a Jabra bluetooth speaker (the Solemate Mini). On Windows 8.1 I plug it in to my laptop using the 3.5mm to 3.5mm cable and then, when I watch a movie, it correctly outputs to the speaker and does not use my laptop speakers....
New RealTek HD Audio Driver available in WU.
My ASUS M4N68T-M V2 has a VIA VT1708S onboard audio. The driver I have that worked in Windows 8.1 v10_1200a won't work in 10. Windows doesn't even see the onboard video so it doesn't even look for a driver. It doesn't show up in device manager. In...