Stuck 'Deleting' Print Queue—Fix It in 2 Minutes
Your print job says 'Deleting' but won't clear. I'll show you how to kill the spooler service and delete the stuck file manually.
Quick answer
Stop the Print Spooler service (services.msc), delete everything in C:\Windows\System32\spool\PRINTERS, then restart the spooler.
Why this happens
You hit print, it fails, now the queue shows a job stuck on 'Deleting – 0 pages'. It won't move. You restart the printer, reboot your PC, still there. I've seen this a dozen times—most recently with a client's Canon imageCLASS running on Windows 11. The spooler (the service that manages print jobs) gets confused. It thinks the job is still in memory, but the file is corrupted or the printer disconnected mid-delete. The result: a frozen ghost job.
Here's the real fix. Not the 'cancel all documents' button (that rarely works). You need to manually kill the spooler, delete the temp files, and restart clean.
Step-by-step fix
- Open Services – Press
Win + R, typeservices.msc, hit Enter. - Stop the Spooler – Scroll down to Print Spooler, right-click, select Stop. Leave the window open.
- Delete the stuck file – Open File Explorer, go to
C:\Windows\System32\spool\PRINTERS. Select everything inside (pressCtrl + A), delete it. You might need admin permission—click Yes. - Restart the Spooler – Go back to the Services window, right-click Print Spooler, select Start.
- Test it – Open your printer queue again. The stuck job should be gone. Print a test page to confirm.
Alternative fixes if this fails
If the file delete fails (Windows says it's in use), you didn't stop the spooler properly. Double-check the service is stopped. If it restarted automatically, set it to disabled first, then stop it again.
Another trick: Open Command Prompt as Administrator, run net stop spooler, then del /Q /F C:\Windows\System32\spool\PRINTERS\*.*, then net start spooler. This does the same thing but bypasses the GUI if it's being stubborn.
If the job still shows, check the printer itself. Some printers (especially HP and Canon) cache jobs internally. Power-cycle the printer—unplug for 30 seconds, plug back in. That clears its internal queue.
Last resort: Run the Windows Print Troubleshooter (Settings > Troubleshoot > Other trouble-shooters > Printer). It's hit-or-miss, but I've seen it fix weird spooler corruption on Windows 10 22H2.
Prevention tip
Don't let print jobs pile up. If a print fails, cancel it immediately—don't keep retrying. Set your printer's default timeout higher (in printer properties, under Advanced) so it doesn't time out mid-job, which is usually what causes this mess. Also, avoid printing PDFs with embedded fonts that drag the spooler—convert to plain PDF first.
Pro tip: Use a dedicated print server (like a Raspberry Pi running CUPS) for businesses with 5+ printers. The spooler is more stable, and stuck jobs are easier to clear remotely.
One more thing
If you're on a network printer (e.g., HP LaserJet Pro M404), check the printer's own web interface. Sometimes the job is stuck in its internal memory. Log in via its IP address, go to Jobs or Print Queue, and delete from there. Had a client last month whose entire office print queue died because of a single corrupted job cached on the printer. That's rare, but it happens.
Was this solution helpful?