Handle a Stuck Print Job Without Creating a Stack of Duplicates
Repeatedly clicking Print while a job is stuck can create several copies waiting behind the first one. If the queue later recovers, they may all print. Stop submitting new jobs and inspect the existing queue before trying again.
In Windows 11, open Settings, Bluetooth & devices, Printers & scanners. Select the exact printer and open its print queue. Check the document names, owners and status. At a shared printer, coordinate with colleagues before cancelling work that is not yours.
Reconcile the queue and the paper
Look at the printer itself. It may be waiting for paper, a particular tray or an intervention shown on its display. Note whether some pages already printed. Cancelling a queued document does not pull back pages already produced, so keep those pages together and protect any confidential information.
For an unwanted or stuck job you own, use its Cancel action. Allow the queue to update. If you submitted duplicates, remove the extra copies deliberately rather than clearing an unfamiliar shared queue without checking.
Save the original document before closing its application. A print job is an output request, not your working source file, but you still need the source available for a controlled retry.
Retry with a small test
Once the queue is clear and the printer reports ready, submit one short, non-sensitive page. Watch whether it enters and leaves the queue and confirm physical output. Then print only the pages still needed from the real document, checking page ranges to avoid repeating an already printed section.
If cancellation remains stuck or several applications cannot print, record the queue state and printer connection type. A spooler, driver or communication problem may need further investigation. On a shared business system, let its administrator coordinate service changes because they can affect other users.
Do not jump to deleting spool directories or removing printer packages merely because one job paused. The useful first result is knowing whether the blockage follows a document, one PC or the shared printing path.
Reference: Microsoft Support.