Printer installed but jobs stay in queue

MSP Toolkit
Practical troubleshooting paths for MSP technicians dealing with real-world support failures.
Submitted by Anonymous (not verified) on

Field Summary

A stuck print queue is usually a queue, port, spooler, driver, permission, or device-state problem. The goal is to prove whether Windows can render the job and whether the printer can receive it before deleting printers or replacing drivers.

Common Symptoms

  • Jobs remain in Printing, Error, or Paused state.
  • One workstation fails while others print.
  • Printer shows offline even though it pings.
  • Jobs disappear from Windows but never emerge from the printer.
  • Scan-to-email works while printing fails, or the reverse.

Fast Triage

  1. Check printer panel for paper, toner, jam, sleep, or manual intervention.
  2. Ping the printer IP and confirm it matches the configured port.
  3. Check queue pause/offline state and oldest stuck job.
  4. Identify WSD versus Standard TCP/IP port.
  5. Print a Windows test page.
  6. Separate printing from scan-to-email; they use different paths.

Likely Causes

  • Stuck spooler job blocks later jobs.
  • WSD port drifted after DHCP/IP change.
  • Wrong or corrupted driver.
  • Print server queue or permissions problem.
  • Printer hardware/manual-intervention state.
  • DHCP reservation or DNS hostname mismatch.

Useful Commands

Get-Printer
Get-PrinterPort
Get-PrintJob
Remove-PrintJob -PrinterName "Printer Name" -ID 1
net stop spooler
net start spooler

Tier 1 Fix Path

  1. Cancel the oldest stuck job and resume the queue.
  2. Restart the Print Spooler if local jobs are jammed.
  3. Create a Standard TCP/IP port when WSD is the likely failure and IP is stable.
  4. Use the approved vendor/class driver for that client.
  5. Avoid removing shared printers until print-server impact is understood.

Tier 2 / Admin Investigation

  1. Review PrintService logs in Event Viewer.
  2. Check print server queue, driver package, permissions, and branch office path.
  3. Compare Get-Printer and Get-PrinterPort output against a working workstation.
  4. Check DHCP reservation, printer web UI, and vendor utility.
  5. Confirm whether GPO or RMM redeploys the old queue after cleanup.

Advanced Remediation

Driver package cleanup, spool folder cleanup, and print server driver replacement are heavier actions. Use them when the queue/port/spooler evidence points there, and schedule server-side changes if many users depend on the queue.

Verification

  • Windows test page prints.
  • User app prints successfully.
  • Queue clears after each job.
  • Printer remains online after reboot or policy refresh.
  • No duplicate WSD/old queues return.

Ticket Notes to Capture

  • Printer name/IP, workstation, queue state, port type, driver, affected users, spooler action, test page result, server/client path, fix, verification.

Escalate When

  • All users fail through a print server.
  • Driver replacement affects many users.
  • Printer panel reports hardware/vendor error.
  • GPO/RMM keeps redeploying broken queue settings.

Prevention

Use documented printer IP reservations, Standard TCP/IP ports where possible, approved drivers, and a print test procedure that separates printer hardware from Windows queue state.

Subjects
Endpoints
Printers & Peripherals