
The speaker icon has a red X. Realtek HD Audio Manager has disappeared from the system tray. Sound stopped working after last night's Windows update. These are the three most common ways Realtek audio driver problems announce themselves — and they all point to the same underlying issue: the Realtek driver has been replaced, corrupted, or disabled by Windows. The hardware itself is almost never the problem. This guide walks through every fix in order, from the fastest checks to the most thorough solutions.
What Causes the Realtek Sound Driver to Stop Working
The most common cause is a Windows Update that silently replaces the Realtek OEM driver with a generic Microsoft audio driver. The generic driver installs without errors and Windows reports the device as working, but it lacks Realtek-specific features and sometimes doesn't produce any audio output at all
Other causes include a Windows Update that corrupted the existing Realtek driver during installation, a failed driver update that left the device in an error state, conflicting audio software like Dolby Atmos or Nahimic preventing Realtek from initializing correctly, the Realtek audio device being silently disabled during a system event, or the wrong Realtek driver version being installed manually for a different hardware variant
Quick Diagnosis Before You Start
Before picking a fix, identify which state the Realtek device is in. This takes about sixty seconds and tells you exactly which path to follow.
Right-click the speaker icon in the taskbar. If it shows a red X with the message no audio output device is installed, the driver is missing or the device is disabled
If the Realtek entry is present with no error icon, the driver is installed but something else — a service, a setting, or a conflict — is preventing audio output. If a yellow exclamation mark appears on the Realtek entry, the driver is corrupted or incompatible
If no Realtek entry appears at all, the driver is completely missing. Each of these states has a different fix path

Fix 1: Run the Windows Audio Troubleshooter
On Windows 10, go to Settings, then Update and Security, then Troubleshoot, then Additional troubleshooters. Select Playing Audio and click Run the troubleshooter
On Windows 11, go to Settings, then System, then Troubleshoot, then Other troubleshooters. Click Run next to Playing Audio

Apply any fixes the troubleshooter suggests and restart. If it reports no issues found but sound is still not working, proceed with the manual fixes below.
Fix 2: Re-enable the Realtek Device in Device Manager
A Windows update may have disabled the Realtek audio device silently. Open Device Manager and expand Sound, video and game controllers. If the Realtek entry has a small downward-pointing arrow on its icon, the device is disabled. Right-click it and select Enable device.
If no Realtek entry appears in Sound, video and game controllers, click View in the Device Manager menu and select Show hidden devices. Greyed-out entries for previously installed hardware will now appear
If a Realtek entry shows up there, right-click it and select Enable device. Restart and test audio
Fix 3: Update the Driver via Device Manager
Right-click the Realtek audio entry in Device Manager and select Update driver
Choose Search automatically for drivers
If Windows finds and installs a driver, restart and test

A red X on the speaker icon, a missing Realtek HD Audio Manager, or sound stopping after a Windows update are all signs of Realtek audio driver issues. In most cases, the driver has been corrupted, disabled, or replaced by Windows — the hardware itself is rarely at fault. This guide walks you through every solution, starting with quick checks and moving to more comprehensive fixes.
Fix 4: Update the Realtek Driver Using Driver Sentry
This is the most reliable fix for getting the exact correct Realtek driver installed. Realtek produces multiple audio chip variants — the ALC887, ALC892, ALC897, ALC1220, and others — and each requires a specifically matched driver. Installing the wrong variant either produces an error or installs in a limited state that doesn't fully support the hardware
Driver Sentry identifies the exact Realtek chip model in your system by reading the hardware ID and matches it to the correct driver version automatically. This eliminates the guesswork that leads to installing an incompatible version

This method is effective in all three diagnosis states: when Device Manager shows an error on the Realtek device, when Windows installed a generic driver in place of Realtek, and when no Realtek entry appears in Device Manager at all.
Fix 5: Download the Realtek Driver from Your PC Manufacturer
Go directly to the manufacturer's support page. Search for your exact laptop or motherboard model and download the audio driver listed there
If you're unsure which version to download, Driver Sentry identifies the correct OEM-matched driver for your hardware and installs it automatically, which is faster than navigating manufacturer support pages

Fix 6: Remove Conflicting Audio Software
Dolby Atmos, Nahimic, DTS Sound Unbound, and similar audio enhancement applications install alongside the audio driver and modify how Windows handles audio output
Go to Settings, then Apps. Search for Dolby, Nahimic, DTS, or any audio enhancement software that was installed with your laptop. Uninstall each one
Restart the PC and test audio with Realtek running on its own. If audio returns, reinstall the enhancement software only after confirming Realtek is stable

Fix 7: Restart Windows Audio Services
Press Win + R, type services.msc, and press Enter. Scroll to Windows Audio. Right-click it, select Properties, set the Startup type to Automatic, and click Start if it's currently stopped
Apply and close. Repeat the same steps for Windows Audio Endpoint Builder. Restart the PC and test audio

Conclusion
Windows Update replacing the Realtek driver with an incompatible generic version is responsible for the majority of Realtek sound driver failures. Fix 4 using Driver Sentry resolves this directly by identifying the exact Realtek chip variant and installing the correct matched driver, including the HD Audio Manager that the generic Microsoft driver doesn't provide.