Print queue stuck on Windows 11
The queue window lists your document, the status never changes, and the printer does nothing. The device is usually fine: one job is blocking every job behind it, and Windows will not remove it while the spooler is holding the file.
Get PrinterFix from the Microsoft StoreOne job blocks all of them
A print queue is strictly ordered. If the job at the head cannot be rendered or sent, the jobs behind it wait, no matter how healthy they are. That is why "nothing prints" and "one document is stuck" are the same fault seen from two angles.
| What you see | Likely cause | First move |
|---|---|---|
| Status stuck on "Deleting" | Spooler holds the file open | Stop the service, then clear the spool folder |
| Status stuck on "Printing", no output | Port or driver problem, job never leaves | Check the printer's port; try a test page |
| Jobs disappear but nothing prints | Job goes to a virtual queue (PDF, OneNote, redirected) | Check which printer is the default |
| Only large documents fail | Driver runs out of memory rendering the job | Print in smaller parts; update the driver |
Clearing it, in order
- Cancel the job in the queue window. If it disappears, you are done.
- If it stays, stop the Print Spooler service (
services.msc). - Delete everything in
C:\Windows\System32\spool\PRINTERS- those files are the queued jobs. - Start the service and print a one-page test. If that works, the queue is clean.
- If the same document re-blocks it, print that document to PDF first, then print the PDF. That rules the application out of the chain.
"Cannot delete print job" is not a permissions problem
Windows refuses to delete a job the spooler is actively using, and it reports that as a generic failure. Granting permissions or reinstalling the printer does not change it, because the file is still open. The service must be stopped first - that is the whole fix.
What PrinterFix does
It reads the queue, the spooler state and the port, then shows the repair steps before running them. The queue clearing step is listed explicitly, because those jobs are discarded. Diagnosis is read-only; repair needs one administrator prompt. Offline, no account, no telemetry.
Free for one printer per task. The optional Pro add-on adds batch repair, a restore point before the repair, and a PDF report of what was found.
What this cannot fix
Toner, paper, a jam, a failed fuser, a printer that lost its network address - hardware and network faults. A clean queue does not make a broken device print.
Questions
Why does the job come back after I delete it?
Because the spooler still has the file open. Delete it with the service stopped: while <code>spoolsv.exe</code> runs, the file stays locked and Windows restores the job on the next refresh.
Is it safe to delete files in the spool folder?
Yes, if the Print Spooler service is stopped. Those files are the queued print jobs - deleting them cancels those jobs permanently. Nothing else in Windows uses that folder.
Do I need to reinstall the printer driver?
Not as a first step. A stuck job and a stopped spooler are far more common and take under a minute to check. Reinstall the driver only after those are ruled out.