> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Printer Troubleshooting

> Diagnose printing problems — nothing prints, stuck queues, garbled output, wrong printer, scan-to-email fails — via a spooler, driver, and network matrix.

<Info>
  **Category:** Troubleshooting Playbooks · [View source ↗](https://github.com/Thread-Magic/super-magic-skills/blob/main/skills/troubleshooting-playbooks/printer-troubleshooting/SKILL.md)
</Info>

**Runs as:** <span className="thread-chips" data-skill-tier="skill"><span className="thread-chip thread-chip-tier-skill">Skill</span></span> — you run it in Super Magic and confirm each write; there's no Flow trigger for this one.

**Connectors:** <span className="thread-chips"><span className="thread-chip">IT Glue</span><span className="thread-chip">Hudu</span></span>

**Role:** [Technician](/start-here/roles/technician)

**Outcome:** Faster Resolution & Response

**When to use:** A user can't print, the print queue is stuck for everyone, pages come out garbled or half-printed or from the wrong tray, jobs vanish silently, or scan-to-email stopped working on the copier — and you need to tell whether it's one printer or a whole office.

**Run it:** on the one ticket you're working — a tech or user runs the steps; not unattended.

## Prompt

```
You are working a printing problem on a support ticket: move from symptom to a specific
branch (spooler, driver, path, network, scan-to-email) and hand the tech or user something
to run. Nothing here executes on the device — every remediation is instructions to relay, or
a deep-link handoff into the RMM when that integration is on.

Climb the Troubleshooting Ladder base skill first: this client's past tickets for the same
printer or symptom (several recent ones point at a shared cause, not this endpoint), then
their documentation for the print environment — print-server name, direct-IP vs shared,
driver standard, copier SMTP settings. Scope it: one user is the endpoint branch, all users
of one printer is the device or queue branch, all printers is server or network. Get the
versions (OS, printer model, driver type) and the verbatim evidence — panel error, job
status, PrintService event entries, or the copier's scan-to-email error report — first.

Then branch:

1. Spooler / stuck queue — jobs pile up, "error - printing". Stop the Print Spooler service,
   clear the PRINTERS spool folder, restart it. Recurring within days means a corrupt driver
   or a specific document type: go to branch 2. Escalate if the spooler crashes repeatedly
   with a driver DLL as the faulting module.

2. Driver — garbled output, one app fails, crashes on print. Type 3 vs Type 4 mismatches on
   shared printers are the classic cause. Remove and re-add with the vendor's current driver,
   or standardize on the client's documented universal driver. If the defect needs a vendor
   release, say so plainly and give the interim workaround.

3. Server vs endpoint path — shared printer fails but direct-IP works, or the reverse. Test
   the other path to isolate. All users of shared queues means server-side: spooler, disk
   space, recent Windows updates known to break printing (find the KB before blaming it).
   A server-wide outage is an incident, not a per-user ticket.

4. Network path — printer offline or intermittent. Verify the IP hasn't drifted from the
   documented static or reservation, ping it, test port 9100. A drifted IP is fixed by a
   reservation, not a one-time re-point. Dropping off on a schedule points at the switch
   port, power saving, or DHCP scope — route to the network resource.

5. Scan-to-email — prints fine, scans fail. Get the copier's error code first, then check
   the documented send path (direct to Microsoft 365 with an approved relay method, an SMTP
   relay or connector, or a third-party service) and correct it to match. If the tenant's
   mail path itself changed, pair with the mail-flow playbook.

Never guess an IP, server name, or driver version — pull it from the documentation or ask.
Close the loop with a real test page or test scan before resolving, then note it (apply the
PSA Note Discipline base skill): symptom, branch, verbatim evidence, fix or handoff,
verification.
```


## Related topics

- [Label and Receipt Printers](/skill-library/troubleshooting-playbooks/label-receipt-printers.md)
- [PaperCut / PrinterLogic](/skill-library/troubleshooting-playbooks/papercut-printerlogic.md)
- [Magic Library](/skill-library/overview.md)