Microtechie
Home/Resources/Print Queue Stuck

Printing guide

Print Queue Stuck: Clearing Jobs on Windows Workstations and Print Servers

One stalled job can stop an entire queue, and on a print server that means the whole office stops printing. Clearing it is routine. Preventing it from recurring usually means dealing with the driver that caused it.

Applies toWindows 10 and 11 workstations and Windows Server print servers. Server steps require administrative access.

Step-by-step

  1. Cancel the job from the queue

    Open the printer's queue, right-click the stuck job and choose Cancel, or use Printer → Cancel All Documents. On a print server, do this in Print Management or the server's queue, not on a client computer.

  2. Restart the Print Spooler service

    If jobs remain listed as Deleting, open services.msc, locate Print Spooler and restart it. On a print server, warn users first; restarting the spooler briefly interrupts every queue on that server.

  3. Remove stranded spool files

    If jobs persist after a restart, stop the Print Spooler service, delete the files in %SystemRoot%\System32\spool\PRINTERS, and start the service again. Remove only the contents of that folder, never the folder itself. This permanently discards all pending jobs, so tell users to resend anything they need.

  4. Identify the problem driver

    If the spooler crashes or queues jam repeatedly, check the System event log for spooler errors that name a driver or printer. In Print Management, a frequently failing driver can be set to run in isolation so that it no longer takes down the whole spooler.

  5. Standardize drivers

    Mixing drivers for the same device across queues and clients is a common source of instability. Use one current, manufacturer-supplied driver version per model, and remove old drivers that are no longer in use.

Driver installation and security

Since the PrintNightmare security updates in 2021, Windows by default requires administrator rights to install printer drivers through Point and Print. Users who previously added printers themselves may now see prompts or failures. The correct response is to deploy printers and their drivers centrally, through Group Policy, Intune or your print management tool, rather than to relax this protection.

When to escalate

Escalate if the spooler on a print server crashes repeatedly, if event logs show a driver failing after updates, or if users across the office cannot add printers. These are configuration issues that should be fixed once, centrally.

Frequently asked questions

Will restarting the spooler delete everyone's print jobs?
Restarting alone usually keeps queued jobs. Deleting the spool files, as in step 3, removes them.
Why does one document keep jamming the queue?
A corrupt or unusually complex file, or a driver that can't handle it. Try printing it to PDF and printing that, or use a different driver.
Should users have admin rights to install printers?
No. Deploy printers centrally. It is more secure and saves support time.
Before you change anythingConfirm you have a current backup and, where configuration changes affect several users, schedule them outside working hours. If you'd prefer us to handle it, get in touch.

Related guides