Fix Service Control Manager Error 7023 – Windows 10/11 2026

System file corruption is the most common cause of error 7023. Start with SFC and DISM to repair damaged files.

1. Press Windows + X and select Windows Terminal (Admin) or Command Prompt (Admin)
2. Run the System File Checker:

sfc /scannow

Wait for the scan to complete. This may take 15-30 minutes.

3. If SFC finds corrupted files it cannot repair, run DISM to fix the Windows image:

DISM /Online /Cleanup-Image /RestoreHealth

4. After DISM completes, run SFC again to ensure all files are repaired:

sfc /scannow

5. Restart your computer and check if the affected services start properly

If specific services continue failing, reset their configurations to default values.

1. Open Services.msc by pressing Windows + R, typing services.msc, and pressing Enter
2. Locate the failing service and note its exact name
3. Open Command Prompt as Administrator
4. Stop the service if it's running:

net stop "ServiceName"

5. Reset the service to its default configuration. For Windows Update service example:

sc config wuauserv start= auto
sc config wuauserv type= share
sc config wuauserv error= normal

6. For critical system services, you can also reset dependencies:

sc config wuauserv depend= rpcss

7. Clear the service's failure actions:

sc failure "ServiceName" reset= 0 actions= ""

8. Restart the service:

net start "ServiceName"

Corrupted registry entries can prevent services from starting. This method repairs service-related registry keys.

1. Press Windows + R, type regedit, and press Enter
2. Navigate to the service registry location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

3. Locate the folder for your failing service (e.g., "wuauserv" for Windows Update)
4. Right-click the service folder and select Export to create a backup
5. Check the following critical values and repair if corrupted:

• ImagePath: Should contain the correct path to the service executable
• Start: Should be a DWORD with appropriate startup type (2=Automatic, 3=Manual, 4=Disabled)
• Type: Should match the service type (typically 16 for shared process, 32 for interactive)

6. If values are missing or corrupted, you can restore them. For Windows Update service:

ImagePath: %systemroot%\system32\svchost.exe -k netsvcs -p
Start: 00000003 (DWORD)
Type: 00000020 (DWORD)

7. Close Registry Editor and restart the computer
8. Open Command Prompt as Administrator and rebuild the service database:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Service dependencies and permissions issues can cause error 7023. This method rebuilds the service dependency chain and resets permissions.

1. Open Command Prompt as Administrator
2. Stop all dependent services first. For example, if fixing Windows Update:

net stop wuauserv
net stop cryptsvc
net stop bits
net stop msiserver

3. Reset Windows Update components (adapt for other services):

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

4. Re-register service-related DLL files:

regsvr32 /s atl.dll
regsvr32 /s urlmon.dll
regsvr32 /s mshtml.dll
regsvr32 /s shdocvw.dll
regsvr32 /s browseui.dll
regsvr32 /s jscript.dll
regsvr32 /s vbscript.dll
regsvr32 /s scrrun.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml6.dll
regsvr32 /s actxprxy.dll
regsvr32 /s softpub.dll
regsvr32 /s wintrust.dll
regsvr32 /s dssenh.dll
regsvr32 /s rsaenh.dll
regsvr32 /s gpkcsp.dll
regsvr32 /s sccbase.dll
regsvr32 /s slbcsp.dll
regsvr32 /s cryptdlg.dll

5. Reset service permissions using the built-in tool:

sc sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

6. Restart the services in proper dependency order:

net start cryptsvc
net start bits
net start wuauserv
net start msiserver

For persistent error 7023 issues, use PowerShell to perform comprehensive service and system repairs.

1. Open Windows PowerShell as Administrator
2. Run a comprehensive service health check:

Get-Service | Where-Object {$_.Status -eq "Stopped" -and $_.StartType -eq "Automatic"} | ForEach-Object {
    Write-Host "Attempting to start: $($_.Name)" -ForegroundColor Yellow
    try {
        Start-Service $_.Name -ErrorAction Stop
        Write-Host "Successfully started: $($_.Name)" -ForegroundColor Green
    }
    catch {
        Write-Host "Failed to start: $($_.Name) - $($_.Exception.Message)" -ForegroundColor Red
    }
}

3. Reset Windows Update components completely:

$services = @("wuauserv", "cryptsvc", "bits", "msiserver")
foreach ($service in $services) {
    Stop-Service $service -Force -ErrorAction SilentlyContinue
    Set-Service $service -StartupType Manual
}

# Clear Windows Update cache
Remove-Item "C:\Windows\SoftwareDistribution" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item "C:\Windows\System32\catroot2" -Recurse -Force -ErrorAction SilentlyContinue

# Reset services to automatic
foreach ($service in $services) {
    Set-Service $service -StartupType Automatic
    Start-Service $service
}

4. Perform a comprehensive system file verification:

# Run multiple repair tools in sequence
Start-Process "sfc" -ArgumentList "/scannow" -Wait -WindowStyle Hidden
Start-Process "DISM" -ArgumentList "/Online", "/Cleanup-Image", "/RestoreHealth" -Wait -WindowStyle Hidden
Start-Process "chkdsk" -ArgumentList "C:", "/f", "/r" -Wait -WindowStyle Hidden

5. Check and repair service executable permissions:

$servicePaths = @(
    "C:\Windows\System32\svchost.exe",
    "C:\Windows\System32\services.exe",
    "C:\Windows\System32\lsass.exe"
)

foreach ($path in $servicePaths) {
    if (Test-Path $path) {
        icacls $path /reset /T /C /Q
        Write-Host "Reset permissions for: $path" -ForegroundColor Green
    }
}

6. Restart the computer to apply all changes