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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-06-13T19:16:11+00:00

    SFC and even DISM didn't work for me sadly. I even tried in Safe mode and tried forcing it to use an ISO download of 21H1. SFC finds no integrity violations.

    I should add that along with this audio issue, after the BSOD on the first attempted (and failed) update, it actually had changed my login screen to require CTRL+ALT+DELETE, and it also enabled the Administrator account (login was never attempted based on 'net user' info.

    I should also mention that this problem occurred for me with the 21H1 CUMULATIVE update that happened this past Tuesday the 8th. It still can't install that update. I've been using 21H1 without issue for a while now, so I can't revert.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-06-12T00:14:07+00:00

    Not a good situation. I hope we don't have to do this little exercise every day until the Judgement Day...

    Waiting for the FIX

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-06-11T23:26:46+00:00

    This works, this so stupid... Thanks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-06-11T23:22:32+00:00

    Guys Window 10 21H1 the sound system is broken. Loading Drivers does not work. Reloading the OS does not work. Resetting the OS does not work. Microsoft when are you releasing the FIX. Until we getting a some what working version of Windows 10 21H1, I will not be recommending anyone to upgrade. Yes, I have tested USB sound cards, Bluetooth speaks, non work.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-06-11T19:19:48+00:00

    Yes it seems visiting the sound setting dialog via ease of use is enough for it to work again although previously it reverted back to not showing any devices and the workaround didn't help until a reboot.

    I am using an old Realtek chipset as well but also have a Sharkoon USB DAC which also does not work.

    Before first experiencing this issue some update lead to a bluescreen which I could fix with safe mode and sfc /scannow

    After that suddenly the audio issue appeared. Note that I only did trigger the 21H1 update afterwards (as I thought why not - it won't get worse) and it was not listed as failed. Therefore I believe that the issue can also be caused by some other update (or Windows for some reason tried to install 21H1 automatically, failed but didn't show it in the log)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments