ERROR-A / Search

Start with a symptom, message or error code.

Explore
Menu
ProblemA job that does not print does not necessarily mean the print service stopped. It may block later jobs, wait for an offline printer or come from one problematic document. Inspect the queue and scope before cancelling it: clearing every job or reinstalling the printer removes information and can affect other users.

Print job stuck in the Windows queue

A queued document is not completing. Identify the job and printer before canceling anything or changing the printing service.

Try this first

1 quick checks · ~3 min

  1. Identify the queue, owner and first stalled jobLocate the blockage without deleting jobs or sending duplicates.

Find your situation

See all the clues. Choose the one that matches what you observe.

One job blocks the jobs behind it

The printer is available, but the queue stops at one document. Identify its owner and document first; cancellation will be targeted.

The queue waits for an unavailable printer

If it shows Offline or the device does not respond, resolve availability before clearing the queue.

It stays on Deleting or several printers fail

Check the service state instead of inferring it from queue wording. A stopped service or one that crashes again needs a different path.

Diagnostic signals

ObservationOnly one app or document gets stuck
If a different small test prints after cancelling the blockage, stop repairing every printer: narrow the problem to that document/app or its processing.

Step-by-step solutions

01

Identify the queue, owner and first stalled job

  • Estimated time: 3 min
  • Easy
  • Low risk

Locate the blockage without deleting jobs or sending duplicates.

  1. Record the first stalled job, status, owner and whether other jobs are waiting behind it. Do not send repeated copies while blocked.

    1. Settings
    2. Bluetooth & devices
    3. Printers & scanners
    4. Affected printer
    5. Open print queue

  2. Check whether the printer is powered on/available and whether this is a local queue or a shared company queue. On a shared queue, contact IT or the job owner before cancelling or restarting anything.

  3. If Offline, follow availability checks. If several printers fail or a job remains on Deleting, inspect the service. If only one job blocks an available printer, move to controlled cancellation.

Sources:
02

Resolve availability before changing the queue

  • Estimated time: 5 min
  • Easy
  • Low risk

  1. Check the printer panel for paper, a jam or a message requiring action according to its manual. If an operation is active, wait for it to finish; do not cut power to speed up a job.

  2. If Windows shows Offline, follow the related offline-printer guide. If it does not appear as a printer at all, use the detection guide. Clearing the queue does not repair the cable, network or device detection.

  3. Once available, watch whether the job resumes. If it prints, do not resend it. If still blocked with no panel error, return to cancelling that job.

Sources:
03

Inspect the service and scope of the blockage

  • Estimated time: 5 min
  • Easy
  • Low risk

  1. Open services.msc and inspect Print Spooler status without changing it. A queue saying Deleting does not prove the service is stopped.

  2. If stopped, or it stops again, use the related print-service guide with that observation. If running and several local queues fail, that guide allows evaluation of controlled recovery; do not manually delete the spool folder here.

  3. If only one printer fails while others print, narrow analysis to that queue/connection. If the queue belongs to a server or other users, give IT the queue names, time and state: restarting your local service may not fix the server and may interrupt your other queues.

Sources:
Advanced

Advanced checks

Continue if the earlier steps did not help. Read each procedure’s precautions first.

04

Cancel one authorized job and check whether it releases the queue

  • Estimated time: 10 min
  • Intermediate
  • Moderate risk
  • Data loss: Possible

  1. Confirm you still have the original file and can resend it if needed. In the queue, select only the stalled job you own or are authorized to manage and choose Cancel; do not choose to clear every document.

  2. Wait for the state to change. If it disappears and later jobs advance, the blockage was associated with that submission. If it remains on Deleting, stop repeating Cancel and follow the service check.

  3. With the queue clear, send one small page from another document/app with no sensitive information. If it prints and the original blocks again, investigate that file/app or driver with support; do not reinstall every printer. If the test also fails, preserve that result and revisit availability/service.

Sources:
Next step

Still not working?

Escalate with the affected queue, local/shared status, first job, service state and result of a different small test. If the service crashes again or a shared queue is affected, stop with IT/support. Do not repeat cancellations, reinstalls or folder cleanup when they do not change the hypothesis.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.

Related problems

peripherals
Problem

Print Spooler service is not running

Check the service that manages print jobs before changing a queue or reinstalling a printer.

View solution
peripherals
Problem

Printer shows offline

Separate USB from network printing, check whether another device prints and use queue state to choose the next step. An Offline entry does not mean Windows stopped detecting the printer.

View solution
peripherals
Problem

Printer not detected in Windows

Check whether Windows 11 finds the printer over USB or the network before installing software or changing drivers.

View solution