Why Does The Print Spooler Keep Stopping? | Fixes That Last

If your printer works right after a restart, then dies on the next job, the spooler is usually the part that’s falling over. That service holds print jobs in line, hands them to the right driver, and keeps the printer queue moving. When it crashes, printing stalls, jobs pile up, and the printer can vanish from apps until the service starts again.

That sounds messy, but the pattern is often pretty clear. A single corrupt job can jam the queue. An old driver can knock the service over the moment a job lands. Damaged files in the spool folder can keep the crash loop going even after a reboot. If you know which pattern you’re seeing, the fix gets much shorter.

What The Print Spooler Actually Does

The print spooler is a Windows service named spoolsv.exe. It takes what an app sends to print, stores that job for a moment, then passes it through the printer driver and on to the printer. That lets you keep working while Windows handles the job in the background.

When the spooler stops, the whole handoff breaks. You might see print jobs stuck on “Deleting,” printers that show as offline when they aren’t, or apps that hang when you hit Print. If the service restarts and fails again right away, that usually means something tied to the queue or the driver is crashing it on contact.

Why Does The Print Spooler Keep Stopping? Usual Crash Triggers

Most repeat spooler crashes come from the same short list:

• One corrupt print job stuck in the queue
• A damaged or outdated printer driver
• Leftover driver files from an old printer
• Bad files inside the spool folder
• A printer add-on or print processor that fails when the service starts
• Low system resources or wider Windows instability
• Policy settings that turned the service off on purpose

A Stuck Job Can Break The Whole Queue

This is the classic case. You send one document to print, nothing comes out, then every job after that freezes behind it. The spooler may restart, but the bad job is still waiting, so the crash repeats. If the service stays up after you clear the queue, you’ve likely found the culprit.

Drivers Cause More Trouble Than Most People Expect

Printer drivers sit right in the middle of the print path, so a bad one can drop the whole service. That’s why spooler crashes often start after a printer swap, a Windows update, or a fresh install from a manufacturer package. If the spooler stays running until the second you print, the driver moves near the top of the suspect list.

Old Files And Old Queues Stick Around

Windows can keep stale print data in the spool folder even after you remove the printer from Settings. That leftover data can keep tripping the service. The same goes for driver packages that were “removed” but still left pieces behind in Print Server Properties.

What You Notice	Likely Cause	First Move
Jobs stuck on “Deleting”	Corrupt queue item	Stop the spooler and clear the PRINTERS folder
Service dies only when you print	Faulty driver	Remove the driver package and install a fresh one
Printer disappears from apps	Spooler crashed in the background	Restart the service, then check Event Viewer
Issue started after a new printer install	Driver conflict	Remove older drivers tied to printers you no longer use
Issue came after a Windows update	Driver mismatch or damaged queue data	Clear the queue, then update or reinstall the driver
Print to PDF fails too	Service-wide spooler fault	Work on the spooler itself, not only the printer
Service will not stay started	Spool files, plug-ins, or policy setting	Check dependencies, policy, and event logs
Only one printer triggers the crash	That printer’s driver or port setup	Remove that printer first and test again

Print Spooler Keeps Stopping In Windows: What To Check First

Microsoft’s own steps line up with what works most often in real use: clear the queue, restart the service, and check for conflicting drivers. Their fix for spooler errors in Windows starts there. Microsoft also notes that corrupt files in the spool folder and the RpcSs dependency can keep printing broken, and their Windows troubleshooting notes add that resource issues or policy settings can stop the service from staying up.

Here’s a practical order that saves time:

1. Restart the Print Spooler service.
2. Clear the queue and delete old spool files.
3. Try printing a plain test page.
4. If it crashes again, remove the printer that triggered it.
5. Remove that printer’s driver package.
6. Restart Windows and install a fresh driver.

If the service stays up after step two, your issue was probably a bad job or damaged queue file. If it crashes only when a printer is installed again, the driver is the stronger suspect.

If You See This	It Usually Means	Next Move
The queue clears and printing returns	Bad job or stale spool file	Watch for the one file or app that started it
The service stops the moment a printer is added back	Driver package is bad	Use a newer driver or a different driver branch
The service will not start at all	Service setting, dependency, or damaged print stack	Check RpcSs, event logs, and policy
Only one app fails	App output issue, not only the spooler	Test from Notepad or another simple app
PDF printing fails too	Windows print path is unstable	Treat it as a spooler issue, not a printer issue
Problem returns every few days	Old driver pieces still loaded	Clean out unused printers and driver packages

When The Problem Is The Driver, Not The Queue

Driver trouble has a telltale shape. The spooler starts fine. You open a document. You click Print. Then the service drops. That usually means the queue itself is not the first problem. The crash starts when Windows hands the job to the driver.

In that case, remove the printer, then remove its driver package too. If you skip the package, Windows may pull the same broken bits right back in. After that, restart the PC and install a fresh package from the printer maker. If there are several old printers listed that you no longer use, clean those out too. One bad leftover can keep spoiling the batch.

• Start with the printer that makes the spooler crash right away.
• Remove unused printers tied to old offices, old Wi-Fi networks, or dead USB ports.
• Test with one clean printer install before adding anything else back.

A Clean Fix Order That Saves Time

If you want one tidy routine instead of random trial and error, use this order:

1. Restart the service. Open Services, find Print Spooler, and restart it.
2. Clear the queue. Stop the service, empty C:\Windows\System32\spool\PRINTERS, then start the service again.
3. Test with a tiny print job. A one-line Notepad page is enough.
4. Remove the problem printer. If the crash returns, delete that printer.
5. Remove the driver package. Clear out the package so Windows does not reuse it.
6. Reinstall one driver. Add only one printer back and test again.
7. Check PrintService logs. Event Viewer can point to a driver, processor, or plug-in by name.

This order works because it separates queue trouble from driver trouble. Once you know which half is failing, the repair path gets much shorter.

What Usually Stops The Loop For Good

Most repeat spooler crashes end with one of two fixes: clearing damaged spool files or replacing a broken driver package. If the crash still comes back after both, look at Event Viewer under Applications and Services Logs > Microsoft > Windows > PrintService > Admin. That log often names the driver or print component that blew up.

If the service will not stay on even with no printers installed, widen the search. Check that Remote Procedure Call is running. Check whether a local or domain policy turned the service off. If the trouble started on a work PC after a security change, that policy angle becomes much more likely.

So, why does the print spooler keep stopping? In plain terms, Windows is hitting a bad print job, a bad driver, or damaged print files and shutting the service down to protect the rest of the print path. Clear the queue first. If that fails, strip out the driver package and rebuild from one clean install. That solves the issue more often than anything else.