New Windows 10 Insider Preview Fast + Skip Build 18298 (19H1) -Dec. 10 Insider

smactilactus said:

Thanks Brink! Hate to sound like a noob, but just never have thought about changing it, and wanted a quick answer. Thanks for providing one.

You're most welcome.

Wynona said:

Hmmm, you have a comparatively new Intel chipset and I have a comparatively old AMD chipset. What does that tell us?

I'm on AMD 970 chipset right now, and sound is working fine (Gigabyte MB).

emilcioran99 said:

Reverted and sound is back.
Now in device manager have 3 devices:
- Intel display audio;
- Nvidia virtual audio device;
- Realtek HD audio.
With 18298 have only Nvidia virtual audio device.
Will try to download the 18298 and clean install to see if there is no sound like installed with WU.

@Wynona (too) and @emilcioran99
This is how my drivers looks like:

smactilactus said:

So my question is this, why can you change a font for "most" of the sys, but it doesn't change in the one place you look at the most, the start menu??? Lol. I will NEVER understand M$. The one place you would want the change the most, as it's what you see the most, is the start menu, and of course M$ blocks the font change there. Wow! So I guess there's not a way to change the font in the start menu, or is there a reg file which will handle that?

I'm not aware of a way to change the font in the Start menu unless some 3rd party program may have a setting for it.

Wynona said:

Thanks, Magilla. So, basically, the hardware that worked on an older version (October Build 17763) of the audio/sound hardware, but the latest version (Build 18298) won't accept the hardware. So . . . in approximately two short months, Microsoft changed something that made our sound sound cards fail.

@Wynona. See you have IDT sound chip. Try this drivers (newest at the top)

www.catalog.update.microsoft.com

AndreTen said:

@Wynona (too) and @emilcioran99
This is how my drivers looks like:

Interesting - we all have different configurations some of which work and some not. I rolled back to previous build again but am doing a clean install to see if that makes any difference — probably not but what the heck, worth a try.

AndreTen said:

@Wynona (too) and @emilcioran99
This is how my drivers looks like:

Here are my drivers in 18290. Note that my IDT High Definition Audio CODEC is included in this Build.

And here's what it looks like in Build 18298. Note that my IDT High Definition Audio CODEC is not included in this Build, nor was I able to install drivers for it.

I'm pretty sure it's a problem created by Microsoft, Andre. Microsoft has changed something that fails to recognize the hardware. Although this source article is from 2014, I'm pretty sure it has some of the answers we need, although, as far as I can tell, no solution.

Here's why I think it's all Microsoft's baby . . . HD Audio Bus Driver - Windows drivers | Microsoft Docs