Print queue stuck? Watch what Cancel does

1. Cancel from the queue, and watch what it does

Start here because it is both the fix for the simplest case and the test that identifies the others. Open Start, then Settings, then Bluetooth & devices, then Printers & scanners on Windows 11 — on Windows 10 the same place is Start, Settings, Devices, Printers & scanners. Select the printer, open its print queue, then right-click each print job and select Cancel.

If the jobs vanish, the problem was the documents rather than the system, and you can print again. A single malformed document — often a complex PDF, a page with an enormous embedded image, or something produced by an application that has since crashed — is enough to block everything behind it, because the queue is processed in order.

If the job changes its status to something like “Deleting” and then stays there indefinitely, that is the informative outcome. It means the spooler has accepted your instruction and cannot carry it out, which points at the service rather than the document, and section 2 is your next step.

And if the whole application freezes when you press Ctrl + P, or the queue window itself will not open, stop cancelling. That pattern means the spooler service is not running, which Microsoft lists among its symptoms alongside printing suddenly stopping and jobs freezing. Go to section 3.

2. Restarting the Print Spooler service

The Print Spooler manages all print jobs in Windows, and restarting it clears whatever state it has got itself into. Press Windows key + R, type services.msc and press Enter. Scroll to Print Spooler in the list, right-click it, and select Restart.

Microsoft describes this as resolving temporary issues with printer recognition, which undersells it slightly — restarting the service also abandons whatever job it was stuck trying to process, which is usually the point. Jobs that were genuinely queued will normally resume; the one that was jammed generally will not, and that is the outcome you want.

Go back to the queue afterwards and check. If it is empty, print something small as a test rather than re-sending the large document that caused the problem, so that a second failure tells you something.

If the queue is still populated after a restart, the spooler cannot clear its own backlog because the files on disk are the problem rather than the service’s memory. That is what section 4 addresses, and it is the point at which most people who have been fighting this for an hour finally get somewhere.

3. When the spooler is not running at all

This is a different fault that produces a similar complaint. Microsoft lists its symptoms as printing suddenly stopping, jobs freezing or applications hanging when you press Ctrl + P, and documents staying stuck in the queue while the printer becomes unresponsive. The application freeze is the giveaway: an application waiting for a service that is not there will hang rather than show an error.

Open services.msc the same way and look at Print Spooler’s status column before doing anything. If it is blank rather than showing as running, the service has stopped. Right-click and choose Start.

A spooler that stops on its own has a reason, and the usual one is a printer driver crashing the service as it loads. That is why Microsoft’s own sequence for this puts driver work between clearing the queue and restarting the service — the service will simply stop again next time if the driver that killed it is still installed.

If it starts and then stops again within a minute or two, treat it as a driver problem rather than a service problem and go to section 5.

A spooler that will not stay started is almost always a driver crashing it. Restarting the service repeatedly will not change that.

4. Deleting the spool files by hand

Every queued job exists as a file on disk, and when one of those files is corrupt the spooler will fail on it every time it starts — which is exactly why the queue survives a restart. Deleting them clears the backlog completely. The order matters, and skipping the first step is the usual mistake.

Stop the service first. In services.msc, right-click Print Spooler and choose Stop. Deleting the files while the service is running will not work, because the spooler holds them open.

Then open File Explorer and go to C:\Windows\System32\spool\PRINTERS, and delete all the files in that folder. You can also reach it by entering %WINDIR%\system32\spool\printers in the taskbar search box. The folder holds only queued jobs, so deleting its contents loses nothing except the documents currently waiting — which are the ones you are trying to get rid of.

Then start the service again: right-click Print Spooler and choose Start. Microsoft’s fuller version of this procedure also has you confirm the startup type is set to Automatic while you are in the service’s properties, which is worth doing if the spooler has been stopping on its own.

5. The driver, and why one document can jam everything

If the queue clears but printing still does not happen, or the spooler keeps stopping, the driver is the remaining suspect. Microsoft’s spooler article puts driver work in the middle of its sequence for this reason: open Device Manager, expand the printer entries, uninstall the problematic driver, and install the manufacturer’s current one.

The manufacturer’s driver matters more than it sounds. Windows will happily install a generic driver that works for simple documents and fails on particular features — duplex, certain paper sizes, or transparency in a graphic — which produces the maddening pattern where most things print and one document jams the queue every time.

That pattern is worth testing for deliberately. If the same document always jams and everything else prints, the document is exercising something the driver handles badly. Printing it to PDF and then printing the PDF is a quick way to sidestep it, and it confirms the diagnosis at the same time.

Microsoft’s last general step is a hardware one: turn the printer off, wait at least 60 seconds, turn it back on, then restart the PC and try again. The 60 seconds is not superstition — it gives the printer’s own memory time to clear, and printers hold a queue internally as well.

6. When it keeps coming back

A queue that jams once is a bad document. A queue that jams every few days is a pattern, and the useful work is identifying it rather than clearing the queue faster each time.

Record what the jammed job was each time it happens: which application sent it, what kind of document, and whether anything unusual was in it. Three occurrences is normally enough to see whether it follows one application, one document type, or one printer feature. If it follows an application, that application’s print path is at fault and updating it is more productive than anything done to Windows.

Check the startup type while you are in the service properties. A spooler set to anything other than Automatic will not come back after a restart, which presents as printing working until the first reboot and then not.

If the queue jams across several machines printing to the same printer, stop looking at Windows. That points at the printer or the print server, and the fix belongs there — at which point the printer’s own status, rather than the queue, is the thing to investigate.

Frequently asked questions

Sources and review notes

Checked on September 24, 2026. Compiled by Glitchary from Microsoft’s articles on fixing print jobs stuck in the queue and on Print Spooler service errors. The menu paths, the services.msc procedure, the spool folder location, the 60-second power cycle and the listed spooler symptoms are Microsoft’s. The use of the Cancel response as a diagnostic, the reasoning about why one document jams a queue, and the guidance on recurring jams are editorial. Menu locations differ between Windows 10 and 11 and between builds — check Microsoft’s current article if yours does not match. Glitchary is independent of Microsoft.

• Microsoft: fix print job stuck in queue errors in Windows
• Microsoft: fix print spooler service not running errors in Windows