1. Home
  2. Windows Tips
  3. Audio renderer error

(FIXED) Audio Renderer Error: Please Restart Your Computer

Computer problems are bound to happen every now and then, so you have to be prepared to take action in any scenario. For instance, if there’s no sound coming from your Windows 10 PC, it could be caused by various issues, such as the audio renderer error. But there’s no need to panic since you can troubleshoot this problem by following the instructions below.

Audio Renderer Error

Audio Renderer Error: Please restart your computer!

Audio renderer error, please restart your computer is an error message that appears on the screen when your computer fails to play audio tracks. It can occur anywhere, whether you’re trying to watch a video on YouTube or a movie in your media player.

The behavior is strange. Sometimes, audio gets played without any issues until the error suddenly occurs and disables all sounds coming from your computer. It kindly asks you to restart your computer, which seems to solve the issue.

However, PC reboot is just a temporary workaround since the error pops up again eventually. At that point, you are forced to enter a computer restart loop just to keep the sound going. It’s easy to see why it’s so frustrating to users, especially when the root of the problem isn’t clear.

We have tested this problem, chatted with various users, and gathered a list of possible solutions that solves the audio renderer error on most PCs running Windows 10.

How to fix audio renderer error on Windows 10

The audio rendering error can be caused by a problem with your web browser or computer settings. It’s important to arm yourself with patience because it might take a while until you exhaust all options.

Before starting to troubleshoot this annoying issue, it’s wise to set up a system restore point. It allows you to revert Windows 10 to a stable state in case you encounter more problems along the way.

Before you troubleshoot: is this a YouTube/browser problem or a Windows-wide audio problem?

Not all audio renderer errors are the same. Spending two minutes on this quick diagnosis will point you to the right fix immediately and save you from working through steps that don’t apply to your situation.

Run through these five checks in order:

  1. Play a local audio or video file. Open a media file on your PC — an MP3 in Windows Media Player, a video in Movies & TV, or any local file. If it plays fine, your system audio is healthy and the problem is browser- or site-specific. If it also fails, you have a system-wide audio problem.
  2. Test another website. Try playing audio on a site other than YouTube (SoundCloud, Spotify Web, a news site with video). If other sites work but YouTube fails, the issue is YouTube- or extension-specific.
  3. Open YouTube in an Incognito or Private window. In Chrome or Edge press Ctrl + Shift + N; in Firefox press Ctrl + Shift + P. Extensions are disabled in these modes. If audio works here, a browser extension is the culprit.
  4. Try a second browser. If the error only happens in one browser, that browser’s cache, settings, or an extension is responsible — not Windows.
  5. Swap or reseat your output device. Unplug and replug headphones, a USB audio adapter, or an HDMI cable. If the error clears immediately, you have a hardware endpoint issue.

Use the table below to route yourself to the right set of fixes:

What you observe Likely cause Start here
Only YouTube fails; local audio and other sites work Ad blocker, browser extension, or browser cache Steps 1 and 2 (cache, extensions)
Only one browser fails; YouTube works in another Browser-specific cache, extension, or outdated browser Steps 1, 2, and 14 (clear cache, disable extensions, update browser)
All apps fail — browser, media player, system sounds Windows Audio service, default device, or audio driver Steps 3, 5, 8, 9, and 10 (troubleshooter, audio service, default device, driver)
Only one output device fails (e.g., HDMI monitor, USB headset) Hardware endpoint not recognized or conflicting app Steps 8 and 12 (default device, check cable/connection)
Error starts after launching a specific app, then spreads App-level audio conflict (audio software, DAW, comms app) Step 13 (disable audio mixing/conflicting software)

Once you know your scenario, jump straight to the relevant fix below rather than working through every step in order.

1. Clear browsing cache

Many users report getting the audio renderer error on YouTube. It could be caused by a browser problem, such as saved cache and cookies. A simple way to fix it is by hard-refreshing your web browser. To make this happen, just select the YouTube tab and press Ctrl + Shift + R. Then, check if you still get the error.

It’s only a temporary fix, though, since you still have to clear browser cache the traditional way.

How to clear Chrome cache:

  1. Launch Chrome and open the More menu on the top-right corner
  2. Go to SettingsGoogle Chrome shows how to access the Settings menu
  3. Jump to Privacy and security on the left side
  4. Click Clear browsing data. Alternatively, you can enter the chrome://settings/clearBrowserData addressGoogle Chrome shows how to access the Clear browsing data option
  5. Remain in the Basic section
  6. Set Time range to All time
  7. Make sure the following options are enabled:
    • Browsing history
    • Cookies and other site data
    • Cached images and files
  8. Click Clear dataGoogle Chrome shows how to clear browsing data
  9. Restart Chrome and try to watch YouTube now

How to clear Firefox cache:

  1. Open Firefox and click the ≡ hamburger button
  2. Select OptionsMozilla Firefox shows how to access the Options menu
  3. Jump to Privacy & Security and click Clear DataMozilla Firefox shows how to access the Clear Data option
  4. Check that the next settings are selected:
    • Cookies and Site Data
    • Cached Web Content
  5. Click ClearMozilla Firefox shows how to clear data
  6. Relaunch Firefox and check for audio errors

How to clear Microsoft Edge cache:

  1. Start Microsoft Edge
  2. Click the More button on the top-right cornerMicrosoft Edge shows how to access the Settings menu
  3. Select Settings
  4. Jump to Privacy, search, and services. Else, you can use the edge://settings/privacy address
  5. At Clear browsing data now, click Choose what to clearMicrosoft Edge shows how to access the Clear Browsing Data option
  6. Set Time range to All time
  7. Check the boxes of the following options:
    • Browsing history
    • Download history
    • Cookies and other site data
    • Cached images and files
  8. Click Clear nowMicrosoft Edge shows how to clear browsing data
  9. Restart Edge and try to enjoy YouTube without audio issues

2. Disable ad blockers and browser extensions on YouTube

If your system sounds and local media files play back fine but the audio renderer error only appears on YouTube or in one specific browser, the culprit is very likely a browser extension rather than a Windows-level problem or a YouTube service error. Ad blockers, volume boosters, audio enhancers, privacy extensions, and even antivirus web shields can all interfere with how YouTube handles audio. Test this path before diving into deeper Windows fixes.

Quick decision point: If local audio works but YouTube fails, start here before trying driver or service fixes.

Here is how to diagnose and isolate the conflict:

  1. Open YouTube in an Incognito (Chrome/Edge: Ctrl + Shift + N) or Private (Firefox: Ctrl + Shift + P) window. Extensions are disabled by default in these modes. If audio works here, an extension is causing the problem.
  2. Return to your normal browser window and temporarily disable all extensions — pay particular attention to ad blockers (uBlock Origin, AdBlock Plus, etc.), volume boosters, audio enhancers, privacy tools, and any antivirus browser shield.
  3. If the error goes away after disabling extensions, whitelist youtube.com in your ad blocker as a permanent fix, or keep specific extensions disabled while using YouTube.
  4. Restart the browser completely (close all windows, then reopen).
  5. Re-enable your extensions one by one, reloading YouTube after each one, until the audio renderer error reappears. The last extension you enabled is the conflict.
  6. Once identified, either remove that extension, whitelist YouTube within it, or look for an updated version that resolves the conflict.

3. Run the audio troubleshooter

Windows 10 comes with an integrated troubleshooter that fixes common audio issues. It’s worth a shot if you got tired of dealing with the audio renderer error. Similar audio problems can also affect other applications, such as when you need a Spotify audio error fix for playback issues.

  1. Right-click the Windows 10 Start button and go to SettingsWindows 10 shows how to access settings from the Start right-click menu
  2. Select Update & SecurityWindows 10 shows how to access the Update and Security settings
  3. Go to Troubleshoot on the left side
  4. Click Additional troubleshootersWindows 10 shows how to access additional troubleshooters
  5. Select Playing Audio and click Run the troubleshooterWindows 10 shows how to run the audio troubleshooter
  6. Follow the on-screen instructions
  7. Check for audio errors

4. Enable the sound device

If you have connected multiple audio device into your computer, you might have unknowingly messed up the sound device settings and disabled the primary audio adapter. Here’s how to re-enable it:

  1. Click the Start button, type Control Panel, and open this app
  2. Go to the Sound sectionWindows shows how to access Sound settings from Control Panel
  3. Switch to the Playback tab
  4. Select your audio device from the list
  5. Click PropertiesWindows 10 shows how to access sound playback properties
  6. In the General tab, set Device usage to Use this device (enable)Windows 10 shows how to enable an audio device
  7. Click Apply and exit
  8. Check for audio issues now

5. Restart the Windows Audio service

All sounds coming out of your computer are operated by a background service. If that service isn’t currently running, gets interrupted often, or doesn’t automatically start when Windows boots, then you should expect issues such as the audio renderer error.

The most effective fix is to perform a true restart of the Windows Audio service — not just start it if stopped. You should also restart the Windows Audio Endpoint Builder service, because failures in audio endpoint handling can trigger the exact same symptom. Here are both methods:

Method 1: Using the Services app

  1. Press the Windows key, type Services, and open this app
  2. Find and right-click Windows Audio
  3. Go to Propertieshow to access Windows Audio service properties
  4. Remain in the General tab
  5. Set Startup type to Automatic
  6. If Service status says Running, click Stop, wait a moment, then click Start to perform a full restart. If it says Stopped, simply click Start.
  7. Click Apply and exitWindows 10 shows how to edit Audio service properties
  8. Back in the Services list, find Windows Audio Endpoint Builder, right-click it, and select Restart (or Stop then Start if Restart is greyed out)
  9. Check for audio issues

Method 2: Using Task Manager

  1. Press Ctrl + Shift + Esc to open Task Manager
  2. Click the Services tab
  3. Find Audiosrv (Windows Audio) in the list, right-click it, and select Restart
  4. Find AudioEndpointBuilder (Windows Audio Endpoint Builder), right-click it, and select Restart
  5. Check for audio issues

6. Synchronize the audio frequency (ASIO drivers)

Users with ASIO4ALL drivers have reported conflicts with the system audio settings. More specifically, if the sample rate is not set at the same value in both parts, the computer starts experiencing sound problems. Here’s how to easily solve this issue:

  1. Click the Start button, type Control Panel, and press Enter
  2. Select the Sound areaWindows shows how to access Sound settings from Control Panel
  3. In the Playback tab, select your audio device and click PropertiesWindows 10 shows how to access sound playback properties
  4. Switch to the Advanced tab
  5. Write down the sample rate specified at Default FormatWindows 10 shows advanced audio device properties
  6. Exit this area
  7. Open the ASIO utility
  8. Switch to the Audio tab
  9. Set Sample rate to the same value as in WindowsThe ASIO utility shows how to set the sample rate
  10. Restart your PC and inspect results

7. Run audio tests (HP laptops)

HP users can turn to an audio diagnostics tool called HP PC Hardware Diagnostics (UEFI). Here’s how to use it:

  1. Restart your HP laptop
  2. During reboot, quickly press the key that grants you access to HP PC Hardware Diagnostics (UEFI)HP PC Hardware Diagnostics (UEFI) shows component tests
  3. Go to the Audio section
  4. Click Run once to start evaluating your audio devices
  5. Select Speaker and follow the on-screen instructions
  6. Complete the test and boot Windows
  7. Check for audio issues

You can also download HP Audio Check from the official website and use it to run additional tests.

8. Set the default audio device

Windows sometimes has trouble identifying the default sound device. And this is also why it could show the audio renderer error, whether you get it on YouTube or anywhere else. To fix this annoying problem, you just have to set your favorite audio device as default again. If you would rather assign audio output per app instead of changing it system-wide, Windows 10 can do that too. Here’s how:

  1. Press the Win key, type Control Panel, and open this app
  2. Click SoundWindows shows how to access Sound settings from Control Panel
  3. Choose your audio device from the Playback tab
  4. Click Set DefaultWindows 10 shows how to set a default audio device
  5. If the Set Default button is greyed out, select any other device to set it as default, then go back to your first option
  6. Click Apply and exit this area
  7. Check for audio issues

9. Reinstall the audio adapter

Your audio adapter might not be properly connected to your computer. However, you can effortlessly reinstall it without harming your PC in the process.

Important note: For driver-level fixes like this one, you need to work under Sound, video and game controllers in Device Manager — not Audio inputs and outputs. The “Audio inputs and outputs” category lists playback endpoints such as Speakers or Headphones, but the actual audio driver/controller (for example, Realtek(R) Audio, Intel Smart Sound Technology, Conexant, AMD High Definition Audio, NVIDIA High Definition Audio, or a USB audio device) lives under “Sound, video and game controllers.” Reinstalling, updating, or rolling back the wrong entry will not fix the audio renderer error.

Here’s what you need to do:

  1. Right-click the Start button and select Device ManagerWindows 10 shows how to access Device Manager from the Start right-click menu
  2. Expand the Sound, video and game controllers group
  3. Identify your main audio controller (such as Realtek(R) Audio, Intel Smart Sound Technology, Conexant, AMD High Definition Audio, NVIDIA High Definition Audio, or your USB audio device), right-click it, and select Uninstall deviceDevice Manager shows how to uninstall an audio device
  4. Select any entry from the list
  5. Open the Action menu and click Scan for hardware changesDevice Manager shows how to scan for hardware changes
  6. Restart your computer. Windows will auto-reinstall the missing audio driver
  7. Check for sound problems

10. Update the audio driver

Even if your sound adapter is correctly installed, perhaps it’s equipped with an obsolete driver that’s no longer supported by Windows 10. It would certainly explain the audio renderer error. However, you can easily update the audio driver.

Remember: Use Audio inputs and outputs only to troubleshoot playback endpoints (like Speakers or Headphones). To update the actual audio driver, you must expand Sound, video and game controllers and target your audio controller there — entries such as Realtek(R) Audio, Intel Smart Sound Technology, Conexant, AMD High Definition Audio, NVIDIA High Definition Audio, or a USB audio device.

  1. Click the Start button, type Device Manager, and press Enter
  2. Expand the Sound, video and game controllers category
  3. Right-click your audio controller (e.g., Realtek(R) Audio, Intel Smart Sound Technology, or similar) and select Update driverDevice Manager shows how to update the audio driver
  4. Click Search automatically for updated driver softwareDevice Manager shows how to search automatically for audio drivers
  5. If you see the The best drivers for your device are already installed message, click Search for updated drivers on Windows UpdateDevice Manager shows that the best audio drivers are already installed
  6. Reboot your PC and check for additional audio issues

If Windows Update does not surface a newer driver, work through the following steps in order rather than turning to a generic driver-updater app — those tools can install the wrong package on laptops with OEM-customized audio stacks, potentially making the problem worse.

  1. Check Windows Update Optional updates. Open Settings > Windows Update > Advanced options > Optional updates > Driver updates and install any audio-related items listed there. These are Microsoft-vetted packages for your specific hardware.
  2. Download the driver directly from your PC maker’s support page. If no optional driver update appears, go to your manufacturer’s support site (Dell, HP, Lenovo, ASUS, Acer, MSI, and so on) and look up your exact model using the model number, SKU, or service tag printed on the underside of your laptop or in Settings > System > About. Download and install the OEM audio package for your hardware — typically a Realtek, Conexant, Intel Smart Sound Technology (SST), AMD, NVIDIA, or USB audio package.
  3. Install supporting components first if the release notes mention it. Some OEM audio packages — particularly Intel Smart Sound Technology drivers — require the matching chipset or Intel SST component to be installed before the audio package itself. If the vendor’s release notes mention audio stability fixes alongside chipset or SST components, install the chipset/SST package first, then the audio driver, and reboot between each step.
  4. Consider a BIOS or firmware update only if the changelog specifically mentions audio. If the manufacturer’s firmware release notes explicitly reference audio stability, HDMI audio, docking station audio, or USB audio fixes, a BIOS update may be warranted. Follow your OEM’s instructions exactly — never interrupt a firmware update — and treat this as a last resort rather than a routine step.

11. Roll back the audio driver

If you have recently updated your sound driver, perhaps you installed an incompatible version that’s throwing you the audio renderer error. To fix it, you should roll back to the previous driver version.

Remember: Perform this rollback under Sound, video and game controllers in Device Manager, targeting your actual audio controller such as Realtek(R) Audio, Intel Smart Sound Technology, or similar — not an entry under “Audio inputs and outputs.” Rolling back the wrong device will have no effect.

Here’s how:

  1. Head over to Device Manager
  2. Expand Sound, video and game controllers, right-click your audio controller, and go to PropertiesDevice Manager shows how to access audio properties
  3. Select the Driver tab
  4. Click Roll Back Driver and follow the given instructions
  5. If the button is greyed out, it means that your operating system doesn’t have the previous driver version, so you can skip this solutionThe Roll back driver option is disabled for an audio device in Windows
  6. Restart your computer and inspect results

12. Check the audio cable

Hardware connection issues are a surprisingly common and overlooked cause of the audio renderer error — and the fix can be instant. Before reaching for a reboot, try physically reseating your audio devices. Unplugging and reconnecting an audio device can immediately reset a stuck audio endpoint in Windows, clearing the error without any deeper troubleshooting.

Here is what to check and how to do it:

  1. Headphones or speakers (3.5mm jack): Unplug the audio cable completely from the jack, wait a few seconds, then firmly plug it back in. If your PC has multiple audio jacks, try a different port.
  2. USB audio devices: Disconnect the USB cable or USB audio adapter, wait a few seconds, then reconnect it. Windows will re-detect the device and reinitialize the audio endpoint.
  3. HDMI or DisplayPort monitor/TV audio: If you are using a monitor or TV as your audio output, unplug the HDMI or DisplayPort cable from the PC, wait a few seconds, and reconnect it. Alternatively, open Control Panel > Sound and temporarily switch your default playback device to your laptop speakers or another device, then switch back to the monitor — this can jolt the endpoint back to life without unplugging anything.
  4. Docking stations: If you use a laptop dock, disconnect it from the laptop completely, wait a few seconds, then reconnect it. Audio endpoints associated with dock-connected devices often get stuck when the dock is hot-plugged.
  5. After reseating any connection, check your Control Panel > Sound > Playback tab to confirm the correct device is set as default, then test audio playback.

Also make sure you haven’t accidentally swapped the audio and microphone jacks, and remove any external playback devices you are not currently using to reduce the chance of endpoint conflicts.

13. Disable audio mixing software

The problem here is not limited to traditional “audio mixing” tools. Any application or utility that reroutes, enhances, or holds exclusive access to your audio device can trigger the audio renderer error. This is a wider category of software than most people realize, and identifying the conflicting app is often the fastest path to a permanent fix.

Common culprits include dedicated audio routing and enhancement tools such as Voicemeeter, Nahimic, Sonic Studio, Dolby Atmos, DTS Sound Unbound, Waves MaxxAudio, and SteelSeries Sonar. Recording and streaming software such as OBS Studio and DAWs (digital audio workstations like Ableton, FL Studio, or Audacity) can also hold the audio device and block other apps.

Communications apps — Skype, Microsoft Teams, and Zoom — are well-known for taking exclusive control of audio endpoints. Even everyday media players like Spotify, iTunes, VLC, and Windows Media Player can hold a device open in the background and prevent other apps from accessing it.

Key indicator: If the audio renderer error starts appearing immediately after you launch one particular app and then affects YouTube or other apps too, that almost always points to an app-level conflict — not a browser cache problem or a driver issue.

Follow this troubleshooting flow to isolate and resolve the conflict:

  1. Check the system tray. Look at the icons in the bottom-right corner of your taskbar (click the up arrow to expand hidden icons). Fully quit any audio enhancement utilities, virtual audio cable tools, or communications apps you find there — right-click each icon and choose Exit or Quit, not just close.
  2. End remaining processes in Task Manager. Press Ctrl + Shift + Esc to open Task Manager. Under the Processes tab, look for and end the tasks of any apps listed above — Voicemeeter, Nahimic, OBS, Zoom, Teams, Skype, Spotify, iTunes, VLC, and any DAW or audio enhancement tool. Simply minimizing or closing their windows is not enough; the process must be fully terminated.
  3. Test playback. After quitting the suspected apps, try playing audio on YouTube and from a local media file. If audio works now, you have identified the conflicting software category.
  4. Re-launch apps one at a time. Open each previously closed app individually and test audio after each one. The app that breaks audio when launched is the conflict.
  5. Temporarily uninstall if needed. If you cannot isolate the conflict through quitting alone — for example, if an enhancement utility like Nahimic or Sonic Studio runs as a background service — temporarily uninstall it through Settings > Apps (Windows 10) or Settings > Apps > Installed apps (Windows 11), then test audio again.
  6. Use a Clean Boot to isolate stubborn conflicts. If you still cannot pinpoint the culprit, perform a Clean Boot of Windows, which starts the OS with only Microsoft services and drivers running. Press Win + R, type msconfig, and press Enter. Go to the Services tab, check Hide all Microsoft services, then click Disable all. Switch to the Startup tab and click Open Task Manager to disable all startup items. Restart and test audio. If audio works on a clean boot, re-enable services and startup items in small groups until the conflict reappears.
  7. Check exclusive mode settings. Some audio software enables exclusive mode on your audio device, which locks out all other apps. In Control Panel > Sound > Playback, right-click your default device, select Properties, go to the Advanced tab, and make sure Allow applications to take exclusive control of this device is unchecked if you continue to experience conflicts.

14. Update your web browser

If you’re getting the audio renderer error message on YouTube when trying to enjoy a video, it’s a good idea to update your web browser to the latest version. This section covers all three browsers the article discusses — Chrome, Microsoft Edge, and Firefox. Note that this article already provides cache-clearing instructions for all three browsers above, but the update steps are equally important and specific to each browser.

How to update Google Chrome:

  1. Open the More menu (three dots) on the top-right corner
  2. Go to Help and click About Google Chrome. Alternatively, visit the chrome://settings/help address
  3. Chrome will automatically check for and download any available update
  4. Once the update installs, click Relaunch to restart Chrome and apply the update, then test YouTube audio

How to update Microsoft Edge:

  1. Open the More menu (three dots) on the top-right corner
  2. Go to Help and feedback and click About Microsoft Edge. Alternatively, visit the edge://settings/help address
  3. Edge will automatically check for and download any available update
  4. Once the update installs, click Restart to relaunch Edge and apply the update, then test YouTube audio

How to update Mozilla Firefox:

  1. Open the ≡ hamburger menu on the top-right corner
  2. Go to Help and click About Firefox
  3. Firefox will automatically check for and download any available update
  4. Once the update installs, click Restart to update Firefox to relaunch and apply the update, then test YouTube audio

Still seeing the error in just one browser after updating? If the audio renderer error persists in a single browser even after updating it, the next things to check are: creating a fresh browser profile to rule out a corrupted profile, disabling all extensions to rule out an extension conflict, and toggling hardware acceleration off (found in the browser’s advanced settings) to rule out a GPU-related audio rendering issue.

How to fix audio renderer error on Windows 11

The core fixes above apply equally to Windows 11 — the underlying audio architecture, Device Manager, Services, and the audio driver model are the same on both operating systems. However, the menu paths in Settings have changed, so Windows 11 users will need to translate a few steps. Here is where to find the most important tools in Windows 11, along with any differences worth noting.

Note: Steps involving Device Manager, the Services app, Control Panel Sound settings, Task Manager, and msconfig are identical on Windows 10 and Windows 11. Only the Settings app paths differ.

Audio troubleshooter on Windows 11

Microsoft moved the troubleshooter location in Windows 11. Instead of going through Update & Security, use this path:

  1. Open Settings (press Win + I)
  2. Go to System > Troubleshoot
  3. Click Other troubleshooters
  4. Find Playing Audio and click Run
  5. Follow the on-screen instructions and check for audio errors

Selecting your default output device on Windows 11

Windows 11 changed how you select the default output device compared to Windows 10. There are two quick ways to do it without opening Control Panel:

  1. Open Settings (press Win + I) and go to System > Sound
  2. Under Output, select the device tile or radio button for the audio output you want to use as your default
  3. Alternatively, click the speaker icon in the taskbar to open Quick Settings, then click the audio output selector (the arrow or device name next to the volume slider) and switch to your preferred device from the list that appears
  4. If you need the old sound panel, type Sound in the Start search bar and select Change system sounds, or run mmsys.cpl from the Run dialog (Win + R) — this opens the same Playback tab interface shown in the steps above

Practical tip: If audio is stuck or not routing correctly, try toggling your output device — switch from your headphones, HDMI output, or USB audio device to a different output (such as your laptop’s built-in speakers), wait a moment, then switch back. This can reset a stuck audio endpoint without requiring a full reboot.

Checking audio output and volume on Windows 11

Windows 11 also surfaces per-app volume controls more prominently:

  1. Go to Settings > System > Sound
  2. Scroll down to Advanced and click Volume mixer to see and adjust volume levels per application
  3. If one app is muted or set to a different output device here, that can cause it to appear broken while everything else works fine

Driver and service steps on Windows 11

Device Manager and the Services app work identically on Windows 11. To open Device Manager, right-click the Start button and select Device Manager — the same as on Windows 10. Expand Sound, video and game controllers to find your audio controller and apply driver updates, rollbacks, or reinstalls exactly as described in steps 9, 10, and 11 above.

To uninstall third-party audio software on Windows 11, go to Settings > Apps > Installed apps rather than Settings > Apps > Apps & features as on Windows 10. The process is otherwise the same. If the audio renderer error persists after trying all of the steps above, consider checking the Microsoft Community forums for additional guidance specific to your hardware configuration.