Designed for Enterprise IT Support & Corporate Environments

Printers

Windows Printer Job Stuck in Queue

Use this guide when print jobs remain in queue and block new jobs. It starts with user-safe actions, then moves to spooler reset steps that generally require local admin rights or remote support tooling.

Severity: MediumAdmin Required
Estimated Fix Time

10-20 min

Access Level

Admin Required

Total Steps

6

Author & Verification

Tamem J

IT Solutions Engineer

Last verified: March 3, 2026

Runbooks and troubleshooting guides are reviewed for enterprise-safe usage and avoid security bypass patterns.

Tested on Windows 11 23H2Tested on Windows 10 22H2

Trust Signals

No ratings yet

0 total helpfulness votes

  • Enterprise Microsoft 365 Administration
  • Endpoint Management (Intune, Jamf, Kandji)
  • Identity & Access (Entra ID, Okta)
#windows#printer#spooler#queue#printing

Note: “Download as PDF” opens the browser print dialog. Choose “Save as PDF” for a printable runbook copy.

Step-by-Step Resolution

Expand each section as needed

  1. 1

    Confirm printer scope and connection type

    Info

    Recommended validation or troubleshooting step

    Check whether the issue affects one user, one workstation, or all users on the same printer. Note whether the printer is USB, network IP, or print-server mapped, because remediation differs.

  2. 2

    Attempt user-safe queue cleanup first

    Info

    Recommended validation or troubleshooting step

    Open Printers & scanners, open the print queue, and cancel pending jobs. If one document is corrupted, removing that single job may restore printing without service restart.

  3. 3

    Restart the print spooler service (admin step)

    Command

    Includes a copyable command block

    Command
    # Windows (PowerShell - Run as Administrator)
    Restart-Service Spooler -Force
  4. 4

    Clear stuck spool files if service restart is insufficient

    Command

    Includes a copyable command block

    Command
    # Windows (PowerShell - Run as Administrator)
    Stop-Service Spooler -Force
    Remove-Item "$env:SystemRoot\System32\spool\PRINTERS\*" -Force -ErrorAction SilentlyContinue
    Start-Service Spooler
  5. 5

    Re-test with a simple document

    Info

    Recommended validation or troubleshooting step

    Print a small text document first. If it prints successfully but larger documents fail, check printer memory limits, driver type, and document rendering settings.

  6. 6

    Escalate for driver or print server incidents

    Warning

    Review carefully before proceeding

    Escalate to desktop engineering or print services if multiple users are affected, if jobs fail only on one print server queue, or if a recent driver rollout introduced the issue. Do not install unsigned printer drivers or disable endpoint controls.

Related Fixes by Exact Query

High-intent troubleshooting phrases mapped to related internal guides.