-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Audio
- No input or output devices detected after win 10 upgrade to ...
![Sign in](/html/assets/sign-in-banner.png)
Create an account on the HP Community to personalize your profile and ask a question
09-14-2020 02:46 PM - edited 09-16-2020 07:23 AM
After windows 10 upgrade to version 2004 to my HP Spectre x360 Laptop - 15-eb0003na, I noticed no sound and a red cross on the speaker icon.
Both trouble shooters Windows/HP indicate "no devices found" (speakers or microphone) and no realtec entries in device manager, however UEFI Diagnostics produce sound from the speakers without problems.
I have downloaded and installed the latest bios and sound drivers without success.
I can get sound using a bluetooth sound bar but not plug in headphones.
Solved! Go to Solution.
Accepted Solutions
09-16-2020 10:22 AM
Fixed - whilst waiting for advice I continued with my research,
in Device Manager I discovered a little yellow triangle against the Intel(R) Smart Sound Technology (Intel(R) SST) OED
entry, just updating the driver did nothing, but deleting the device (AND deleting driver software) then restarting cured the problem. (it took a couple of minutes after the restart.)
09-16-2020 10:22 AM
Fixed - whilst waiting for advice I continued with my research,
in Device Manager I discovered a little yellow triangle against the Intel(R) Smart Sound Technology (Intel(R) SST) OED
entry, just updating the driver did nothing, but deleting the device (AND deleting driver software) then restarting cured the problem. (it took a couple of minutes after the restart.)
Didn't find what you were looking for? Ask the community