How to Fix ‘The Dependency Service or Group Failed to Start’ in Windows 11

Attempting to connect to Wi-Fi, start a virtual private network (VPN), enable the mobile hotspot, or configure audio in Windows 11 only to be stopped by the alert: ‘The dependency service or group failed to start’ (accompanied by system error code 1068) indicates that a background Windows service cannot initialize because one of its prerequisite underlying services has crashed or is disabled. In Windows, services are arranged hierarchically; if a foundational driver or network component fails, all dependent subsystems fail cascadingly. Restoring these foundational services restores normal system functionality.

What Causes Error 1068 and Dependency Failures?

The Windows Service Control Manager (SCM) inspects dependency trees before starting any process. Failure occurs when:

  • Disabled Foundational Network Services: Services such as Network Store Interface Service (NSI), Remote Procedure Call (RPC), or DHCP Client being accidentally set to Disabled.
  • Corrupted Local Service Permissions: The built-in LOCAL SERVICE or NETWORK SERVICE accounts losing permissions to access administrative registry keys in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
  • Network Adapter Protocol Corruption: Corrupted TCP/IP stacks or Winsock catalog entries blocking the base transport layer.
  • Third-Party Antivirus Firewall Interception: Security suites disabling standard Windows firewall or networking daemons during uninstallation or updates.
  • Corrupted Windows Component Store: Missing or damaged system DLL files preventing service binaries from loading.

Step 1: Identify Dependencies in the Services Management Console

Identifying which specific service is failing tells you exactly which prerequisite service requires remediation.

  1. Press Windows + R, type services.msc, and press Enter.
  2. Locate the service that is failing to start (for instance, Network Connections, Windows Audio, or WLAN AutoConfig).
  3. Right-click the service and select Properties.
  4. Switch to the Dependencies tab.
  5. Inspect the box labelled ‘This service depends on the following system components’. Expand each entry.
  6. Note the names of all parent services listed (such as Network Store Interface Service, RPCSS, or Plug and Play).
  7. Close the properties window, locate those parent services in the main list, and ensure their Startup type is set to Automatic and their Status reads Running.

Step 2: Add Local Service and Network Service to the Administrators Group

Permission regressions in system accounts frequently prevent core network services from binding to hardware ports.

  1. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
  2. Add the Local Service account to the local Administrators security group:
    net localgroup Administrators /add localservice
  3. Add the Network Service account to the local Administrators security group:
    net localgroup Administrators /add networkservice
  4. Verify that the command prompt responds with: ‘The command completed successfully.’
  5. Restart your computer to allow the updated security tokens to take effect.

Step 3: Reset TCP/IP Stack and Winsock Catalog

If network-related services are failing to launch, resetting the underlying transport catalog clears corrupted socket definitions.

  1. Open Command Prompt as Administrator.
  2. Execute the following commands sequentially, pressing Enter after each:
    netsh winsock reset
    netsh int ip reset
    ipconfig /flushdns
  3. Do not restart yet; proceed to the system file check below.

Step 4: Run DISM and System File Checker (SFC) Scans

Replacing corrupted system servicing files restores pristine service binary manifests directly from the Windows Component Store.

  1. In the administrative Command Prompt window, execute the DISM health repair command:
    DISM /Online /Cleanup-Image /RestoreHealth
  2. Allow the progress bar to reach 100%. Once finished, run the System File Checker:
    sfc /scannow
  3. Verify that the output displays: ‘Windows Resource Protection found corrupt files and successfully repaired them.’
  4. Restart your PC.

Step 5: Verify Critical Network Services via Registry Editor

If services such as DHCP or NSI remain disabled due to malware or registry alterations, verify their startup values in the registry.

  1. Press Windows + R, type regedit, and press Enter.
  2. Navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp
  3. In the right pane, locate the Start DWORD value. Double-click it and ensure the value is set to 2 (Automatic).
  4. Navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Nsi
  5. Ensure its Start value is also set to 2.
  6. Close the Registry Editor and reboot Windows 11.

Restoring dependency service startup states and repairing system permissions eliminates error 1068, allowing all Windows services to initialise smoothly.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.