How to Clear HP Printer Queue

A stuck print queue can freeze your entire workflow. You click Print, nothing happens, and the job sits in the queue forever—often showing “Printing,” “Error – Printing,” or “Deleting…” for minutes (or hours). This guide gives you a clean, dependable process to clear the HP printer queue, purge stuck print jobs, restart the print spooler safely, and prevent the problem from recurring—whether you’re at home with a USB HP DeskJet or running a busy office with HP LaserJet and shared print servers.

Good to know: Although the instructions are HP-focused, the queue lives on the computer or print server, not inside the printer. Fixing the computer/OS side usually solves it—even when the HP device itself is healthy.

Quick Fixes (Try These First)

1. Cancel jobs from the OS queue

   • Windows: Settings → Bluetooth & devices → Printers & scanners → select your HP printer → Open print queue → select job(s) → Cancel.

   • macOS: System Settings → Printers & Scanners → select your HP printer → Open Print Queue → select job(s) → X (Delete).

2. Power cycle the HP printer
   Turn the printer off, wait 30–60 seconds, then turn it back on. This clears internal statuses (like “busy” or “paused” states).

3. Restart the computer
   A simple restart frees locked handles to spooler files and resets client-side queues.

If these don’t work, move to the deeper steps below.

Part 1 — Clear the Queue on Windows (All Versions)

A. Standard GUI Method

1. Pause printing (optional safety step)

   • Control Panel → Devices and Printers → right-click your HP printer → See what’s printing → Printer menu → Pause Printing.

2. Cancel all documents

   • In the same window, Printer menu → Cancel All Documents → confirm.

3. Resume printing

   • Printer menu → uncheck Pause Printing.

If jobs remain stuck at “Deleting…” or “Error – Printing”, use the Spooler Reset method.

B. Spooler Reset (Reliable Fix)

This sequence fully flushes the Windows spooler.

Steps:

1. Open Command Prompt (Admin) or PowerShell (Admin).

2. Run the following commands in order:

net stop spooler
del /q /f %systemroot%\System32\spool\PRINTERS\*.*
net start spooler

• net stop spooler halts the Print Spooler service.

• The del command deletes all pending spool files.

• net start spooler restarts the service with a clean slate.

If you get “in use” errors, make sure the Print Spooler service is stopped, and that no other admin tool is open (e.g., the Print Management snap-in).

C. One-Click Cleanup (Batch File)

Create a file named ClearPrintQueue.bat with:

@echo off
echo Stopping Print Spooler...
net stop spooler >nul 2>&1
echo Deleting stale spool files...
del /q /f %systemroot%\System32\spool\PRINTERS\*.*
echo Starting Print Spooler...
net start spooler >nul 2>&1
echo Done. Print queue cleared.
pause

Right-click → Run as administrator when needed.

D. PowerShell Version (Verbose)

Write-Host "Stopping spooler..."
Stop-Service -Name Spooler -Force
Start-Sleep -Seconds 1

$spool = "$env:windir\System32\spool\PRINTERS"
Write-Host "Clearing $spool ..."
Remove-Item "$spool\*.*" -Force -ErrorAction SilentlyContinue

Write-Host "Starting spooler..."
Start-Service -Name Spooler
Write-Host "Done."

E. If It’s a Shared/Network Printer

• If you print to a shared queue on another PC or a Windows Print Server, clearing your local queue may not be enough. You must clear the queue on the server (see Part 3).

• On your client PC, remove and re-add the printer if it keeps pulling stale jobs:

  • Settings → Printers & scanners → select the HP → Remove.

  • Add device → choose the correct shared printer or TCP/IP device.

F. Common Windows Gotchas

• WSD vs TCP/IP (Raw 9100): WSD ports can be flaky. For stability, create a Standard TCP/IP Port pointing to the HP’s IP:
  Control Panel → Devices and Printers → Printer Properties → Ports → Add Port… → Standard TCP/IP Port → enter printer IP.

• Permissions: If you can’t cancel jobs, you may lack permissions on a shared queue. Ask the admin to clear it server-side.

• HP Print and Scan Doctor (Windows): This free HP tool can repair spooler issues and port problems automatically.

Part 2 — Clear the Queue on macOS

A. Standard GUI Method

1. System Settings → Printers & Scanners.

2. Select your HP printer → Open Print Queue.

3. Highlight stuck job(s) → click the X to Delete.

B. Reset the Printing System (macOS “Nuclear” Option)

This removes all printers and clears macOS printing subsystems. You’ll re-add the HP afterwards.

1. System Settings → Printers & Scanners.

2. Right-click (or Control-click) in the printers list → Reset printing system… → confirm.

3. Click Add Printer, Scanner, or Fax… → re-add your HP (AirPrint/IP/HP driver).

Use this when you have persistent corruption or endless “Paused” states you can’t clear.

C. Clear CUPS Jobs (Advanced)

macOS uses CUPS under the hood.

• Open a browser and go to http://localhost:631 (enable CUPS web interface if needed).

• Printers → select your HP → Jobs → cancel/remove.

• Or use Terminal:

  cancel -a
  

  This cancels all jobs for the current user. For all printers:

  cancel -a -
  

D. Re-Add via IP for Stability

If AirPrint/WSD is unreliable, add the printer via IP:

• System Settings → Printers & Scanners → Add → IP tab → enter HP’s IP → Protocol: Line Printer Daemon – LPD or HP Jetdirect – Socket → Add.

Part 3 — Clearing Queues on Print Servers (Windows & Linux)

A. Windows Print Server (Print Management MMC)

1. On the server, open Print Management (or run printmanagement.msc).

2. Navigate to Print Servers → [ServerName] → Printers → right-click the HP queue → Open Printer.

3. Printer menu → Pause Printing.

4. Cancel All Documents (confirm).

5. On the server, stop/start the spooler service to flush any stuck files:

   net stop spooler
   del /q /f %systemroot%\System32\spool\PRINTERS\*.*
   net start spooler
   

6. Resume Printing and test.

If the queue repopulates immediately with garbage jobs, a client may be resubmitting. Identify the source via See what’s printing → Document column → Owner.

B. Linux/CUPS Server

• List jobs:

  lpq -P 
  

• Cancel all jobs in a queue:

  cancel -a 
  

• Restart CUPS:

  sudo systemctl restart cups
  

• Clear spool directory if needed (careful):

  sudo rm -f /var/spool/cups/* 
  sudo systemctl restart cups
  

Part 4 — Mobile (iOS/iPadOS/Android/ChromeOS)

A. iOS / iPadOS (AirPrint)

1. Double-tap App Switcher → go back to the app that printed.

2. Open the Print Center (it appears as a print icon in App Switcher while a job is active).

3. Tap the job → Cancel Printing.
   If you can’t see it, the job may have already left the device; clear it on the printer/PC instead.

B. Android (HP Smart / System Print)

• Open HP Smart → Print History/Queue if available → cancel.

• Or go to Settings → Connected devices → Printing → Default Print Service / HP Print Service Plugin → Printing history/queued jobs and cancel.

• If the job is already at a PC/server queue, cancel there.

C. ChromeOS

• Settings → Advanced → Printing → Print Jobs → cancel.

• If printing via a network queue or server, clear it on that host.

Part 5 — Why Print Queues Get Stuck (And How to Prevent It)

Common causes:

• Corrupt spool files (partial downloads, app crashes during print).

• Network hiccups (Wi-Fi drops) between PC and HP printer.

• Driver/PDL mismatch (e.g., printing complex PDFs via the wrong driver).

• Overloaded spoolers (huge jobs, many concurrent users).

• WSD port glitches (Windows Web Services for Devices).

• Firmware bugs or very old drivers.

• Permissions issues on shared queues.

Prevention tips:

• Prefer Standard TCP/IP (Raw 9100) over WSD on Windows for stability.

• Keep HP firmware and drivers current (use HP Smart or HP’s support site).

• For complex PDFs, try the HP PCL6 (UPD) driver for speed/stability, or PostScript for fidelity—test both.

• Avoid sending enormous image-heavy jobs at ultra-high DPI.

• On print servers, limit job sizes and set sensible timeouts.

• Educate users to cancel duplicate clicks when an app “hangs”—those extra commands create job storms.

Part 6 — Extra Troubleshooting (When the Queue Keeps Re-Sticking)

1. Remove & Re-Add the Printer
   Stale ports or drivers often cause repeated sticking. Remove the queue completely and add it back (via TCP/IP).

2. Change Print Processor (Windows)
   Printer Properties → Advanced → Print Processor → choose WinPrint; Data type: RAW.

3. Bypass the Spooler (Test Only)
   Properties → Advanced → select Print directly to the printer.
   If this works, the spooler or port is the culprit. Switch back after testing to allow sharing.

4. Event Viewer Diagnostics
   Check Applications and Services Logs → Microsoft → Windows → PrintService for errors.

5. Permissions on Server Queues
   If jobs from a specific user always stick, review queue permissions. On Windows print servers, grant Manage Documents to helpdesk/ops.

6. Driver Isolation (Server)
   In Print Management, set driver isolation to Isolated for flaky third-party drivers to prevent spooler crashes.

7. Antivirus Exclusions
   Real-time scanning of spool directory can lock files. Add exclusions for %systemroot%\System32\spool\PRINTERS on servers (per security policy).

8. Firmware & Memory (Enterprise HP)
   Massive graphics jobs can exceed device memory. Update firmware, add memory (if supported), or change driver to host-based rendering.

Part 7 — Final “Clean Slate” Recipes

Recipe A: Home Windows PC + HP DeskJet/ENVY (USB or Wi-Fi)

1. Cancel jobs from the queue window.

2. Run the spooler reset commands.

3. Power cycle the HP printer.

4. Print a simple text page (Notepad).

5. If the issue returns, remove and re-add the printer via TCP/IP (if networked).

Recipe B: macOS + HP OfficeJet

1. Delete jobs in Open Print Queue.

2. If stuck persists, Reset printing system.

3. Re-add the printer (prefer IP if AirPrint is unreliable).

4. Test with a small PDF and a plain text page.

Recipe C: Windows Domain + HP LaserJet on Print Server

1. On the server, Pause Printing and Cancel All Documents.

2. Stop spooler, clear PRINTERS folder, start spooler.

3. Confirm driver isolation and correct port (TCP/IP).

4. Resume printing; monitor Event Viewer.

Part 8 — Final Checklist

• Canceled jobs at the OS queue.

•  Restarted HP printer and PC.

•  Ran spooler reset (Windows) or Reset printing system (macOS) if needed.

•  Verified port type (TCP/IP Raw 9100 preferred on Windows).

•  Re-added the printer after cleanup.

•  Tested with small text/PDF; confirmed new jobs flow.

•  (Server) Cleared queue on the server, not just clients.

•  Updated HP firmware/driver; considered HP Print and Scan Doctor (Windows).

•  Noted any recurring causes (large files, Wi-Fi stability, specific app).

10 Frequently Asked Questions (FAQs)

1) My job shows “Deleting…” forever. What should I do?
Stop the Print Spooler, delete files in %systemroot%\System32\spool\PRINTERS, then start the spooler again. This clears the stuck state. If it’s a shared printer, perform the same steps on the print server.

2) Do I need to clear the queue on the HP printer itself?
Usually no—the queue you see on Windows/macOS is local or server-side. Power cycling the HP helps, but purging the OS spooler is the key step.

3) Why do my HP print jobs keep getting stuck after I clear them?
Common reasons include WSD ports, old drivers, network hiccups, or corrupt files. Switch to a Standard TCP/IP port, update drivers/firmware, and avoid printing huge, complex documents without optimization.

4) Is there a quick script I can use on Windows?
Yes—use the batch file in this guide (ClearPrintQueue.bat) or the PowerShell snippet to stop the spooler, delete spool files, and restart the service in one go.

5) On macOS, what does “Reset printing system” actually do?
It removes all printers, deletes pending jobs, and resets the macOS printing subsystem. You’ll re-add your HP afterwards. It’s the cleanest fix for persistent macOS queue issues.

6) I print through a company server. Do I still clear my local queue?
You should clear local and server queues if necessary. If the server queue is stuck, only clearing your local queue won’t help—ask IT (or, if you’re the admin) to purge it on the server.

7) Does using AirPrint (macOS/iOS) affect queue stability?
AirPrint is convenient but can be sensitive to network conditions. If jobs frequently stall, add your HP via IP on macOS (JetDirect/LPD) and test stability.

8) How do I prevent queues from jamming in the future?
Use TCP/IP ports, keep HP firmware/drivers updated, avoid sending massive unoptimized files, and consider driver isolation on Windows servers. For Wi-Fi printers, ensure strong signal or use Ethernet.

9) Can antivirus cause stuck queues?
Yes. Real-time scanning of the spool folder can lock files. If policy allows, add the spool directory to AV exclusions on servers and test again.

10) After clearing the queue, my HP still won’t print. What else can I try?
Remove and re-add the printer, verify the correct driver (HP UPD PCL6 or model-specific), try a different port (TCP/IP), run HP Print and Scan Doctor (Windows), and confirm the printer is Ready/Online with a valid IP address. If nothing helps, check Event Viewer (Windows) or CUPS logs (macOS/Linux) for deeper clues.