Stuck or undeletable print jobs
A job that appears to be printing forever, or that will not delete no matter how many times you press cancel, is almost always a stuck job rather than a broken printer. The operating system keeps a record of every job on a queue, and until that queue is cleared no further job will run. The steps below go from a two-click fix to the full service reset, in that order.
Open the queue and look at the status column. Paused means someone pressed pause — click Resume. Error means the job itself is the problem. Only a job showing Printing or Pending for several minutes with no printer activity is genuinely stuck. Also check the destination: a job sent to a file, a PDF writer or an offline port looks exactly like a stuck print.
Why one job blocks everything behind it
The operating system does not hand work straight to the printer. Every job goes into a queue held by a background service — the print spooler — and only one job is processed at a time, in order.
- If the first job in the queue cannot complete, the ones behind it never start.
- If the printer connection dropped, the spooler is still holding the job and still waiting for it to finish.
- Because the spooler survives applications closing, a frozen job can survive rebooting the application — and sometimes the whole computer.
That last point is why the fix involves the spooler rather than the application.
Windows: four escalating steps
Step 1 — Cancel from the queue window
- Press Ctrl + P and choose the printer.
- Click Open print queue.
- Select all jobs with Ctrl + A, then click Cancel.
- If the button is greyed out, go to step 2.
Step 2 — Restart the print spooler
This releases any job the system has marked as unfinishable, and it is safe to do at any time.
Open the services list
Win + R → services.msc
- Find Print Spooler in the list.
- Right-click → Restart. If it is already stopped, choose Start.
- Reopen the queue. The stuck jobs will usually be gone.
Step 3 — Delete the spool files directly
Use this when restarting the spooler is not enough, which usually means a job record has been corrupted.
- Open the services list again and stop the Print Spooler. Do not close the window yet.
- Open File Explorer and paste this path into the address bar:
Spool folder
%SystemRoot%\System32\spool\PRINTERS - Select every file inside and delete them all. These are temporary job records, not your documents.
- Return to the services list and start the Print Spooler again.
- Open the queue and add the printer back if it disappeared from the list.
If it is still running, the files will be locked and will either refuse to delete or be recreated before the job is cancelled. This is the reason most attempts at this step appear not to work.
Step 4 — Check for something re-adding the job
If jobs get stuck repeatedly, something is recreating them. Check these before reinstalling anything:
- Startup programs: print management utilities, document conversion tools and backup software sometimes queue documents at sign-in.
- Duplicate printer entries: two entries pointing at the same physical printer will produce two queues, and jobs sent to the wrong one appear to vanish.
- A second computer or a phone on the network: the same job may have been sent twice, and the second instance blocks the first.
- The printer's own port: if it is set to a port that no longer exists, every job will hang at the same point.
macOS
- Open System Settings → Printers & Scanners.
- Select the printer and click Open Print Queue.
- Select all jobs and click the − button to delete them, or | to pause and ▶ to resume.
- If the queue will not open, restart the printing system from a terminal:
Commands
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.printnotify.plist sudo launchctl load /System/Library/LaunchDaemons/com.apple.printnotify.plist - On a stubborn printer, remove it with Remove Printer, restart, and add it again.
Send one document to Save as PDF instead of the printer. If that works instantly, the file and the application are fine, which narrows the problem to the queue, the port or the printer itself. It takes ten seconds and rules out half of the possible causes.
After clearing the queue
- Check the port is still correct before sending anything, particularly after a reinstall:
Check the port
Devices and Printers → right-click printer → Printer Properties → Ports tab - Print one test page rather than a whole document.
- If the job reaches the queue and then disappears without printing, the job is being sent somewhere else — check the destination in the print dialog.
- If the job disappears silently every time, note the timestamp and check the printer's own job history on its web page or panel, which often shows whether it ever arrived.
Questions
Why can I not delete a print job?
The cancel button is greyed out when the job is in a state the system treats as final but unfinished, which happens when the connection to the printer dropped mid-job. Clearing the queue restarts the spooler, which releases the record. Restarting the print spooler service is the quickest way to do that.
Does clearing the queue delete the document?
No. The queue holds a reference to the file, not the file itself. Clearing the queue removes the pending print instruction; your document is untouched and can be printed again as soon as the printer is working.
Should I disable the spooler permanently?
No. Some advice recommends setting the spooler to disabled to avoid these problems. That does stop jobs printing, because the spooler is the component that hands work to the printer. If jobs hang regularly, the underlying cause is worth finding instead.
Why do jobs get stuck after a crash or forced shutdown?
The spooler writes a temporary file for each job as it prepares it. A crash or forced shutdown leaves those files behind, and on the next start the spooler tries to process records whose printer connection no longer exists. Clearing the spooler folder removes them.
Will clearing the queue also fix an offline printer?
No, and the difference is worth being clear about. Clearing the queue deals with the computer record of work. An offline printer is a connection fault, which is a separate problem covered in the offline guide.
Related guides
Printer shows offline
When the machine is reachable but not accepting work.
Open guideNothing prints
For the broader case where output never starts at all.
Open guidePrinter not detected
When the queue itself has vanished from the device list.
Open guideBlank pages and margins
When jobs complete but produce empty or cut-off pages.
Open guide