Windows 10: Suche Standartwerte für Registryeintrag Audiosrv Depend on Service

Hallo liebe Community,ich habe gestern fälschlicherweise die Werte des Registryeintrags HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Sevices/Audiosrv/DependOnService geändert bzw. Alle bis auf den Eintrag RpcSs gelöscht.Die Pointe der Geschichte ist wohl, dass sich rausgestellt hat, dass die tolle Logitech Gaming Software, da eigentliche Problem verursacht hatte Der Service Windows-Audio startete nicht mehr und das Problem somit gar nicht mit den Werten in Audiosrv/DependOnService zusammenhing.Somit stellt sich die Frage, ob mir jemand die Standardwerte für diesen Eintrag geben kann ist das

:)

 

Local Service cannot start Audiosrv even with full control permission

I have a problem that audio doesn't play for any devices.

The problem seems to be that the Audiosrv is not running.

I gave a full control permission on Audiosrv to LOCAL SERVICE from regedit.

I tried to run Audiosrv with Local Service account, but it gives error 0x8007005.

I restarted like 4 times. I also ran chkdsk /f, but still cannot run.

I could ran Audiosrv by local system account but that didn't enable the audio.

 

Unable to turn on the service with error: "The dependency service or group failed to start" on Windows 10

Hi,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

I understand the inconvenience caused to you while connected to internet on Windows 10, we will help you with this issue.

Try the below steps and check if it helps.

Method 1: I suggest you to check with the dependency services of “Remote Access Connection Manager” and make sure that all the dependency services are started.

• 
  Click Start, type
  Services.msc in the Start Search box.
  
• 
  Scroll down the list of services, right-click
  Remote Access Connection Manager, click on Properties.
  
• 
  Click the Dependencies tab.
  
• 
  Make a note of the dependency services of Remote Access Connection Manager and make sure that these services are started and the startup type is set to
  Automatic.
  

To start a service, right-click the particular service and select Start
or Restart.

To set the startup type of a particular service,

• Right-click the service and select Properties.
• Under General tab, make sure the Startup type
  is set to Automatic.

Method 2: Perform a Winsock Reset

• Open the Windows Start Screen or
  Start Menu and type cmd in the search box.
• Right-click Command Prompt or
  cmd in the search results and select Run as Administrator.
• Type netsh winsock reset in the Command Prompt window and press
  Enter. Wait for Windows to finish resetting your Winsock configuration.
• Reboot your computer.

Hope it helps. Reply to the post with an updated status of this issue, we will be happy to help you further.

 

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.