Troubleshooting Realtek audio is an exercise in fault isolation: the sound path runs from application to Windows audio engine to driver to codec chip to speaker, and your job is to find which link is broken. This guide treats the problem like a technician would — testing each layer and only reinstalling drivers once the evidence points there. It complements our step-by-step Realtek repair guide with a deeper diagnostic method.

Start with the cheapest tests. Play audio from two different applications, test both speakers and headphones, and check whether Windows even registers the playback device. Each answer narrows the field. A fault that affects everything points at the driver or services; a fault limited to one app or one output points at settings. Resist the urge to reinstall drivers first — half of all “no sound” cases are routing or mute problems that a reinstall will not touch.

Why this happens

  • Driver model mismatch (HDA vs UAD): Mixing legacy HDA drivers with Universal Audio Driver packages leaves the codec half-configured and silent.
  • Realtek service not running: The Realtek Audio Universal Service fails to start, so the driver stack never completes initialization.
  • Power management sleeping the codec: PCI power management puts the audio device to sleep and it never wakes, killing sound until reboot.
  • Application-level output misrouting: Per-app settings in the volume mixer send audio to a device that no longer exists.
  • Corrupt driver store entries: Partially uninstalled drivers linger in the driver store and get reapplied on every boot.
  • Conflicting audio software: Nahimic, Waves MaxxAudio, Dolby, or third-party EQs install APO filters that crash the pipeline.
  • Windows feature update driver replacement: The update process swaps in a generic driver that lacks the correct codec verbs for your machine.
  • Hardware degradation: Failed capacitors or a cracked codec chip after heat cycles or liquid exposure — rare, but definitive when present.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Map the fault with controlled tests

Before changing anything, run a quick test matrix. Play a YouTube video and a local media file (two apps), listen on speakers and on wired headphones (two outputs), and watch the volume mixer to see if the green level bars move when audio “should” be playing. Moving bars with no audible sound means the signal reaches the driver but dies at the codec or speaker — a driver or hardware fault. No moving bars means the problem is upstream in routing or the app.

  1. Play audio in two different applications.
  2. Test built-in speakers and wired headphones separately.
  3. Watch the volume mixer level bars during playback.
  4. Note exactly which combinations work and which don’t.
  5. Use the results to target the right layer below.

Fix 2: Inspect the driver model and service state

Open Device Manager and check whether your Realtek entry is the UAD or legacy HDA type — mismatched components are a classic silent-audio cause. Then open Services and verify the Realtek Audio Universal Service (or similarly named Realtek service) is running and set to Automatic. Check the System event log for errors from the audio driver around boot time; repeated crash entries confirm a driver-level fault rather than a settings problem. Microsoft’s Windows support hub explains how to read Event Viewer if you are unfamiliar.

  1. In Device Manager, note the exact Realtek device name and type.
  2. Open Services and find the Realtek audio service.
  3. Set it to Automatic and start it if stopped.
  4. Open Event Viewer, Windows Logs, System, and filter for audio errors.
  5. Record any repeating driver crash entries.

Fix 3: Clean the driver store and reinstall properly

A standard uninstall often leaves driver remnants that Windows reapplies. Open Device Manager, uninstall the Realtek device with “Attempt to remove the driver for this device” ticked, then reboot into Safe Mode and check for leftover Realtek entries under Sound controllers and System devices. Install the full driver package from your laptop maker — HP’s support site and Dell’s support portal both archive per-model audio drivers. Reboot normally and verify the service starts cleanly. Our guide to updating drivers safely on Windows 11 covers the general discipline.

  1. Uninstall the Realtek device with driver software removed.
  2. Reboot into Safe Mode and remove any leftover Realtek entries.
  3. Reboot normally and install the maker’s full audio package.
  4. Verify the Realtek service is running afterward.
  5. Test speakers and headphones before installing any audio extras.

Fix 4: Disable power management on the audio device

In Device Manager, find the Realtek audio device, open Properties, and look at the Power Management tab (present on most Intel-based audio controllers). Uncheck “Allow the computer to turn off this device to save power.” Then open Power Options, edit your active plan’s advanced settings, and under PCI Express, Link State Power Management, set it to Off or Moderate rather than Maximum power savings. This specifically targets the “works after reboot, dies later” pattern.

  1. Open the Realtek device Properties in Device Manager.
  2. On the Power Management tab, uncheck the power-saving option.
  3. Open Power Options, Change plan settings, advanced settings.
  4. Set PCI Express Link State Power Management to Off.
  5. Reboot and test for several hours of use.

Fix 5: Remove conflicting audio enhancement software

Third-party audio processing is a frequent saboteur. Uninstall Nahimic, Sonic Studio, Waves MaxxAudio, Dolby Access, or any “audio enhancer” you don’t actively use, then check Device Manager for leftover APO entries under “Audio inputs and outputs.” In Sound settings, disable all enhancements on the Realtek playback device. Reinstall only one enhancement suite — the one your laptop maker bundles — after base audio is confirmed working. If the issue is distortion rather than silence, see fixing crackling sound .

  1. Uninstall third-party audio enhancement apps in Settings, Apps.
  2. Check Device Manager for leftover audio filter entries.
  3. In Sound settings, disable enhancements on the playback device.
  4. Also disable exclusive mode during testing.
  5. Reinstall only the maker’s bundled suite after sound works.

Fix 6: Test with a clean boot and alternate OS

Use msconfig to perform a clean boot — disabling all non-Microsoft services and startup items — and test audio. If sound returns, re-enable services in halves until the culprit returns; this catches the background app that was crashing the audio stack. For the definitive hardware verdict, boot a Linux live USB and play a test sound. Sound in Linux with silence in Windows proves a Windows driver problem; silence in both proves hardware failure beyond reasonable doubt.

  1. Run msconfig and choose a clean boot (hide Microsoft services first).
  2. Test audio, then re-enable services in halves to find the culprit.
  3. Create a Linux live USB and boot from it.
  4. Play audio in Linux to test the hardware independently.
  5. Silence in both operating systems means hardware failure.

Fix 7: Repair the Windows audio stack itself

If the Realtek driver is healthy but Windows’ own audio engine is damaged, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated Command Prompt to repair system files. Then restart the audio services once more. As a last resort, use Settings, System, Recovery to reset Windows while keeping files — this rebuilds the entire audio stack. Before resetting, back up your drivers so you can restore working versions quickly afterward.

  1. Run sfc /scannow in an elevated Command Prompt.
  2. Run DISM restore-health to fix the component store.
  3. Restart the Windows Audio services.
  4. Back up current drivers before any reset.
  5. Use Reset this PC (keep files) only as the final step.

Closing

Realtek troubleshooting rewards patience: every test you run before reinstalling narrows the search and saves you from the reinstall-reboot-hope loop. Most faults resolve at the driver, service, or power-management layer. When the evidence — silence in Linux, no output across clean installs — points at the codec chip, stop troubleshooting software and get a hardware diagnosis. You will have earned it.

Frequently asked questions

How do I tell whether my Realtek audio problem is software or hardware?
Use a process of elimination. If Bluetooth audio or a USB headset works but the built-in speakers and jack don’t, the Realtek path is suspect but the system audio stack is fine. If a clean driver reinstall and a Linux live USB both stay silent, the codec chip or its circuit is likely dead. Software faults almost always respond to at least one driver fix.
Why does my Realtek audio work after reboot but die later?
This pattern points to a driver that loads correctly but crashes under use, or a power-management setting that puts the codec to sleep and never wakes it. Disable power saving on the audio device in Device Manager, update to the latest manufacturer driver, and check Event Viewer for driver crash entries around the time sound stops.
What is the Realtek Audio Universal Service and does it matter?
It is the background service that the modern UAD (Universal Audio Driver) package uses to manage the codec, replacing the older monolithic driver model. If this service is disabled or crashing, the Realtek device may appear in Device Manager but produce no sound. Set it to Automatic and make sure it is running after any driver reinstall.
Can I roll back to an older Realtek driver if a new one breaks sound?
Yes. In Device Manager, open the Realtek device properties, go to the Driver tab, and choose Roll Back Driver if the button is active. This restores the previous version. If the button is grayed out, uninstall the current driver with its software removed and manually install the older package from your laptop maker’s support archive.