New
#1411
It always amazes me how many variants of a single Realtek HD driver Microsoft can come up with.
If you have a look at the MUC now there are 8 seperate downloads for build 7968
UPDATE
Looking at all the variants in more detail 4 of the drivers are ASUS specific.
Hi,
Thanks DooGie.
I guess the remainder must the pre and the post AU, 32 and 64 bit.
Cheers,
Yep, I always wondered about that too. Usually all the downloads are essentially the same anyway. The ones marked with Asus are smaller because they must remove certain things? But what they remove probably doesn't get installed anyway if use the other download (which I do; I always pick the bigger Realtek one even though I have an Asus motherboard).
Yes, the non-Asus drivers have more .inf files for Dell, etc and more .dll files to accommodate different implementations on various motherboards as well as branding differences. The rest are broken down by 32 vs 64 bit and Pre and Post Win10 Anniversary update.
So after attempting to rule out the placebo effect, I guess I have to agree, the fidelity of music does seem noticeably improved. Overall clearer and cleaner sound for sure. It sounds like there's better frequency separation, like the sounds of instruments and even voices seem more distinct in the mix. It's like on-the-fly remastering! lol
Harder to tell sound improvements with game action, but seems crisper at least.
Thank you, most users have found these drivers a good improvement over previous versions. as you say the separation of different instruments is clearer. The bass is still deep though and not boomy.
As for gaming I don't know, if I game with sound through the speakers my Wife always comes upstairs and tells me to shut up and stop killing all those people :) .
I now game using a Corsair Void USB headset.
Exact same boat here. I'm convinced that:
1. Microsoft broke something in a previous update that killed DISM
or
2. The CAB is packaged incorrectly.
or
3. We're both morons
I went through the exact same steps you did (changing permissions, renaming, moving file to root of drive) and nothing works. I even set "Everyone" as the owner on the file and that got me nowhere too. The last time I ran into something this bizarre, Microsoft pushed an update a week later and it was magically fixed.
sfc /scannow reports no issues, btw.