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

Wynona said:

Did you get sound to work, @magilla? And if so, what did you do to make it work?

Thanks in advance . . .

No, I haven’t had any luck. I rolled back, then reinstalled, only to find the reinstall failed, so I’m still on 18290. I’m attempting another reinstall. I’ll let you know what happens. It’s strange to see other systems upgrading with sound but this one just had none.

Tweet

— Twitter API (@user) View on Twitter

Tweet

— Twitter API (@user) View on Twitter

emilcioran99 said:

@Wynona, drivers for... what?
As I said here the system at boot didn't recognize any sound controller so... install driver for what?
In Device manager there is no sound controller at all in sound, video and game controllers other than Nvidia virtual audio, BUT in system device there is an sound controller (that in 18290 wasn't there) High definition audio controller with an M$ generic driver (10.0.18298.1000) that didn't work at all. The device status is "This device cannot start. (Code 10) {Operation Failed} The requested operation was unsuccessful." and the error is:
Device PCI\VEN_8086&DEV_A348&SUBSYS_1BC01043&REV_10\3&11583659&0&FB had a problem starting.

Driver Name: hdaudbus.inf
Class Guid: {4d36e97d-e325-11ce-bfc1-08002be10318}
Service: HDAudBus
Lower Filters:
Upper Filters:
Problem: 0xA
Problem Status: 0xC0000001

Tried to install 4-5 Realtek drivers but at the end run into BSOD and restarts.
Tried to install an Intel driver but no luck at all, so I opened an ticket in Feedback hub yesterday in the morning.
I saw that there are opened more over 30-40 discutions about this bug.

As I saw, the problems are when there are Intel chipsets + Realtek + Nvidia display.


PS:
Sorry for my english!
It's not my primary language and didn't use it regularly to improve it.

Interesting that device managers has nothing about sound, video, and game controllers. My system identifies the sound controllers, IDT and nVidia but can’t install sound drivers. I have reinstalled this build twice and get nowhere with that.
Ps. Your English is very good.

Wynona said:

I was told there were no drivers installed, @emilcioran99! Using Device Manager, I told it to update drivers and it installed something but then told me again that no drivers were installed.

Did you try with manufacturers drivers?

emilcioran99 said:

@Wynona, drivers for... what?
As I said here the system at boot didn't recognize any sound controller so... install driver for what?
In Device manager there is no sound controller at all in sound, video and game controllers other than Nvidia virtual audio, BUT in system device there is an sound controller (that in 18290 wasn't there) High definition audio controller with an M$ generic driver (10.0.18298.1000) that didn't work at all. The device status is "This device cannot start. (Code 10) {Operation Failed} The requested operation was unsuccessful." and the error is:
Device PCI\VEN_8086&DEV_A348&SUBSYS_1BC01043&REV_10\3&11583659&0&FB had a problem starting.

Driver Name: hdaudbus.inf
Class Guid: {4d36e97d-e325-11ce-bfc1-08002be10318}
Service: HDAudBus
Lower Filters:
Upper Filters:
Problem: 0xA
Problem Status: 0xC0000001

Tried to install 4-5 Realtek drivers but at the end run into BSOD and restarts.
Tried to install an Intel driver but no luck at all, so I opened an ticket in Feedback hub yesterday in the morning.
I saw that there are opened more over 30-40 discutions about this bug.

As I saw, the problems are when there are Intel chipsets + Realtek + Nvidia display.


PS:
Sorry for my english!
It's not my primary language and didn't use it regularly to improve it.

Thank you for this, @emilcioran99. Your English is fine.

As I saw, the problems are when there are Intel chipsets + Realtek + Nvidia display.

This is an AMD chipset machine, so it's not just Intel machines that have the sound problem!

AndreTen said:

Did you try with manufacturers drivers?

Andre, read Post #124 and let me know what you think? From what he says, and from a friend who's read it too, there seems to be nothing we can do to fix the problem. The ball's in Microsoft's court for now . . .