Fix Printer Spooler Service Won't Start

Your spooler won't start? Yeah, it's annoying.

You click Start, type 'services.msc', find the Print Spooler, right-click Start. Nothing happens. Or maybe it starts then stops a second later. Had a client last month whose whole office print queue died because of this. Here's the fix that works every time.

The quick fix: nuke the spooler folder

The number one reason the spooler won't start is a corrupt file in C:\Windows\System32\spool\PRINTERS. One bad print job can lock up the whole service. Here's what to do:

Open Command Prompt as Administrator (right-click Start, choose 'Command Prompt (Admin)' or 'Windows Terminal (Admin)').
Stop the spooler with this command:
```
net stop spooler
```
If it says 'stopped already', cool. If it says 'failed to stop', skip to step 3 anyway.
Now delete the contents of the PRINTERS folder:
```
del /q /f /s C:\Windows\System32\spool\PRINTERS\*.*
```
This removes everything in there – corrupt files, stuck jobs, the works.
Restart the spooler:
```
net start spooler
```

That's it. Most of the time the service starts right up. If it doesn't, move to the next step.

Why this works

The spooler service holds temporary files for print jobs in that PRINTERS folder. A corrupt job – like a PDF that didn't render right or a driver that crashed mid-spool – can make the service hang or fail when it tries to read the queue. Deleting those files clears the logjam. I've seen this fix work on Windows 10, 11, even Server 2016. Simple and effective.

When the folder trick doesn't work

Sometimes the spooler still won't start after clearing the folder. Here are the less common causes and their fixes:

Bad printer driver still loaded

If a driver is stuck in the spooler's memory, you need to remove it from the registry. Do this:

Open Regedit as Administrator.
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3 (or Version-4 for some printers).
Delete any subkey that looks like a printer you don't have or a driver that's known to cause issues (e.g., old HP or Canon drivers).
Restart the spooler service.

Spooler service dependencies missing

The Print Spooler relies on RPC (Remote Procedure Call) and HTTP services. If those are disabled, the spooler won't start. Check in services.msc that these are set to Automatic and running:

Remote Procedure Call (RPC)
RPC Endpoint Mapper
HTTP Service (if you see it)

Corrupt spooler executable

Rare, but if the actual spoolsv.exe file is corrupt, run an SFC scan:

sfc /scannow

This checks system files. Usually doesn't find anything, but worth a try if nothing else works.

Prevention tips

You don't want this headache again. Here's what I tell my clients:

Never cancel a print job mid-print. Wait for it to finish or at least stop the spooler before deleting. Abrupt cancellations are the #1 cause of corrupt files.
Update drivers from the manufacturer's site. Windows Update sometimes pushes bad drivers. Go to HP, Epson, Brother – whatever brand – and get the latest directly.
Set the spooler to restart on failure. In services.msc, right-click Print Spooler, Properties, Recovery tab. Set first failure to 'Restart the Service'. Saves you from having to manually restart it.

One last thing: if you're on a network with shared printers, check other machines too. A bad job from someone else's PC can hit the same spooler. I once spent an hour on a server spooler that kept dying – turned out someone was printing a 500-page Excel file that froze. Cleared the folder, job done.

That's the real fix. No fluff, no extra steps. Go get your printers working again.