Software

How to clear a stuck print queue on Windows and Mac

4 min read · Updated · PrinterErrors editorial team

Overview

A "stuck" queue is a document that will not print and will not cancel, often blocking everything queued behind it. In most cases you can clear it with the built-in cancel option in seconds. If a job refuses to disappear, the next reliable step is to restart the service that manages printing (the Print Spooler on Windows) or, on Mac, reset the printing system.

Everything here uses tools built into Windows and macOS. Nothing on this page requires firmware changes, chip resets, or third-party utilities. Try the simplest step first and only escalate if the job is still stuck.

Before you begin

A little patience prevents most of the "it is still there" frustration.

01Give it 30 seconds. Large files and network print jobs take time to leave the queue after you cancel.
02Make sure the printer is on and not showing an error or "paused" state, since a paused printer holds jobs indefinitely.
03Close the app you printed from. A crashed app can keep re-sending the same job.
04If you only need a quick fix, restarting the computer resets the queue automatically and clears most stuck jobs.

Cancel jobs on Windows

Start with the built-in queue window. This is the safe, first-line fix.

01Open Settings › Bluetooth & devices › Printers & scanners.
02Select your printer, then choose "Open print queue".
03To clear everything, open the three-dot menu (or the Printer menu) and choose "Cancel all", then confirm.
04To remove one job, right-click it and choose Cancel. Wait up to 30 seconds for the list to update.

Restart the Windows Print Spooler

If a job will not cancel, restart the Print Spooler, the Windows service that manages the queue. This is the documented fix for jobs that are truly stuck.

01Press Windows key + R, type services.msc and press Enter.
02Scroll to "Print Spooler", right-click it and choose Restart. Then re-open the queue to confirm it cleared.
03Still stuck? Right-click Print Spooler and choose Stop (leave the window open).
04Open File Explorer and go to C:\Windows\System32\spool\PRINTERS, then delete every file inside that folder (delete the files, not the folder).
05Return to Services, right-click Print Spooler and choose Start. Your queue is now empty.

How do I clear the print queue from Command Prompt?

Open Command Prompt as administrator and run three commands: stop the Print Spooler, delete the files in the spool folder and start the spooler again. It is the same fix as the Services steps above, typed as commands.

01Type cmd in the search bar, right-click Command Prompt and select "Run as administrator".
02Type net stop spooler and press Enter.
03Type del C:\Windows\System32\spool\PRINTERS\*.* /Q and press Enter. This deletes the files in the spool folder, not the folder.
04Type net start spooler and press Enter.
05Jobs still listed? Run the three commands again. A Microsoft Q&A answer notes that it sometimes takes two or three runs to delete every stuck job.

Cancel jobs on Mac

macOS lets you clear jobs directly from the print queue window (Print Center).

01Open the Apple menu › System Settings › Printers & Scanners.
02Select your printer and click "Open Print Queue" (on macOS Monterey or earlier, "Open Print Queue" under Printers & Scanners in System Preferences).
03Click the small "X" next to a job to cancel it, or press Command + A then Command + Delete to cancel all jobs at once.
04If nothing prints and the queue also will not clear, move on to resetting the printing system below.

Reset the Mac printing system

This is Apple’s last-resort fix when no other step works. It clears every stuck job, but it also removes all your printers and scanners, so you will need to add them again afterward.

01Open the Apple menu › System Settings › Printers & Scanners.
02Right-click (or Control-click) anywhere in the printer list, then choose "Reset printing system".
03Confirm, entering your Mac password if prompted. The queue and all printers are removed.
04Re-add your printer from Printers & Scanners › Add Printer once the reset finishes.

When to get help

If jobs keep getting stuck even after a spooler restart or a printing-system reset, the cause is usually outside the queue: a paused/offline printer, an outdated or corrupt driver, or a failing network connection. Update the driver from the maker’s app, confirm the printer is online, and run a guided diagnosis for a next step tailored to your model.

Frequently asked questions

How do I clear the print queue with CMD in Windows 11?

Open Command Prompt as administrator (type cmd in the search bar, right-click Command Prompt and select Run as administrator). Run net stop spooler, then del C:\Windows\System32\spool\PRINTERS\*.* /Q to delete the files in the spool folder, and finally net start spooler. Microsoft gives the same order (stop, delete, start) for Windows 11 and Windows 10 using the Services window.

How do I force delete a print queue that won’t clear?

Stop the Print Spooler, delete every file in C:\Windows\System32\spool\PRINTERS and start the service again. Microsoft points to this method when canceling jobs does not clear the queue. If Windows says you do not have access to the folder, click Continue. If the job is still there, Microsoft’s next step is to turn off the printer, wait at least 60 seconds, turn it back on and restart the PC.

Print job stuck on "Deleting": how do I remove it?

If canceling leaves a job on "Deleting", clear the queue at the service level: stop the Print Spooler, delete the files in C:\Windows\System32\spool\PRINTERS and start it again. On a shared printer, a job stuck on "Deleting" also blocks everyone else’s prints, as a Microsoft Q&A thread describes. If it is still there, restart the PC and the printer, leaving the printer off for at least 60 seconds.

Can I make a batch file to clear the print queue?

Yes. An answer on Microsoft Q&A suggests saving these three lines in a text file renamed ResetSpooler.bat: net stop Spooler, del C:\Windows\System32\spool\PRINTERS\*.* /Q and net start Spooler. Run it as administrator, since Microsoft runs these commands from an administrator Command Prompt. The same answer notes that it sometimes has to run two or three times to delete every stuck job.

PEPrinterErrors editorial teamUpdated
PrinterErrors editorial team

Last updated · Content is independent and not sponsored by any manufacturer.

Sources & methodology

Spotted something inaccurate? Report a content issue

Related guides