How to fix Audio services not responding in windows 10: So you have been using windows 10 from quite a while but suddenly one day out of nowhere an error pops up saying “Audio services not responding” and audio is no longer working on your PC. Don’t worry this is totally fixable but let’s first understand why you are getting such an error.
This error occurs because the audio driver is outdated and couldn’t function properly or during Windows 10 update the audio driver gets damaged, in any case, let’s see how to fix this issue.
Audio services not responding in windows 10 Fix:
Method 1: Start Windows Audio services
- Press Windows key + R then type services.msc and hit enter to open Windows services list.
- Now locate the following services:
Windows Audio Windows Audio Endpoint Builder Plug and Play
- Make sure their Startup Type is set to Automatic and the services are Running, either way, restart all of them once again.
- If Startup Type is not Automatic then double click the services and inside property window set them to Automatic.
- Make sure the above services are checked in msconfig.exe
- Restart your computer to apply these changes.
Method 2: Start Windows Audio components
- Press Windows key + R then type services.msc
- Locate Windows Audio service and double click it to open properties.
- Select Dependencies tab and expand the components listed in “This service depends on the following system components.”
- Now make sure all the components listed above are Started and Running in the services.msc
- Finally restart the Windows Audio services and Reboot to apply changes.
Method 3: Uninstall Sound drivers
- Install CCleaner from here.
- Go to Registry window on the left, then scan for all the problems and let it fix them.
- Press Windows Key + R then type devmgmt.msc and hit enter to open Device Manager.
- Expand Sound, video and game controllers and click on the sound device then select Uninstall.
- Now confirm the uninstall by clicking OK.
- Finally, in the Device Manager window, go to Action and click on Scan for hardware changes.
- Restart to apply changes.
Method 4: Restore registry key from Antivirus
- Open your anti-virus and go to the virus vault.
- From system tray Right click on Norton Security and select “View Recent History.”
- Now select “Quarantine” from the Show drop-down.
- Inside Quarantine or virus vault search for the Audio device or services that are quarantined.
- Look for registry key: HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROL and if the registry key ends in:
- Restore them and Restart to apply changes.
- See if the issue “Audio services not responding” is resolved otherwise repeat steps 1 and 2.
Method 5: Modify Registry key
- Press Windows Key + R then type regedit and hit enter to open Registry editor.
- Now inside Registory editor navigate to the following key:
- Locate ServicDll and if the value is %SystemRoot%\System32\Audiosrv.dll, this is the cause of the problem.
- Replace the above value with this: %SystemRoot%\System32\AudioEndPointBuilder.dll
- Restart your PC to apply changes.
Method 6: Use Windows troubleshooter
- Open control panel and in the search box type “troubleshooting.“
- In the search results click on “Troubleshooting” and then select Hardware and Sound.
- Now in the next window click on “Playing Audio” inside Sound sub-category.
- Finally, click Advanced Options in the Playing Audio window and check “Apply repairs automatically” and click Next.
- Troubleshooter will automatically diagnose the issue and ask you if you want to apply the fix or not.
- Click Apply this fix and Reboot to apply changes.
Also, read How to fix Headphone not working in Windows 10:
If you have followed each and every step according to this guide then you just fixed the issue “Audio services not responding” but if you still have any queries regarding this post feel free to ask them in the comment section.
Latest posts by adityafarrad (see all)
- Fix Boot Configuration Data File is missing some required information - April 13, 2017
- Fix Your PC needs to be repaired error - March 28, 2017
- Fix Windows Store Error The Server Stumbled - March 27, 2017