Windows Service Control Manager won't start — real fix

The 30-second fix: boot into Safe Mode

Had a client call me last month — their whole network printing stopped because the Print Spooler service wouldn't start. Turned out the Service Control Manager was corrupted from a Windows update that failed halfway.

First thing: boot into Safe Mode. This loads only the core drivers and services. If SCM works there, the problem is a third-party service or driver.

Restart your PC.
As soon as the Windows logo appears, hold the Shift key and click Restart from the power icon.
Go to Troubleshoot > Advanced options > Startup Settings.
Click Restart again, then press 4 or F4 for Safe Mode.

Once in Safe Mode, try opening Task Manager or services.msc. If they open fine, you've got a bad driver or startup app. Run msconfig and disable all non-Microsoft services under the Services tab. Reboot normal — if it works, turn services back on one by one until the crash returns.

Real example: One guy's antivirus was hooking into the SCM process and killing it. Disabled it in Safe Mode, uninstalled, and switched to Defender. Problem gone in 2 minutes.

The 5-minute fix: System File Checker and DISM

If Safe Mode still crashes, or SCM won't start there either, you've got system file damage. This is common after a power loss during an update — files get half-written.

Open an elevated Command Prompt (right-click Start, choose Command Prompt (Admin) or Terminal (Admin)).

Run this first:

DISM /Online /Cleanup-Image /RestoreHealth

This repairs the component store — the base that Windows Update uses. Takes a few minutes. Let it finish.

Then run:

sfc /scannow

This checks all protected system files. If it finds corrupt ones, it replaces them from a cache. If the cache is also corrupt, DISM already fixed that.

After both, reboot. I've had this fix SCM failures on Windows 10 22H2 and Windows 11 23H2. About 70% of the time, that's all you need.

When SFC fails to repair

Sometimes SFC says it found corrupt files but can't fix them. Check the log at C:\Windows\Logs\CBS\CBS.log. Look for lines with [SR] — they tell you which file is bad. If it's services.exe or svchost.exe, you might need the next fix.

The 15-minute fix: registry hacks and update removal

If DISM and SFC didn't work, we go deeper. This usually means a specific update broke things, or the registry is hosed.

Step 1: Uninstall the last Windows Update

Open Settings > Windows Update > Update history > Uninstall updates. Look for the most recent update (date-wise). Select it and click Uninstall. Reboot. If SCM works now, block that update from reinstalling — use the Show or hide updates troubleshooter from Microsoft.

Step 2: Check the registry for orphaned services

This is the advanced part. A corrupted service entry in the registry can lock up the SCM. Open regedit.exe as Admin.

Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

This lists every service. Look for keys with weird names — like ! or _ prefixes. Also check keys that have no ImagePath value, or where the Start value is 0 (boot-start) but the driver file is missing.

Export that key first (right-click Services, Export) as a backup. Then delete the bad key. I've seen third-party backup software leave behind a nonsense service that hung the SCM.

Step 3: Repair or replace services.exe

Services.exe is the actual executable for the SCM. If it's corrupt, you can copy a clean one from another working PC with the same Windows version. Or run a Windows repair install using the Media Creation Tool — choose Keep personal files and apps. This replaces system files without wiping your data.

I've done this twice this year alone. Both times it fixed the SCM when nothing else did.

When to give up and nuke it

If you've done all three steps and the SCM still won't start, you're looking at a deeper issue — maybe a failing hard drive or corrupted volume. Run chkdsk C: /f from an admin command prompt and reboot. It'll check for bad sectors. If it finds a bunch, replace the drive. Had a client whose SCM failure was actually a dying SSD — once we swapped it, Windows reinstalled clean and everything worked.

Otherwise, a fresh Windows install is the final option. Use the Media Creation Tool, boot from USB, and install over the existing Windows (choose custom install, delete all partitions). Yes, it's a pain. But it beats spending 4 hours chasing a ghost.