Windows 10: “the dependency service or group failed to start

Hello Microsoft , I dont know but my internt no working so when i checked about that so i found That This is Error 1068“the dependency service or group failed to start" so When i see the solutiion of this error on support microsoft so at that place there is a file for "automated fix" but i cant download that can you please give the link of that File ASAp

:)

 

Dependency service or group failed to start


Hello, last night I upgraded to win 10 home from win 7. However, I noticed that I was unable to use the Start Menu Search function or open the start menu and found out I was only connected to my Local Area Connection (Realtek PCIe GBE Family Controller), and my connection/internet is limited. There were no other connections available or found!
So I opened up the Network and Sharing Center only to find that where my network should show it says "Unknown - The dependency service or group failed to start."
In conclusion, I cannot connect to any private networks - possibly because of this dependency service error. Any help or fix would be appreciated!

Thanks,
Nick

 

Windows 10 Enterprise Edition Update from RS3 to RS4, service is not started (error 1068 the dependency service or group failed to start)

We have identified an issue upgrading Windows 10 Enterprise Edition from RS3 (1709) to RS4 (1803). After the update our Service is not started even though it is set to start Automatically. We know the application is intact because it can
be started manually through the Services UI and performs as expected.



Supporting Data:

1. The System Event Log shows the sender is not Automatically started because it is dependent on LanmanWorkstation (Error 1068: the dependency service or group failed to start).
2. The Event Logs do not show any LanmanWorkstation events and when queried the LanmanWorkstation service is running.
   1. RGS Service Dependencies are LanmanWorkstation, TermService, Winmgmt, EventLog
   2. Dependency Map
      1. Remote Procedure Call (RPC) : rpcSs(Automatic),
         
         1. Depends on: DCOM Service Process Launcher(automatic, no dependencies)
         2. Depends on: RPC Endpoint Mapper(automatic, no dependencies)
      2. Workstation: LanmanWorkstation(Automatic)
         1. Depends on: Network Store Interface Service who depends on NSI Proxy Service Driver
         2. Depends on: Network Store Interface Service who depends on Remote Procedure Call
         3. Depends on: SMB 2.0 MiniRedirector
         4. Dependent on this service: Remote Desktop Configuration(Manual)
         5. Dependent on this service: Our Service(Automatic)
      3. Remote Desktop Services: TermService(Manual)
         1. Depends on: Remote Procedure Call
         2. Dependent on this service: Our Service(Automatic)

My assumption is that LanmanWorkstation service is delayed starting (could be in recovery restart mode), but after it starts, the Update Service doesn't go back and start its dependent services. The only
other service that is dependent on LanmanWorkstation is the Remote Desktop Configuration, but it’s a Manual start so we don’t see a similar failure.

I would appreciate any suggestions or ideas.

 

How to easily fix Dependency service or group failed to start.

I know that many of you are facing this error. All the methods to fix this error won't work. You need to enable ' Windows Event Log ' and 'Windows Event Collector ' services.

Fix dependency service or group failed to start. . This method has worked for over thousands of people.