Since HP BIOS update no audio output device detected

[TroyS1]

Fixed my issue in less than a minute

Thanks

Peace

[jpdx1]

same issue. our bug is here: https://h30434.www3.hp.com/t5/Desktop-Audio/Windows-Update-installed-HP-Inc-Firmware-15-58-0-0/m-p/7...

[Ken_K5RG]

I've had this problem with HP Support Assistant for over 8 months and this is the second time I've lost the Realtek audio drivers after an HP initiated update.  Under my device manager the only sound hardware driver is the NVIDIA Virtual Audio Device (WDM).  The Realtek High Def Audio driver linkage is completely gone.  Resorting to a System Restore that was automatically performed prior to the HP Update (believe it was a BIOS update, this is my wife's machine) states that it will DELETE the Realtek 12/3/2019 2024.0.10.209 (oem91.inf) driver which will be a real trick since no Realtek drivers are currently shown by the Device Manager.  When I had this problem 8 months ago, HP support was essentially lost so I had to reimaging my SSD (I do regular backups) which looks like I will have to go thru this once again.  I thought I had stopped the HP Support Assistant but I will once again uninstall the program and waste another two hours of my life restoring the SSD (Windows Image) which is few days old so I will have to follow up with a File and Folder restore that is current as of today.

[Ken_K5RG]

I'll take back my previous post, the marked solution is correct but works just a little different for my HP Envy which initially threw me off.  As stated, the audio driver that needs to be updated in the Device Manager is under System Devices shown as Microsoft Smart Sound Technology with the giveaway of a yellow splotch. For my HP Envy All-in-One 27-b245se, the screwed up/missing driver is not under Sound, video and game controller. After updating the yellow splotched Smart Sound Technology driver, this driver listing disappears and the Realtek High Definition Audio driver reappears under the Sound, video and game controller heading in the Device Manager as stated in the marked solution.  So as some previous postings have indicated, the fix is easy but depending on your specific system there might be some slight differences in execution.