My printer won't print

Start here if you're not sure where the problem is. A print job moves through four links in a fixed order: an application sends it, the operating system's print spooler queues it, a connection (USB cable or Wi-Fi) carries it, and the printer turns it into paper. When a printer “won't print,” one of those links is broken — and the whole job is to find which one without changing everything at once. That's why this series works in a set order rather than a random list of fixes: each step either solves it or rules a link out in a minute or two.

The move that does most of the separating work is the panel test page — print a test page from the printer's own control panel, with no computer involved. If the panel prints, the printer is healthy and the fault is on the computer's side (the driver, the queue, or the connection — parts 5, 6 and 9). If the panel fails too, the fault is in the printer itself (power, paper, ink, or a hardware error — parts 2 and 3). Everything else on this page is a closer look at one of those links, and the diagnostic tree above runs this exact split for you before you read a word of the parts.

How to use the series: if you're in a hurry, work the tree, then jump to the one part that matches. If you want to actually understand what's happening, read parts 2 through 9 in order — by part 9 you'll have checked power, supplies, offline status, the queue, the driver, and both connection types, which is the entire software-and-connection side of the problem. Part 10 is where you stop guessing and either fix the last software layer or hand the machine to someone with the right tools. There's also a full checklist that condenses the whole ladder into twelve ticks you can work through with a pen.

The least glamorous part, and the one that clears a surprising share of “it won't print” reports. Check three things physically. Power: is the printer actually on, and not asleep? Some printers sleep so deeply they look dead — press the power or any button to wake it, and if it's on a switch or a power strip, make sure that's on. Connection: for USB, is the cable firmly seated at both ends and in a port you know works; for Wi-Fi, is the printer's network light steady (a steady light usually means connected, a blinking one means working or not connected — this varies by model, so trust your model's manual). Status: read the panel. A solid green/white light usually means ready; an amber, orange, or red light, or a flashing one, means the printer is telling you something, and that message is your next clue — note it, because it often points straight at the fix.

Manufacturer status lights mean different things on different models, so don't read a specific colour as universal — use the table as a guide and confirm against your printer's manual. When a status light is lit, the fastest move is to read the panel's message (or the code, covered in the error-code guide) before touching the computer at all, because a printer with an error light on will usually refuse jobs regardless of what you do on the PC. If the power and status checks are clean, the next two parts — paper, ink and toner and offline status — are where most of the rest of the problem lives.

A printer needs three physical things to make a page: paper it can feed, a supply of ink or toner, and a clear path for both. Work them in that order. Paper: is there paper in the tray the job is actually using, is it loaded so the feed sensor sees it, and do the width guides sit against the stack without squeezing it (too tight can stop the feed, too loose can feed two sheets or a crooked one)? Match the loaded paper to the size the job is set to print — a letter-size job with A4 loaded is a classic “it jams or won't feed” cause. Ink and toner: are the cartridges installed and fully seated, and do the levels show anything left? On an inkjet, also check that a brand-new cartridge has had its protective tape or plastic tab removed — that single forgotten tab is a top cause of a printer that powers on, accepts a job, and produces nothing. Path: is anything obvious blocking the paper path or left in an open door?

If the panel shows a supply or paper error, follow the on-screen instruction exactly — printers are good at telling you which tray or which cartridge, and the message is more reliable than guessing. Refilled or third-party cartridges sometimes read as empty or “unrecognized” even with plenty left, which is covered in can't detect ink or toner; if a new genuine cartridge still gives you blank or banded pages, the printhead is the suspect and blank pages and streaks or lines are where to go. Once paper and supply are confirmed, the problem is almost certainly on the connection or the computer side, which is the next part of the ladder: offline status.

First, the meaning, because it's often misread: “offline” does not mean the printer is powered off. It means the computer believes it can't reach the printer, so it holds jobs instead of sending them. The printer can be perfectly healthy, plugged in, and on Wi-Fi, and still show as offline on the PC for a software reason. That distinction matters, because the fix is usually on the computer or the connection, not the machine. The most common specific causes, in rough order: a “use printer offline” / “keep printer offline” option that got switched on in the driver's settings; the connection genuinely dropping (USB unplugged, Wi-Fi lost); or the print spooler wedged so it can't hand jobs over.

The sequence. Clear the offline state: open the printer's queue, and if there's an option like “Use Printer Offline” or the printer is marked offline, clear it (in Windows, Printer → “Resume printing” / uncheck offline under the Printer menu; in macOS, open Print Center and make sure it isn't paused and shows as available). Confirm the connection: USB is seated, or — for Wi-Fi — the printer is actually on the same network (see Wi-Fi connection problems if it isn't). Restart the spooler on Windows if the status won't clear (part of the spooler guide). What to expect: a stale offline flag clears in seconds and printing resumes; if it keeps coming back, that's a recurring drop, and keeps going offline is the next read — usually a changing network address.

Here's the mechanic that makes a queue problem feel much bigger than it is: printers process jobs in order, so a single job that fails partway through (a bad file, a sudden offline moment, a mid-job error) stops at the head of the line and holds up everything queued behind it. The printer isn't “broken” — it's waiting on a job it can't finish. The whole fix is usually to get that bad job out of the way. Open the print queue (Windows: open the printer from Settings → Printers, or double-click it in the Printers window; macOS: the Print Center / print queue icon), and you'll typically see one job marked as “error,” “failed,” or stuck “printing” with the rest waiting behind it.

The sequence. Cancel the stuck job (and anything behind it, if it's a mess) from the queue. If a job refuses to cancel, that's its own problem — printer won't cancel a document. Restart the spooler on Windows if the queue is truly wedged and won't accept a cancel — the spooler guide has the exact steps and a command chip. On macOS, the Print Center does the same job; lpstat -o in Terminal lists the queue and cancel -a clears all jobs if the GUI is unhelpful. Then send a fresh, simple test page. What to expect: once the bad job is gone, the queue usually clears and normal printing returns immediately. If the queue immediately wedges again on the next job, the cause is the job's source (a specific app or file) or the spooler itself, so follow the link above.

The driver is the translator between your computer's “print this” and the printer's own language. When it's missing, mismatched to your operating system, or corrupted, the result is usually “no print,” a job that vanishes into the queue, or output that's garbled or in the wrong layout — even though the printer and the connection are fine. The sign that the driver is the suspect is a healthy connection and a clean queue that still won't produce a page, or a printer that prints but not the way it should. The one rule that keeps this safe: get the driver from the manufacturer's own support page for your exact model and operating system (or let the OS install it), not from a third-party “driver updater,” which is a well-known source of new problems.

The sequence. Update first: on the manufacturer's page, download and run the current driver for your OS; on Windows, Settings → Printers → “Add printer” will often fetch the right one automatically, and an OS update sometimes installs it for you. Reinstall if updating doesn't help: remove the printer from the system (this removes the old driver entry), reboot, and add it again — the remove-and-re-add cycle clears a corrupt driver state better than any amount of clicking “update.” Check the OS is current: a printer that behaves oddly right after an OS change sometimes wants a driver refresh, which is the overlap with driver installation problems. One honest note on manufacturer “printer software” suites: they add features (scanning, maintenance tools) but also a lot of extra programs — for a printer that simply won't print, the core driver is usually all you need, so you can skip the full bundle if you just want it working again.

The whole of a network printing problem reduces to one rule: the printer and the device must be on the same network, and the device must be able to reach the printer's current address. Most “my wireless printer won't connect” reports are a version of that rule being quietly broken — the printer dropped off Wi-Fi, the device is on a different network (a guest network, a hotspot, a work VPN that splits traffic), or the printer's address changed and the device is still calling the old one. The printer's own Wi-Fi light is your first tell: steady usually means connected, blinking usually means not (again, this varies by model — trust the manual).

The sequence. Reconnect the printer to Wi-Fi using its setup flow (usually a button on the printer plus the manufacturer's app, or a WPS button on the router) — a clean reconnect fixes a dropped connection. Confirm same network and band: the device and the printer on the same SSID; note that many printers only join the 2.4 GHz band, so if your router combines bands, make sure the printer actually landed on one the device can reach. Stabilise the address: if it keeps breaking, reserve the printer's IP in the router (or set it static), which is the subject of IP & network configuration. The branches off this part: not found on Wi-Fi, connects but can't print, and keeps going offline each take one of these failure shapes further. If you're printing over a cable instead, the parallel guide is USB connection problems.

USB is the simplest connection and usually the most reliable, which makes a USB failure easy to reason about: it's a physical path between two ports, and it fails in a short list of ways. A loose or failed cable, a port that's dead or powered differently than you expect (front-panel and hub ports are weaker than the ports at the back of a desktop), or the computer simply not re-detecting the printer after a change. The good news is that a USB printer doesn't involve a network at all, so you can rule the entire Wi-Fi half of this page out of the question — if it's on a cable, the fault is the cable, a port, or the computer's detection of it.

The sequence. Re-seat the cable at both ends, and try a different cable if you have one (USB printer cables are data cables, and a charge-style or frayed one is a real failure point). Try a different port — a rear port on a desktop, or a different USB port on a laptop; avoid powered hubs and long extension cables for the test. Remove and re-add the printer on the computer so it re-detects the device fresh, which clears a stale connection entry. If a USB printer that worked starts failing after a driver change, the overlap is driver and software. And the honest trade-off to note: USB ties the printer to one machine at a fixed distance — if you're sharing it across the house or hitting cable-length limits, that's the point where a Wi-Fi connection becomes the better fix, not a bigger cable.

This is the computer-side home for the settings that decide whether a job ever leaves the machine, and it's where “the panel prints but the computer won't” lands. The two systems do the same job with different menus, so here's each. Windows: Settings → Bluetooth & devices → Printers & scanners is where you see the installed printers, add a missing one, and set the default; the classic “Printers and Faxes” / Print Management console (reachable with control printers) has the per-printer queue, the offline toggle, and the driver properties. Windows also ships a built-in printer troubleshooter under the same Settings area — it's automated and low-risk, worth one run. macOS: System Settings (or System Preferences on older versions) → Printers & Scanners is the equivalent; the “+” button adds a printer by name over Wi-Fi, USB, or the local network, and the default printer is chosen from the default-printer menu. Note the version naming difference — the controls are the same, the window's name changed.

Use this part as the hub for three common computer-side jobs. Add a missing printer: if it's not in the list at all, add it (USB is usually detected automatically; Wi-Fi you select by name) — a detection failure here overlaps with driver installation problems. Set the default: if jobs keep going to the wrong printer, that's the default printer — and on Windows, an option called “Let Windows manage my default printer” can keep changing it, which you may want to turn off. Run the OS troubleshooter (Windows) as a safe automated pass before deeper driver work. If, after the printer is correctly installed and selected on the computer, it still won't print while the panel works, the remaining computer-side suspects are the spooler and the driver — and if everything on this side is clean, part 10 is where the machine's own hardware gets considered.

You've reached this part with the connection, the queue, the driver, and the OS settings all checked — which means the remaining possibilities are fewer and more specific. Three of them. A firmware problem: the printer's own software can be out of date (a known bug) or, worse, mid-update and stuck — that's firmware & update problems. A hardware error the panel is reporting: a code that the manufacturer lists as a maintenance or service item — that's the error-code guide, and it's the fastest route to knowing whether it's a part or a procedure. A genuinely failing component: the printhead, drum, fuser, or control board — which no amount of settings reaches, and which is where “get help” becomes the correct answer rather than the last resort.

Before you call anyone in, collect the evidence that makes the help actually useful, because a repair or warranty conversation goes ten times faster with it: the exact error code or panel message; what prints and what doesn't (all colours? only from one device? a test page?); the result of a panel test page (this is the single most useful fact, because it tells the technician whether the fault is the printer or the connection); and what changed first (an update, a power cut, a moved cable, a new router). Then the honest decision: a cleaning cycle or a cartridge swap you can do yourself is worth trying first (see blank pages and streaks or lines), but a repeating hardware fault, a bricked firmware state, or a dead control panel is a repair or replacement call, and the when to get help section below lays out exactly those stops. This is the end of the ladder — everything above it has already been checked.

Blank pages are a supply problem in almost every case — the ink or toner simply isn't reaching the paper. Work the likely causes in order. First, the cartridge: is there any left, is it the right type, and is it fully seated? On a brand-new cartridge, check for the protective tape or plastic tab that ships in the ink path — leaving that in is the single most common cause of a printer that accepts a job, feeds paper, and outputs a blank page. Second, the inkjet printhead: if the cartridge has ink but the page is blank or has gaps, the head may be clogged, which the printer's own cleaning cycle addresses (usually under a Maintenance or Tools menu on the panel).

The sequence: confirm the cartridge level and seating, remove any protective tape, reseat it until it clicks, then print a nozzle-check or test page from the printer's panel (not from the computer, so you're testing the mechanism directly). If the panel's own test page is blank, the fault is the cartridge or the head — clean the head, and if a fresh genuine cartridge doesn't fix it, that's the hardware line. If the panel page is fine but computer jobs are blank, the problem is upstream of the mechanism — usually a job that never actually sent, so check the queue. Faded-but-not-blank is a close relative, covered in faded pages.

Faded output is “the supply is there but not enough of it, or not all of it.” For an inkjet, the usual causes are a low cartridge, an unevenly-fed or partially clogged head (which gives light patches rather than full blankness), or a quality setting turned down to a draft/economy mode to save ink. For a laser, faded pages usually mean the toner is genuinely low, or the toner has settled to one side of the cartridge — a gentle, level shake of a laser cartridge to redistribute the toner is a legitimate temporary measure, not a hack, and it's what many manuals quietly recommend.

The sequence: check the reported level and replace if low; on a laser with a half-depleted cartridge, redistribute the toner and reprint to confirm; check the quality/draft setting in the print dialog and the driver (an economy mode will deliberately thin the page); and if one colour is consistently faint, that cartridge's channel is the suspect. If fading comes with streaks or bands rather than uniform lightness, the mechanism is involved — streaks or lines. And if the page goes from faded to fully blank, follow blank pages.

Lines and streaks are the most diagnostic symptom a printer can give you, because the pattern points at a specific part. A repeating set of vertical lines, spaced at a regular interval, usually traces to a rotating component — on a laser, the drum or the transfer belt (the repeat distance roughly matches that part's circumference); on an inkjet, a clogged section of the printhead. A horizontal band is more often the printhead (inkjet) or the fuser (laser). A single thin scratch-like line can be a speck of debris or a scuff on the drum. So before replacing anything, note the direction and the spacing of the lines — that's what tells a technician which part, and what tells you whether it's a cleaning job or a replacement.

The sequence: on an inkjet, run the printhead cleaning cycle (the printer's Maintenance menu) and print a test page — clogs often clear in one or two cycles. On a laser, inspect and, if you're comfortable, clean or replace the drum (many drum units are user-replaceable; others are combined with the toner cartridge). Check for obvious debris in the paper path. If the lines survive a cleaning cycle and a fresh drum/cartridge, the fuser or belt is the suspect and it's the service line, not a settings fix. Faded output that turns out to be banded is this guide, not faded pages.

“Slow” has a few very different causes, and the first job is to tell whether it's slow to start (the job takes forever to begin) or slow to produce (pages come out one at a time, slowly). A long delay before the first page is usually on the computer side — a large or graphics-heavy file the spooler is processing, a network delay, or the spooler working through a backlog. Slow page production is more often a settings or hardware matter — a high-quality mode, or (less often) a thermal/mechanical limit of the machine.

The sequence: print a simple one-page text file in draft/standard quality — if that's fast, your “slow” jobs are heavy files or a high quality setting, and dropping to standard quality or a lighter file fixes it. If even a simple page is slow to start and the printer is on Wi-Fi, a network delay or a wedged queue is the likely cause — check the queue and Wi-Fi. If a simple page is slow to produce even in draft, the machine's speed setting or its age is the factor, and that's a specification of the device rather than a fault you can repair. This is one of the rarer “it's working as designed” outcomes, so isolate the file and the quality setting first before assuming a problem.

A “jam” message with no visible jam is almost never a mystery — the printer's paper-path sensor is being tripped by something small or by a component it reads as an obstruction. The three usual culprits: a tiny scrap of torn paper, a staple, or a pin caught somewhere you haven't looked (the rear access panel and the area under a cartridge are the classic hiding spots); a cartridge or drum that isn't fully seated, which many models interpret as a jam because the part isn't in its expected position; or a genuinely stuck paper-path sensor that a power-cycle resets.

The sequence: open every panel — front, rear, and the cartridge access — and look specifically for a small scrap or a staple, not just a big sheet; remove and fully reseat the cartridge/drum and the paper trays, since an unseated part is a top cause; then power the printer fully off and on (unplug for a few seconds if needed) to reset the sensor state. If the false jam returns on every job after a clean reseat and a reset, the sensor or the paper path is the suspect and it's the service line. A related symptom — the printer claiming there's no paper when there clearly is — is can't detect paper.

“No paper” with paper in the tray is a detection problem: the printer's feed sensor isn't seeing the stack. The causes are physical and simple. The paper isn't touching the sensor (loaded too far back, or a small stack that doesn't reach the feed point); the width guides are mis-set (too loose so the sensor doesn't register the edge, or so tight the stack is distorted); the job is set to a different tray than the one that's loaded; or the loaded paper type/size doesn't match what the driver is telling the printer to expect.

The sequence: reseat the paper so it's flat, touching the rear stop, and the guides snug against the edges without squeezing; select the correct tray and paper size in both the driver and the print dialog (a letter job pointing at an empty A4 tray reads as “no paper” in the tray it wants); try a fresh, smaller, flat stack to rule out a curled or clumped bundle; and if it still doesn't detect, the feed sensor is the suspect. If the “no paper” is really a false jam message, that's the false-jam guide; if paper feeds but crookedly or two at a time, the guides and the paper condition are the fix.

“Cartridge not recognised,” “ink not detected,” or a level that reads empty with a full cartridge — these are a reading problem, not necessarily a supply problem. The printer reads each cartridge through a chip and electrical contacts, and that read can fail for a few reasons: the cartridge isn't fully seated so the contacts aren't making; the contacts are dirty or oxidised; or — very commonly — the cartridge is refilled or third-party, and its chip either doesn't report a level the printer accepts or the printer is configured to reject non-genuine cartridges outright.

The sequence: remove and fully reseat the cartridge until it clicks; if the model allows it and you're comfortable, gently clean the cartridge contacts with a dry, lint-free cloth (follow the manual — some contacts are delicate); and be clear-eyed about the cartridge itself: if it's refilled or non-genuine, an “unrecognised” or “empty” reading may be the printer working as designed, and the clean fix is a genuine cartridge. If a confirmed-genuine, fully-seated cartridge still isn't detected, the printer's cartridge sensor is the suspect — that's the service line. Blank pages from a “full” cartridge are usually this same detection problem showing up downstream, in blank pages.

“Connected but unavailable” is a useful state to name because it rules things out: the computer sees the printer (so it's installed and, on a network, was found) but can't hand it a job. That narrows the fault to the path between the two — a network reachability issue, a wedged spooler, or a stale entry pointing at an address the printer no longer has. It's different from “offline” in that the link is present but not working, rather than flagged as down.

The sequence: confirm the printer and the device are on the same network; on a network printer, check you can reach the printer's IP (the address may have changed — IP & network configuration); restart the spooler on Windows if the queue is wedged (spooler); and if the entry is simply stale, remove and re-add the printer so the computer picks up the current address. If it's a one-off, re-adding usually fixes it; if “unavailable” keeps returning, that's a recurring drop and keeps going offline is the next read.

“Fixes and then breaks again” points at a connection that's unstable, not broken. The three recurring causes, in order of frequency: the printer's network address changes over time (the router hands out a new IP and the computer keeps calling the old one), the printer's own network power-saving drops its link after idle, and the printer and device sitting on different bands or networks that the router treats separately. Each of these “works” for a while and then fails, which is exactly the pattern you're seeing.

The sequence: give the printer a stable address — reserve its IP in the router (the usual fix) or set it static on the printer; reduce the printer's network power-saving in its settings so it doesn't drop the link when idle; and confirm same network and band for the printer and the device (see Wi-Fi connection). After these, the “keeps going offline” cycle usually stops. If it's a USB printer that keeps dropping, the analog is a marginal cable or port — USB connection problems — not a network setting.

A printer that was in the list and now isn't has usually been “forgotten” by the computer for one of three reasons: the network entry went stale (the printer's address changed and the old entry can't find it, so it drops off), a driver or OS update removed the device, or the printer itself left the network. The distinguishing question is whether the printer still shows up for other devices: if it does, the computer forgot it (re-add it); if nothing can see it, the printer left the network (reconnect it).

The sequence: check whether the printer is still visible to another device on the network; if yes, remove and re-add it on this computer and refresh the driver if the re-add fails; if no, reconnect the printer to Wi-Fi (Wi-Fi connection) and then re-add. For a network printer that keeps vanishing, the root fix is a stable, reserved IP so the entry stops going stale — IP & network configuration. A USB printer that “disappears” is a cable or port issue, not a network one — USB connection problems.

When you try to add a wireless printer and it simply doesn't appear in the list, the discovery step is failing. The usual reasons: the printer isn't actually on the network (its Wi-Fi dropped and it needs reconnecting), the printer and the device are on different networks or bands (many printers join 2.4 GHz only, and a guest or work network won't see it), or the printer's discovery is being blocked by the router or by the printer being in a setup/sleep state. “Not found” is a discovery problem, which is earlier in the path than “found but won't print.”

The sequence: confirm the printer's Wi-Fi is actually connected (its light, or a network-status page from its panel), and reconnect it if it dropped; confirm the device is on the same SSID and that the band the printer joined is reachable by the device; re-run the printer's network setup (the WPS button or the manufacturer's app) to force a clean re-discovery; and make sure the router isn't isolating devices or blocking discovery. If it's found after this but still won't print, you've moved past discovery into connects but can't print.

This is the subtle one, and the one people get stuck on longest: the printer's Wi-Fi light is solid, it shows as connected, and yet the job never arrives. The classic cause is an address mismatch — the printer got a new IP, but the computer (or the printer entry) is still sending jobs to the old one. A close second is the printer and the device being on different subnets or VLANs (common where a router separates IoT or guest devices), so each can “see” the other exist but can't actually exchange data.

The sequence: find the printer's current IP (print a network-status page from its panel, or check its settings), and compare it to the address the computer has stored for that printer — if they differ, update the printer entry to the current address, or better, reserve that IP in the router so it stops changing (IP & network configuration); confirm the printer and device are on the same subnet, not split across a guest or IoT VLAN. If the addresses match and it's the same subnet but jobs still don't land, a wedged spooler or a stale entry to re-add is the next suspect.

Most recurring network-printing problems trace back to one thing: the computer talks to a specific IP address, and when that address changes, printing breaks until the address is updated. By default, a router assigns addresses dynamically (DHCP), so a printer can get a new one after a reboot or a lease renewal — and the computer, still calling the old number, goes “offline,” “unavailable,” or simply stops finding it. The permanent fix is to make the printer's address stable: either reserve the printer's MAC address in the router (the cleaner option, because the router always gives it the same IP) or set a static IP on the printer (making sure it's outside the router's dynamic range so nothing else grabs it).

The sequence: find the printer's current IP (a network-status page from the panel is the reliable way); reserve it in the router (or set it static on the printer); then make sure the computer's printer entry uses that address — re-adding the printer by its reserved IP is often the cleanest way to point it correctly. This single change resolves the whole family of “keeps going offline,” “connects but can't print,” and “disappears” symptoms when the common root is a drifting address. If you're not comfortable in the router, the static-IP-on-the-printer route is the fallback, and the manufacturer's manual covers where the setting lives for your model.

This is the single best isolator in the whole hub, because it answers a question you otherwise have to guess at: if device A prints, the printer and its network are proven healthy — the fault is on device B's side. That shrinks a “the printer is broken” problem into a “this one device can't reach it” problem, which is far smaller. The usual device-B causes: it's on a different network or band than the printer, it needs the printer re-added, its driver or printing app is out of date or missing, or its default printer is set to something else.

The sequence, all on the failing device: confirm it's on the same network and band as the printer; remove and re-add the printer there; update or install the driver/app for that device (a phone needs the vendor app or AirPrint/Mopria — see printing from a phone); and check its default printer isn't pointed elsewhere (default printer). Because the working device proves the printer is fine, resist the urge to reset the printer itself — the fix is on the device that's failing, and this guide keeps you there.

A queue that repeatedly flips to “paused” is usually reacting to something, not misbehaving at random. The common triggers: a failed job at the head that pauses the queue behind it, a “pause printing” option left on (easy to switch on by accident in the queue window), or the spooler auto-pausing after an error so it doesn't keep sending jobs to a printer that just reported a problem. The first move is to find out why it paused, because “resume” without clearing the cause just gets it to pause again.

The sequence: resume printing to unblock it; cancel the failed job that triggered the pause (and anything wedged behind it — clear a stuck queue); make sure no “pause printing” box is checked; and if it pauses right after a specific error, the error is the real story — check the panel message and the spooler state. If the queue pauses with no error and no failed job, the spooler itself is the suspect and a restart of it (Windows) usually settles it.

A job that won't cancel usually means it's already past the point where the computer controls it. A print job has two homes: while it's in the computer's spooler, you can cancel it from the queue; once it's been handed to the printer, it lives in the printer's own memory, and the only way to clear it is to clear the printer. So “won't cancel” splits into two cases — a job stuck in the spooler (a computer-side cancel problem) versus a job already on the printer (which needs the printer powered cycled).

The sequence: cancel from the application first (the source), then from the queue (the spooler); if it's still listed and greyed out or “processing,” the spooler is holding it — restart the Print Spooler on Windows to force-clear it (spooler), or use cancel -a on macOS. If the job is no longer in the queue but the printer is still slowly printing it, it's on the printer now — power the printer off and on to clear its memory. That's the honest end of the road for a truly stuck job: the spooler for the computer's copy, a reboot for the printer's copy.

The print spooler is the Windows service that holds your print jobs and feeds them to the printer one at a time — it's the “spooler” in the diagram at the top of this page. When it's stopped, crashed, or clogged with a bad job, the symptoms are queue-specific: nothing prints even though the printer is fine, jobs pile up and never start, the queue window won't respond, or a single bad job wedges everything. The spooler is almost always running and healthy, so this is a later-stage suspect — but when a queue problem resists a simple cancel, the spooler is where to look.

The sequence: check the Print Spooler service is running (Services → “Print Spooler” — it should be “Running,” usually set to Automatic); restart it (Stop, then Start) — this clears a wedged queue and is the single most effective fix for a clogged spooler, and it's safe (any pending jobs are dropped, which is usually the point); and only if a restart doesn't clear a deeply stuck queue, the further step is to stop the spooler and clear its temporary files before restarting it — that's a “use caution” move because it deletes pending jobs, so do it only after the restart has failed. On macOS the equivalent is the CUPS printing system, managed through the Print Center rather than a visible service.

A driver that won't install is usually one of a few specific failures, each with its own tell. No driver found: the OS can't match the printer to a driver (common with newer or niche models, or when the printer isn't reachable during the install). The installer fails or errors: often a permissions issue (it needs admin rights), a blocked download, or a half-finished previous install in the way. It installs but the printer still isn't there: the driver went in but the device wasn't detected, so it needs (re-)adding. The through-line is the same as everywhere on this page: use the manufacturer's driver for your exact model and OS, and clear failed attempts before starting again.

The sequence: remove any failed or partial installs first (so a broken half-install isn't in the way); download the correct driver from the manufacturer's support page for your model and operating system — not a third-party updater; run the installer with administrator rights and let it complete without interrupting; for a Wi-Fi printer, allow the network access the first-time setup needs so it can reach the printer. If the driver installs but the printer won't appear, add it explicitly (USB is usually auto-detected; Wi-Fi you select by name) — and if the install itself keeps failing for a permission or compatibility reason, that's driver and software problems and the OS-level add flow in Windows & macOS.

The default printer is the device that silently receives a job whenever you hit print without choosing — so when it's set to the wrong printer, the symptom is baffling: you print, nothing comes out of the printer in front of you, and the page turns up somewhere else (another printer, a PDF, a virtual device). The two common sub-problems are a default that's simply wrong (easy to fix) and a default that keeps changing on its own (Windows, in particular, can rotate the default to whatever you last printed to, unless you tell it not to).

The sequence: set the default explicitly — Windows: Settings → Printers & scanners → choose the printer → set as default; macOS: System Settings → Printers & Scanners → pick it in the default-printer menu. On Windows, if it keeps changing, turn off “Let Windows manage my default printer” so your choice sticks. And remember the caveat: some applications keep their own default independent of the system one, so if a specific app still prints to the wrong place, check the printer chosen in that app's print dialog. Jobs landing on the wrong device are also the subject of prints the wrong document.

When the printer produces a page you didn't just send — an old report, a document from days ago — the almost-certain cause is a stale job still sitting in the queue that has now, at last, made it to the front. Print queues hold jobs until they're printed or cancelled, so a job that was stuck behind a failure (or just waiting) can surface much later, looking like the printer “printed the wrong thing.” The second, less common cause is the wrong printer selected in the dialog, so your current job went elsewhere and what printed was a leftover.

The sequence: open the print queue and look for older jobs behind or ahead of the current one — cancel the stragglers, which is the same move as clearing a stuck queue; confirm the right printer is selected in the app you're printing from, and that the default printer is what you expect; and restart the application if it seems to be re-sending a cached document. Once the queue is cleared of leftovers, the “wrong document” symptom disappears, because there's nothing old left to print.

Mobile printing uses a different path than the desktop, and it has its own setup: on iOS/iPadOS it's AirPrint (the printer appears in the Share → Print sheet if it supports the protocol and is on the same network); on Android it's either the built-in printing service or the manufacturer's app / a standard like Mopria, depending on the model. The common requirement across all of it is the same as desktop — same Wi-Fi network — plus the phone actually having the printer in its list, which often needs a one-time add or an app.

The sequence: confirm the phone is on the same network as the printer; open the share/print sheet and see whether the printer is listed — if not, add it there or install the manufacturer's printing app for the model; make sure the printer supports the protocol the phone uses (AirPrint for iOS, Mopria or the vendor app for Android). If the desktop prints fine but the phone doesn't, the printer is proven healthy and the whole problem is on the phone's side — the same logic as works from one device, not another, just applied to mobile.

Browser-specific printing problems are usually about the browser's own print dialog rather than the printer: the printer shown in the browser's dialog is different from the one you expect (browsers can carry their own last-used choice), a specific website that overrides or restructures the page for printing, or the browser choosing a different default. The cleanest isolator is the same one used elsewhere: if the same page prints correctly from a different browser, the problem is the first browser's settings or a cached choice, not the printer or the file.

The sequence: in the browser's print dialog, check which printer is actually selected and pick the right one; try the same page in a different browser to isolate the browser from the printer; if it's one specific site, check that the site isn't forcing a print layout that's breaking (and try printing from the site's own “print” option if it has one); and as a data check, “Save as PDF” first — if the PDF is correct, the content is fine and the problem is purely the print step. A PDF that then prints wrong is the next guide down, printing PDFs incorrectly.

A PDF that prints cut off, scaled wrong, rotated, or on the wrong number of pages is almost always a settings mismatch between the PDF viewer and the printer, not a printer fault. The usual culprits: scale / “fit to page” left off (so a document sized for a different page size overflows or shrinks), the paper size in the viewer not matching the loaded paper, or the PDF viewer's own print defaults differing from the OS's. The tell that it's the viewer and not the printer: the same PDF prints correctly from a different reader, or the “Save as PDF” round-trip is fine.

The sequence: in the PDF reader's print dialog, set scale to “Fit” / “Fit to page” (or 100% if you want exact size) and match the paper size to what's loaded; try a different PDF reader to isolate the viewer — if another reader prints it correctly, the first reader's defaults were the cause; and print through the OS print dialog where available rather than a viewer shortcut. If every reader prints the file wrong the same way, the file itself (its page size or a scanned layout) is the factor, and re-sizing it before printing is the fix.

An error code is the printer doing you a favour: it's naming the subsystem that's at fault, which is the fastest possible route past guessing. The right first move is simply to note the exact code (the number and any letters, exactly as shown — and the panel's wording, since the same code family can be labelled differently), because that's what turns “it's broken” into “the paper path is obstructed” or “the imaging unit needs attention.” Codes cluster into a few families: paper (jam, no paper, feed), supply (cartridge, toner, drum), connection (network, USB), and maintenance/service (cleaning, a part that needs replacing). Which family it's in tells you whether it's a ten-second fix or a service call.

The sequence: read the full message, not just the code — the panel usually says what to do (“open the rear door,” “replace the black cartridge”); look up the exact code for your model on the manufacturer's support site, because codes aren't universal across brands and even across models; and act on the family — a paper code goes to false jam or no paper, a supply code to ink/toner, a maintenance code often to a cleaning cycle or a part. If the code is one the manufacturer lists as a service item, or it returns after you've done the listed action, that's the when to get help line, and the code is the most useful thing you can give the technician.

Firmware is the printer's own operating software, separate from the driver on your computer. It matters for troubleshooting in two opposite ways: a known bug in an older firmware can cause a printing fault that a update fixes, and a failed or interrupted firmware update can leave the printer misbehaving or, in the worst case, unable to boot properly. The one rule that keeps updates safe: never interrupt a firmware update — don't power the printer off or unplug it mid-update — because an update cut short is exactly what turns a routine change into a “now it won't start” problem.

The sequence: check the current firmware level (usually in the printer's settings or on a status page); update from the manufacturer's support site or the printer's own update option — get the update for your exact model, and let it run to completion with stable power and network; and if an update failed partway or the printer won't recover, that's a “use caution” state where the manufacturer's recovery procedure (often a specific button combination or a support tool) is the right next step, and vendor support is a legitimate call rather than a last resort. Firmware work sits alongside the driver in the advanced layer — the driver is on the computer, the firmware is in the printer, and a printing fault can live in either.

This is the entire ladder from the top of the page condensed into an ordered list, in the sequence it should be done — cheapest and safest first, driver and network steps later. It mirrors the interactive checklist below, and it's written so you can work it with a pen if you'd rather not touch the computer yet. The principle is the same as the whole hub: each item either fixes it or rules a link out, and you stop at the first one that does.

Work top to bottom: power and status (on, awake, no error light — part 2); paper and supplies (loaded, seated, levels, protective tape — part 3); offline status cleared (part 4); queue checked and cleared (part 5); right printer selected in the dialog and as default (default); the connection confirmed — USB seated or on the same Wi-Fi (USB / Wi-Fi); a test page from the panel to split computer-side from printer-side; driver current (part 6); spooler restarted on Windows if the queue is wedged (spooler); stable IP for a network printer that keeps dropping (IP); and a reboot of both printer and computer to clear anything wedged. If you've done all of that and it still won't print, you're at the advanced layer and the when to get help section — and the interactive version of this list, with saved ticks and a copy button, is the checklist below.