You might think the workaround here would be fairly easy and as simple as turning on the Windows Audio service. That’s correct, however, if you try simply starting the Windows Audio service through the Windows Services window, you will stumble upon the “Windows could not start the Windows Audio service on Local Computer” error message. This happens when the Audio service does not have enough permissions to run on your machine which can be really weird. Since this is a system service, it requires proper permissions to be able to work properly. Therefore, in case the permissions are denied, the service won’t be able to start and as a result, you will be left with no sound in your system. With that said, there are actually really easy workarounds to the error message in question that you can implement to get the audio service back up and running. The essence of all these solutions is to simply provide the service with enough permissions so that it can start and stay running without any problems. So, without further ado, let us get right into it.
Change Windows Audio Service Log On Settings
As it turns out, one way of circumventing the error message is to change the log on settings of the service. These settings define which user account is used by the service to start as. In essence, it reflects how the service is running on your system. Here, we will be configuring the service to log on as the local system account which should help in resolving the issue for you. To do this, follow the instructions given down below:
Change Audio Registry Permissions
If changing the log on account for the service does not fix the issue for you, it is possible that your user account does not have the proper permissions for the audio registry. In such a scenario, you will have to change the permissions of the audio registry by giving your user account full control permissions. Making changes to the Windows Registry is normally not recommended because incorrect modifications can cause various system problems. Therefore, make sure to follow the given instructions carefully and you should be good to go. Let us get started.
Fix: Windows Resource Protection Could not Start the Repair ServiceFix: Windows could not start the Background Intelligent Transfer Service (BITS)Fix: Windows Setup could not configure Windows to run on this computer hardwareFix: Windows could not Update the Computer’s Boot Configuration
