Print spooler stuck on Windows
A print job that never leaves the queue is almost never a printer problem. The printer is fine, the cable is fine, and the job is sitting in a service on your PC that has stopped or is holding a file open. This is how to tell which one it is.
Get PrinterFix from the Microsoft StoreWhat the print spooler is
The Print Spooler (spoolsv.exe) is the Windows service that receives every print job first. It writes
the job to C:\Windows\System32\spool\PRINTERS, then hands it to the driver and the port. When the
service stops, or when one job cannot be written out, everything behind it waits - which looks exactly like a dead
printer.
| What you see | What is actually wrong | Check |
|---|---|---|
| Status stays "Printing" and nothing comes out | Spooler stopped, or the job is stuck mid-transfer | Services → Print Spooler: running? |
| A job says "Deleting" for minutes | The spooler still holds the file open | Stop the service, then clear the PRINTERS folder |
| Nothing prints and there is no error at all | Spooler set to Manual and never started | Services → Print Spooler → Startup type: Automatic |
| It fails only for one printer | That printer's port or driver, not the spooler | Printer properties → Ports |
The order that works
- Restart the Print Spooler service.
services.msc→ Print Spooler → Restart. This alone clears most stuck jobs. - If the job survives the restart, stop the service first. Right-click → Stop, then delete
the contents of
spool\PRINTERS. The service must be stopped: while it runs, Windows keeps the file open, the delete fails, and the job comes back. - Start the service again and print a test page. If the test page works, the fault was the queue, not the printer.
- Still stuck? Compare the port. A USB printer moved to another socket can enumerate as a new device on a new port, leaving the old queue pointing at nothing.
Why "clear the print queue" often appears not to work
Cancelling a job from the queue window only asks the spooler to remove it. If the spooler is the thing holding it, the request queues up behind the problem. That is why the working sequence stops the service before touching the spool folder - one skipped step is the whole difference.
What PrinterFix does
PrinterFix checks the spooler state, the queue and the port before it changes anything, then shows the exact steps it is about to run. Diagnosis is read-only. Repairing the spooler needs administrator rights, so Windows shows one elevation prompt when the repair starts; the app itself opens without them.
Clearing the queue discards the jobs in it - they are deleted, not paused. PrinterFix lists that as an action so you can see it before it runs. Offline: no telemetry, no account, no uploads.
What this cannot fix
A paper jam, a dead fuser, an empty toner cartridge or a printer that has dropped off the network is a hardware or network fault. No service restart changes those. If the spooler is healthy and the test page still does not print, the next step is the printer's own self-test, not another repair run.
Questions
Can I clear the spool folder while the service is running?
No. The spooler keeps the job files open, so the delete fails or the files reappear as soon as it restarts. Stop the Print Spooler service first, delete the files, then start the service.
Does restarting the spooler lose my queued documents?
A restart keeps the jobs; they resume when the service comes back. Deleting the spool folder does lose them - those jobs are discarded and have to be printed again.
Why does it keep coming back after I fix it?
Usually one application keeps sending a job the driver cannot render, and the same bad job re-blocks the queue. Check which document is at the head of the queue when it stalls; that is the one to delete.