Print job stuck in queue, how to clear it
Every Windows user meets this one: a job sits in the queue at Error, Deleting, or Printing forever, Cancel does nothing, and nothing behind it prints either. The queue is managed by the Print Spooler service, and a job it cannot process or release jams the line. Restarting the PC sometimes helps and often does not, because the bad job is stored on disk and reloads. The spool-file clear below is the method that works every time.
The fix, in order
- Try the polite cancel first. Open the print queue, right-click the stuck job, Cancel. Give it a full minute; large jobs take time to die. If the job changes to Deleting and stays there, move on.
- Turn the printer off. Power the printer down so it stops requesting or holding part of the job. A printer holding half a page in memory keeps the queue negotiating instead of clearing.
- Stop the spooler and delete the spool files. In services.msc, stop Print Spooler. Delete everything in C:\Windows\System32\spool\PRINTERS (these are the queued jobs, stored as .SPL and .SHD pairs). Start Print Spooler again. The queue now opens empty, which is the goal.
- Turn the printer back on and print a test page. Use the printer's entry in Settings to print a test page. A clean test proves the path works before real documents are sent again.
- Reprint the problem document differently. If the jam came from one file, print it in smaller batches of pages, or print it as a PDF (or use Print as image in the PDF reader's advanced options). A page the printer's interpreter chokes on will jam again if sent identically.
- Check for a driver mismatch on repeat jams. Jobs that spool as the wrong data type, or a PCL versus PostScript mismatch on office printers, jam at the same point repeatedly. Reinstalling the correct vendor driver ends the pattern.
If it still happens
On a shared printer, one user's stuck job blocks everyone, and only the host PC's spool folder matters: clear it on the host, not on each client. If jobs stick at the same size or page from many applications, the printer itself is faulting mid-job, which shows in its event log or display, and that is a printer problem rather than a queue problem.
Common questions
Why will the job not delete even after a restart? Because queued jobs are files on disk, not memory. A restart reloads the same corrupt job into the same queue. Deleting the spool files while the service is stopped is what actually removes it.
Will clearing the spool folder delete other people's jobs on a shared printer? Yes, on the host it clears the whole queue for that printer. Warn anyone with jobs waiting, or have them resend; there is no supported way to surgically remove one job's spool files reliably.
Related errors