Problem with Windows 10 ver. 21H1 -- all audio input/output devices missing in Sound settings, red X on volume icon

Anonymous
2021-05-19T09:59:57+00:00

For 2-3 days, I am getting no sound at all from my several audio devices/Windows computer here - I have TWO monitors with HDMI audio, plus headphones jack connected to motherboard audio card. I was able to fix it one time by doing lots of tinkering in Device Manager, but I am unable to replicate the fix a 2nd time.

So, asking here.

System is a desktop PC, running an Intel Core i3 Haswell CPU (2 cores, 4 threads), 16 GB of DDR3 RAM, on a ASUS H81M2 motherboard, GPU is AMD Radeon R9 390 (8 GB). Audio card is the built-in Realtek. 1 Crucial SSD, plus 2 HDDs -- WD and Seagate. Logitech Full HD webcam , Logitech wireless mouse, wired Razer keyboard.

The volume icon in lower right (Notification area) shows with a red X. In Settings of Windows 10 OS, Sounds, NO input or output devices show at all.

No sounds possible in any software, i.e. browser, actual OS does not make the Start Windows sound like it used to/etc.

Also, no recording or voice chat possible with my Logitech webcam (which has a stereo microphone), so no Skype, Viber/etc voice calls.

In Device Manager, nothing shows wrong - all audio, system devices appear to be working fine. In AMD Radeon GPU settings, nothing wrong shows either.

I tried the Windows 10 Sound Troubleshooter, but it unfortunately says it cannot identify the issue.

What can I do to fix this?

(Please do not suggest a reinstall Windows OS or Reset OS, I cannot do those.)

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

144 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-06-09T22:07:33+00:00

    The problem is due definitely to Version 21H1 update.

    I manage many PCs, some of the after upgrading goes BSOD during boot some other I did not have mic and hedphone any longer.

    I did some test and I discovered that if you remove realtek drivers, systems boot correctly but you lose the ability to have an imput device and switch to a different output port.

    Otherwise if you rollback the 21H1 upgrade everything comes back to normality and you have everything working.

    Given this I strongly reccommend to upgrade to 21H1 only when a reliable audio driver will be proposed by realtek or (better) Microsoft itself.

    Al the tests I made are done on x64 version and 6 PC/Latops ranging form 10 to 1 years old.

    You see with smart working a pc without audio is nearly useless.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-06-09T17:34:15+00:00

    Being crystal clear, before 21h1 the behaviour is the one JohnD told about.

    After installing 21h1 depending on the pc you can have normal behaviour, only speaker available (no headset or mic option) or bsod (on older computers with realtek software).

    Currently if you face the proble you have two options:

    start in safe mode and unistall realtek drivers package (with this you will be able to boot windows but no headphone or mic available)

    start in safe mode and unistall 21h1 ( evething then start to work again.)

    I have chosen the second option.

    I hope that either Microsoft or Realteck will fix it.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-05-31T10:37:15+00:00

    This is incorrect!

    Yes, the fix has nothing to do with sound controllers, that part is correct.

    But the actual problem is exactly with them (plus input devices such as microphones).

    Hi,

    Some update.

    I did a clean install on a separate SSD yesterday. Installed 21h1 (Build 19043.985) - sound input/output controllers works fine. Then updated to a build 19043.1023 - the same thing, sound works just fine.

    My best guess, a problem somehow related to Windows audio service. But to confirm/deny that I'll have to find some time to do more digging.

    BR

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2021-05-20T13:12:30+00:00

    No worries, thanks for trying to help me. :) No need to apologize.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2021-05-20T10:08:24+00:00

    I see. I'm sorry to hear that. And I'm really sorry if the solutions I provided above could not help. Maybe someone else here in the community will have a solution for you. Again, I do apologize for the inconvenience.

    Kind regards,
    Benedict P.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments