We have already seen many issues regarding various services, when dependency service do not coordinate, the actual service failed to start as a consequence of this. Recently, we came around the similar problem for Security Center service. If you can’t start Security Center service, checkout this fix. After applying the same fix, one of my reader asked that he now gets different error and thus can’t start the service. This is what he received now:
Windows could not start the Security Center service on Local Computer.
Error 1075: The dependency service does not exist or has been marked for deletion.
This error is not only bound to Security Center service, but you can get this with other services too, which have dependency on some other services. In such a case, when try to check Dependencies tab for the service, you’ll find that both the boxes (This service depends on the following system components and vice versa) are empty.
After doing a bit research on this error, we found that this hiccup can be tackled easily from registry manipulation. Also, you may want to give a try by running SFC /SCANNOW in administrative Command Prompt and see if it helps. Even if this not helps and you’re still getting Error 1075, no matter whichever the service is, try this general method by substituting your service name in successive steps:
FIX : The Dependency Service Does Not Exist Or Has Been Marked For Deletion In Windows 10/8
Registry Disclaimer: The further steps will involve registry manipulation. Making mistakes while manipulating registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point first.
1. Press + R and put regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here). Click OK.
2. In the left pane of Registry Editor, navigate here:
Here you need to identify the technical service name for which you’re facing issue and substitute into above mentioned location. To identify the service name, run services.msc command. In the Services window, double click the issue creating service. On the General tab, notice the Service name there, this is what you need to place in the registry location mentioned above. Thus, for example; if the Service name is wscsvc, registry location becomes HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc.
3. Once arrived the correct registry location for the service with which you’re facing problem, highlight the Service name key and export it as backup. Now come to its right pane, you’ll find that there is multi-valued registry string named DependOnService. Simply right click on it and select Delete. Select Yes here:
Finally after deleting the string, you can close Registry Editor. Reboot the machine, and retry to start the service. This time the service will start as usual, without any error.
That’s it! Go here if you’re facing Error 1079 while starting services in Windows 8.1.