Generally, such type of errors can be solved easily by executing SFC /SCANNOW command with an administrative Command Prompt. The reason behind this kind of error is many times due to the usage of third-party antivirus on the system. Usually, the antivirus program marks the file as a virus and puts them into the quarantined items list, and thus the associated services with these files get affected. Well, here is how you can rid of this issue, suggests a post at Answers. Further steps will involve registry manipulation and making mistakes while editing the registry may cause serious instabilities to the system. We recommend here creating a System Restore point first, before proceeding.
Windows could not start the Windows Audio service on Local Computer, Error 0x800706cc
If the Audio Service is not running, go to another computer that is running the same edition as on the issued system. Also, both system should have the same architecture like 32-bit on both machines. On another computer, press Windows Key + R combination, type put regedit in Run dialog box, and hit Enter to open the Registry Editor.
In the left pane of Registry Editor, navigate here:
Now you’d be able to see this dialog. Save the registry entry at a USB drive so that you can easily move it to the affected computer.
Moving on, now plug the same USB drive to the affected computer, and copy the registry to file to Desktop. Right-click over the file and select Merge. Click OK/Yes if any confirmation dialog appears.
Finally, reboot the machine and re-try to start the Windows Audio Service, you should now be able to do so without any problem. Read: Error 1083, Executable program that service is configured to run in does not implement the service.
Add Windows Audio service or Audiosrv to antivirus Safelist
To solve this issue, another way to fix it goes via the antivirus program you’re using. Go to the quarantined items list, and look if you can find Windows Audio Service related file and add it to the safe list. In this way, the original file is restored to the machine, which should fix your problem on the go. Hope this helps! If it does not, have a look at these posts too:
