Windows 7/8/10: How To Fix Group Dependency Failed To Start Error
How to resolve “The dependency service or group failed to start”.
A pretty well-known Windows issue, pretty much because of the sheer number of people who were and still continue to be affected by it, is one where the affected user’s access to the internet becomes entirely non-existent and a message that reads “The dependency service or group failed to start” is displayed in their Network & Sharing Center. This issue first affected Windows 7 users but, since then, has also been found on other versions of the Windows Operating System.
Users affected by this issue become incapable of connecting to the internet on any and all networks regardless of whether they try to connect wirelessly or via an Ethernet cable. Any attempts to troubleshoot this problem from the Network & Sharing Center result in failure and yet another message which reads “The Diagnostic Policy Service is not running”.
The Diagnostic Policy Service is a Windows service that should start running as soon as your computer boots up. However, when affected users try to start the Diagnostic Policy Service by launching services.msc, they receive an error message stating “Windows could not start the Diagnostic Policy Service on Local Computer; Error 5: Access is denied”. This error message, ladies and gentlemen, is the true source of this entire problem. If you are suffering from this problem, you are in this predicament because localservice and networkservice have, for some reason, been removed from your administrator group and your user account no longer has the access level necessary to start the Diagnostic Policy Service upon startup.
This tutorial will apply for computers, laptops, desktops,and tablets running the Windows 10, Windows 8/8.1, Windows 7 operating systems.Works for all major computer manufactures (Dell, HP, Acer, Asus, Toshiba, Lenovo, Samsung).
how to repair windows 7
