IT Support Playbooks / IT Support Guides
Investigate a stuck print job without clearing every queue
A user may be unable to print because one job blocks a queue, the device is offline or the driver fails. Inspect that queue before restarting a shared spooler.
Environment and inputs: Everyday IT support · Windows PowerShell examples unless specified
Try the diagnostic command
Use the stated shell and platform. Replace sample domains, addresses, services and paths with values from the system you are authorized to support.
Get-PrintJob -PrinterName 'Office Printer'How to read the result
The command lists jobs visible in the named Windows queue. Replace the display name with the affected printer and compare job status and submission time with the user's report.
What to do next
Check the printer display, paper state and network connection, then coordinate any job cancellation with its owner. Print a small test only after the blocking condition is understood.
Before you make a change
Restarting the spooler or clearing spool files can interrupt other users and discard pending work. Do not treat a queue-wide reset as the first diagnostic step.