Windows Event ID 7022 – Service Control Manager: Service Hung on Starting

Start by identifying the specific service causing the timeout and gathering detailed information from Event Viewer.

1. Open Event Viewer by pressing Win + R, typing eventvwr.msc, and pressing Enter
2. Navigate to Windows Logs → System
3. Filter for Event ID 7022 by right-clicking System → Filter Current Log → enter 7022 in Event IDs field
4. Double-click the most recent Event ID 7022 entry to view details
5. Note the service name mentioned in the event description
6. Use PowerShell to get additional service information:

   Get-Service -Name "ServiceName" | Format-List *
   Get-WinEvent -FilterHashtable @{LogName='System'; Id=7022} -MaxEvents 5 | Format-Table TimeCreated, Message -Wrap

7. Check for related events around the same timestamp that might indicate root causes

Examine the service configuration and dependencies to identify potential startup issues.

1. Open Services console by running services.msc
2. Locate the problematic service and double-click to open Properties
3. Check the Dependencies tab to identify required services
4. Verify all dependencies are running using PowerShell:

   $serviceName = "YourServiceName"
   $service = Get-Service -Name $serviceName
   $dependencies = Get-Service -Name $serviceName -DependentServices
   $dependencies | Format-Table Name, Status, StartType

5. Check the service's startup type and account configuration in the General and Log On tabs
6. Review the service executable path and verify file existence:

   $servicePath = (Get-WmiObject -Class Win32_Service -Filter "Name='$serviceName'").PathName
   Test-Path $servicePath.Split('"')[1]

7. Attempt manual service startup and monitor for immediate failures

Examine and potentially adjust service timeout settings to resolve startup issues.

1. Check the current service timeout value in the registry:

   Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control" -Name "ServicesPipeTimeout"

2. Open Registry Editor as Administrator and navigate to HKLM\SYSTEM\CurrentControlSet\Control
3. Look for the ServicesPipeTimeout DWORD value (default is 30000 milliseconds)
4. Check service-specific timeout settings:

   $serviceName = "YourServiceName"
   $regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\$serviceName"
   Get-ItemProperty -Path $regPath -ErrorAction SilentlyContinue

5. If the service consistently requires more time to start, consider increasing the timeout:

   # Increase global service timeout to 60 seconds (60000 ms)
   Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control" -Name "ServicesPipeTimeout" -Value 60000 -Type DWord

6. Restart the system to apply timeout changes
7. Monitor subsequent service startups to verify improvement

Use advanced diagnostic tools to identify the root cause of service startup failures.

1. Enable service control manager debug logging:

   New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter" -Name "DEFAULT" -Value 0xFFFFFFFF -PropertyType DWord -Force

2. Use Process Monitor (ProcMon) to trace service startup activity:
   • Download ProcMon from Microsoft Sysinternals
   • Set filters for the service executable name
   • Attempt service startup while monitoring file/registry access
3. Check Windows Error Reporting logs for service crashes:

   Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='Windows Error Reporting'} -MaxEvents 10 | Where-Object {$_.Message -like "*YourServiceName*"}

4. Analyze service dependencies with PowerShell:

   $serviceName = "YourServiceName"
   $service = Get-WmiObject -Class Win32_Service -Filter "Name='$serviceName'"
   $dependencies = $service.ServiceDependencies
   foreach ($dep in $dependencies) {
       $depService = Get-Service -Name $dep
       Write-Output "$dep : $($depService.Status)"
   }

5. Check system resource utilization during service startup using Performance Monitor
6. Review Application and System event logs for related errors occurring during the startup timeframe

When other methods fail, rebuild the service configuration to resolve persistent startup issues.

1. Export the current service configuration for backup:

   $serviceName = "YourServiceName"
   $service = Get-WmiObject -Class Win32_Service -Filter "Name='$serviceName'"
   $service | Export-Clixml -Path "C:\Temp\$serviceName-backup.xml"

2. Stop the problematic service and any dependent services:

   Stop-Service -Name $serviceName -Force
   Get-Service -Name $serviceName -DependentServices | Stop-Service -Force

3. Remove and recreate the service registration:

   # Note: Only for non-critical system services
   # sc delete $serviceName
   # sc create $serviceName binPath="C:\Path\To\Service.exe" start=auto

4. Reset service permissions using the Services console or PowerShell:

   $acl = Get-Acl "HKLM:\SYSTEM\CurrentControlSet\Services\$serviceName"
   # Review and reset permissions as needed

5. Verify service executable integrity:

   $servicePath = (Get-WmiObject -Class Win32_Service -Filter "Name='$serviceName'").PathName
   sfc /scanfile=$servicePath.Split('"')[1]

6. Restart dependent services in proper order and test functionality