- Are you trying to install a Windows Update or access the printer, but it returns an error message, Windows could not start the service on the local computer?
- This is common and can occur with any of the Windows services if the service dependencies are not running, due to corrupt system files or if the service does not have full permissions.
- Sometimes, even the temporary files stored in the system can be the reason behind the Windows service error.
Sometimes, when trying to open a Windows service, it fails to start with the error, Windows could not start the service on a local computer.
While this issue is common with the Windows Update service, it can also show up with other services, for example, the audio service.
Why couldn’t Windows start the service on a local computer?
Some of the reasons why you may come across the error, Windows could not start the service on a local computer:
- Service dependencies are not running – If the service dependencies are not working properly, you may come across this error,
- If the service is disabled – Chances are, that the service itself is disabled and so, you see the Windows could not start the service on a local computer error.
- When the service does not have full permissions – For some reason, the required service is set to default account with local permissions, and hence, it fails to start.
- Accumulated temporary files – Sometimes the temporary files tend to pile up and interrupt the functioning of the Windows services, and hence you see the error.
- Faulty system files – It could be possible that you may encounter the error, Windows could not start the service on a local computer due to corrupted system files.
What can I do if Windows could not start the Windows Update service on the local computer?
1. Run Windows Troubleshooter
- Press the Win + I keys together to launch the Windows Settings app. Click on System on the left side of the app and then click on Troubleshoot on the right.
- Next, click on Other trouble-shooters on the right.
- On the next screen, go to the right, look for the troubleshooter related to the service, for example, Windows Update and click on Run.
- The troubleshooter will now start looking for any issues, and if any are found, it will apply the fix automatically.
Once done, restart your PC and check if the service is running or if you still encounter the Windows service error.
But if the Windows Troubleshooter is not working for some reason, here we have a detailed post on how to fix the issue.
2. Give full permission to the Windows service
- Press the Win + R keys simultaneously to launch the Run console. Type services.msc in the search be and hit Enter to open the Service manager.
- In the Services window, go to the right and look for the service, for example, Print Spooler. Double-click on it.
- As the Properties window opens, select the Log On tab, select This account and click on Browse.
- Next, in the Select User dialog, click on Advanced.
- In the next window, click on Find Now. Now, from the Search results below, select Local Service and press OK.
- Let the password field remain blank. Press Apply and then OK to save the changes and exit.
Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.
Now, reboot your PC and check if you still see the error, Windows could not start the service on a local computer.
But if the local print spooler service is still not running, you may refer to the troubleshooting methods in our guide to fix the issue.
3. Re-configure the service
- To open the Run console, press the Win + R shortcut keys. Type cmd in the search bar and press the Ctrl + Shift + Enter keys to launch Command Prompt with admin rights.
- Run the below commands in the Command prompt window one after another and hit Enter after each one (replace the highlighted part with the relevant service):
net stop w32time
net start w32time
- Once the commands have been executed successfully, close the Command prompt, restart your PC and you should not see the error anymore.
4. Delete Temporary Files
- Open the Windows Settings app by pressing the Win + I keys together. Click on System on the left and then click on Storage on the right.
- Now, on the right, click on Temporary files.
- On the next screen, select the files you want to delete and press Remove files.
Once all the files are deleted, close the Windows Settings app and reboot your PC to check if you still come across the Windows service error.
5. Run SFC Scan and DISM Tool
- Press the Win + R keys together to open the Run dialog, type cmd, and press Ctrl + Shift + Enter keys to open Command Prompt with admin rights.
- Execute the below command in the Command prompt (admin) window and hit Enter:
- Windows will now start looking for the corrupted files and repair them automatically. The process takes a while, so wait patiently till you see a success message.
- Next, run the below command and hit Enter:
DISM /Online /Cleanup-Image /CheckHealth
- This process also takes a while, so wait patiently till the utility repairs or replaces the faulty files.
- Once done, exit the Command Prompt, and restart your PC.
At the same time, you must also run an antivirus scan or make sure that the Windows Defender Firewall is activated for added protection.
But, if you bump into a Windows service error like WLAN AutoConfig error 1068 instead, we have some effective workarounds for you to fix the issue.
For any other queries related to any specific Windows service not running, you can let us know in the comments box below.
Still having issues? Fix them with this tool:
If the advices above haven't solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.