Print Jobs Stuck? Why the Windows Spooler Keeps Crashing — And How to Clear It for Good

Your document is queued. The status says "Printing." The printer is doing absolutely nothing. You cancel the job. It doesn't cancel. You try printing again. It queues behind the first one. Now you have three stuck jobs and a rising urge to throw something heavy.

Welcome to the Windows Print Spooler failure — one of the most reliably frustrating recurring problems in Windows, and one of the most reliably fixable once you understand what's actually going wrong.

What Is the Print Spooler, Exactly?

The Print Spooler (formally spoolsv.exe) is a Windows service that manages print jobs. When you click Print, your document doesn't go directly to the printer — it gets written to a temporary file in C:\Windows\System32\spool\PRINTERS and handed to the Spooler service, which queues it and feeds it to the printer driver at the appropriate moment.

This is actually a sensible design: it lets Windows hand control of the print job back to you immediately while the slower work of sending data to the printer happens in the background. The problem is that the Spooler service is one of the more fragile components in Windows, and when it crashes, all queued jobs freeze in place — and the files that represent those jobs can become impossible to delete through the normal cancel button.

Why the Spooler Keeps Crashing

There are five main causes, and it's worth knowing which one you're dealing with before reaching for the fixes.

Corrupted spool files. A print job that was interrupted mid-transmission can leave a corrupted .SHD or .SPL file in the spool folder. The next time the Spooler tries to process the queue, it chokes on the bad file and crashes or hangs.

Driver conflicts. If you have multiple printers installed — especially older ones — their drivers can conflict. A bad interaction between two drivers causes the Spooler to crash when either printer receives a job.

Windows Update damage. Windows 11 updates have a documented history of breaking printer drivers silently. A patch updates a core print component, the installed driver becomes incompatible, and the Spooler starts throwing errors on every job.

Third-party print software. PDF printers, label printing software, and virtual printers (like OneNote) all install their own Spooler-dependent components. A buggy update to any of them can destabilise the entire queue.

Spooler folder permissions. Rare, but real: if the permissions on the spool folder have been altered (sometimes by security software), the Spooler service can't write or read job files and crashes immediately.

Quick Fix: Restart the Spooler Service

This clears stuck jobs immediately and gets you printing in under two minutes. It doesn't fix the underlying cause but it's what you need right now.

• 1
  Open Services as Administrator

  Press Win + R, type services.msc, hit Enter. Right-click the taskbar and choose "Run as administrator" if prompted.
• 2
  Find "Print Spooler" in the list

  Scroll to the P section. You should see "Print Spooler" with a status of "Running" or blank (if it's crashed).
• 3
  Stop the service

  Right-click Print Spooler → Stop. Wait for it to fully stop before proceeding.
• 4
  Delete spool files

  Navigate to C:\Windows\System32\spool\PRINTERS. Delete everything inside the folder — but not the folder itself. These are your stuck jobs.
• 5
  Restart the service

  Back in Services, right-click Print Spooler → Start. Your printer queue is now empty and the service is running clean.

If the Spool Folder Won't Clear

Sometimes Windows won't let you delete files from the PRINTERS folder even after stopping the service. This usually means another process has a lock on the files. The reliable workaround is to boot into Safe Mode (where fewer background services run), navigate to the spool folder, and delete the files there. Normal mode deletion will work after a Safe Mode boot.

Fixing Driver Conflicts

If the Spooler restarts successfully but crashes again after the next print job, you almost certainly have a driver conflict. The fastest way to diagnose this is to remove all printers except the one you actively use, then reinstall the driver fresh from the manufacturer's website — not through Windows Update.

HP users in particular should download the full driver package from HP's support site rather than using the stripped-down version Windows installs automatically. The Windows-installed version frequently omits components the Spooler needs to manage job priority correctly.

Preventing It From Happening Again

Once you've cleared the immediate problem, a few configuration changes will significantly reduce recurrence. In Services, set Print Spooler to restart automatically on failure: right-click → Properties → Recovery tab → set "First failure" and "Second failure" to "Restart the Service." This means a crash won't leave you stranded — the service will recover itself.

Additionally, avoid installing printer software from the disc that comes in the box. Manufacturer CDs are invariably out of date and often include components that conflict with modern Windows. Always download the latest driver directly from the manufacturer's support page.