The Print Spooler Keeps Stopping in Windows: How to Fix "Spooler Service Not Running"

You hit print and nothing happens — or Windows flashes a "Print Spooler service is not running" message, and you can't even add or open a printer. This looks like a dead printer or a driver disaster, but it's usually neither. It's one small Windows background service that has either jammed on a bad print job or been knocked over by a faulty driver. The good news is that there are really only two root causes, and once you know which one you've got, the fix takes a couple of minutes.

What the print spooler actually is

The Print Spooler is a background service built into Windows (its file is spoolsv.exe). Every time you print, your document doesn't go straight to the printer — it goes into a queue that the spooler manages, holding each job and feeding it to the printer in order. That's why you can fire off five documents at once and walk away: the spooler lines them up. Because every single print job passes through it, when the spooler stops, everything stops. Nothing prints, the queue freezes, and Windows tools that talk to it (adding a printer, opening printer properties) start throwing errors.

So the symptom — "nothing prints" or "spooler not running" — is downstream of one of two things: the spooler choked on a corrupted job sitting in its queue, or a misbehaving printer driver is crashing it the moment it starts. Work through them in that order and you'll clear the large majority of cases.

Fix #1: clear the stuck queue (the most common cause)

A single corrupted or half-finished print job can wedge the whole spooler — it keeps trying to process the broken job, fails, and stalls. Clearing the queue files by hand fixes this, and it's the first thing to try. The trick is that you have to stop the spooler first, delete the jammed jobs, then start it again.

The clean way: press Windows key + R, type services.msc and press Enter. Scroll to Print Spooler, right-click it and choose Stop (leave this window open). Now open File Explorer and go to C:\Windows\System32\spool\PRINTERS — this folder is where queued jobs live. Delete everything inside it (the folder itself stays; just empty its contents). Then go back to the Services window, right-click Print Spooler again and choose Start. Try printing.

If you're comfortable with the command line, the same thing is faster: open Command Prompt or Terminal as administrator and run, one line at a time, "net stop spooler", then "del /Q /F /S "%systemroot%\System32\spool\PRINTERS\*.*"", then "net start spooler". That stops the service, wipes the stuck jobs, and restarts it. Either route clears a jammed queue, which is the single most frequent reason the spooler won't stay running.

Fix #2: if it stops again within seconds, it's a driver

Here's the tell-tale pattern: you start the spooler, it runs for a few seconds, then stops itself — over and over. That almost always means a printer driver is crashing it. Conflicting, outdated, or duplicate drivers are the classic cause, and they pile up over the years as you add and remove printers, so the fix is to clean them out.

Open Device Manager (right-click Start > Device Manager), expand Print queues and Printers, and remove printers you no longer own. Then open Settings > Bluetooth & devices > Printers & scanners and remove old or duplicate entries there too. If the spooler will stay running long enough, reinstall just your current printer using the latest full driver from the manufacturer's website (HP, Brother, Canon, Epson) rather than the basic one Windows picks automatically. If you have several printers installed and don't know which one is the culprit, remove them one at a time, testing the spooler after each, until it stays up — the last one you removed is the bad apple.

To find the offending driver directly, open Event Viewer (type it into Start), and look under Applications and Services Logs > Microsoft > Windows > PrintService > Admin, or under Windows Logs > System for "Print Spooler" or "spoolsv" errors. The crash details often name the exact driver, port, or file that brought the service down, which tells you precisely what to remove.

When it broke right after a Windows update

If printing was fine until a Windows update and then the spooler started failing, the update likely left a driver mismatched or a system file in a bad state. Two repair commands fix most of this. Open Command Prompt or Terminal as administrator and run "sfc /scannow" — it checks and repairs Windows system files, including spoolsv.exe itself if it got damaged. If that doesn't do it, run "DISM /Online /Cleanup-Image /RestoreHealth" and then "sfc /scannow" again. After that, reinstall the current full driver for your printer from the maker's site, since an update can quietly replace a working driver with a generic one that doesn't agree with your model.

Make Windows restart the spooler on its own

While you're tracking down the real cause, you can tell Windows to bring the spooler straight back up whenever it stops, so you're not restarting it by hand all day. In the Services window, double-click Print Spooler, go to the Recovery tab, and set First failure, Second failure, and Subsequent failures all to "Restart the Service." This is a stopgap, not a cure — if a driver is crashing it, it'll just keep restarting and crashing — but it keeps you printing while you sort out the underlying driver, and it's genuinely useful on a machine that only hiccups occasionally.

One more suspect: security software

Occasionally it's not Windows or a driver at all — some antivirus and security suites watch the spooler closely (it has been targeted by malware in the past) and can interfere with it or the files it needs. If the spooler keeps dying and nothing above has helped, check whether your security software is blocking spoolsv.exe or the spool folder, and add an exclusion for C:\Windows\System32\spool if so. As always, change the setting rather than turning protection off and leaving it off.

When to hand it over

The print spooler is one of those problems that's usually a five-minute fix once you know it's the queue or a driver — but if it keeps crashing after you've cleared the queue, stripped out old drivers, run the system-file repairs, and checked your security software, something deeper is going on (a corrupted print subsystem, a stubborn driver conflict, or update damage), and it's worth getting a second set of hands on it. We fix printing and spooler problems across Southern California and the Coachella Valley, in person or by remote support, and we'll get it printing again and leave the drivers clean so it doesn't keep falling over.