Printer won’t print when I really need it — emergency checks to run first

Hi! If your printer won’t print and it’s one of those “I need this right now” moments, the fastest path is to avoid random reinstall/reset steps and instead figure out where the failure is happening: the printer itself, the connection (Wi-Fi/USB), the computer’s print queue, or the app/document.

Before we do anything disruptive, can you tell me a few quick facts (any order):
1) What device are you printing from: Windows 11/10, macOS, phone (AirPrint), or something else?
2) What do you see on the printer: any lights, error code, “offline,” “paused,” low ink/toner, paper jam, or just “ready”?
3) What happens on the computer: does the job sit in the print queue stuck on “Printing,” does it disappear instantly, or does it say “Error/Offline”?

We’ll use your answers to pick the safest emergency checks without making the situation worse.

Got it — urgent prints are the worst time for a “silent failure.” Let’s narrow it quickly with observation, not guesswork.

First, two different failure patterns look the same from your side (“nothing prints”):
Pattern A: the job never reaches the printer (queue/connection issue).
Pattern B: the job reaches the printer, but the printer blocks it (offline/paused/paper/cover/ink/toner).

Quick questions (short answers are fine):
• Are you connected by Wi-Fi or USB?
• On the printer screen (or lights), does it look “Ready,” or does it show anything like “Offline,” “Paused,” “Attention,” or “Paper”?
• On your computer, do you actually see the print job appear in the printer queue?

That detail is really useful: job appears briefly, then vanishes, while the printer stays “Ready.” That can happen when the print is being sent to the wrong printer queue, the job is being redirected (for example to “print to PDF”), or the app is failing before it actually transmits data to the printer.

Let’s confirm three things without changing anything major:
1) In the print window, what exact printer name is selected? (Sometimes Windows picks a similarly named device, a virtual printer, or an old “offline” instance.)
2) What are you printing — a PDF, email, web page, Word/Docs? And does it fail in every app or just one?
3) Do you have another device on the same Wi-Fi (phone/tablet) that can “see” the printer? This isn’t a fix — it’s just to tell whether the printer is reachable on the network right now.

Great — Brother MFC on Wi-Fi + PDF from a browser preview is a very common “urgent print won’t go” combo, and it doesn’t automatically mean the printer is broken.

Two diagnostic angles (we can do either first):

Angle 1: App/document isolation
Browser PDF viewers sometimes behave differently than a dedicated PDF app. If Edge preview fails but a different app prints, that points to an app-level printing issue, not the printer hardware.

Angle 2: Queue/spooler symptoms
When jobs flash and disappear, sometimes Windows is “handing off” the job but it never reaches the device due to a queue/port mismatch — often seen as the printer being “online” but not actually receiving data.

A couple of “tell me what you see” checks:
• In Windows Settings → Printers (or Control Panel), does the printer status show Online, Offline, or Paused?
• If you open the printer’s queue window, do you see any history of failed jobs, or is it completely empty right after you print?
• Is this printer sometimes used via a different network (work VPN, guest Wi-Fi, extender)?

Okay — “Ready” + empty queue could still be one of these:
• The job is going to a different instance of the printer (Windows can create duplicates after updates).
• The document/app stops before it transmits (looks like it “printed” but never actually sent data).
• The printer is reachable but not actually accepting jobs right now (for example, it’s in a quiet paused/offline state on the device side even if Windows says Ready).

Since you’re in an emergency scenario, I want to avoid risky changes. Let’s do a simple confirmation test that doesn’t require reinstalling anything:

Question: Does it fail only with that PDF/email preview, or would it also fail if you print something ultra-simple like a one-line Notepad text file?

And on the printer itself, does it have a “Wi-Fi” indicator showing it’s connected (not searching/disconnected)?

That’s an important split: if Notepad prints and some PDFs print, then your printer and Wi-Fi connection are probably okay. The “won’t print” event is more likely tied to the specific file or the way it’s being opened/previewed.

When one PDF fails and another succeeds, common non-hardware causes include:
• The PDF is encrypted/restricted or has unusual fonts/layers (some viewers handle it differently).
• The PDF is being printed from an email/web preview rather than a downloaded file.
• The job is being sent with a different paper setting or rendering mode depending on the viewer.

I’m not going to give you a “do this and it will definitely work” script — but to pinpoint what’s happening, can you tell me:
1) Is the failing PDF being printed straight from the email preview (Edge/Gmail/Outlook view), or after saving it to your computer?
2) When it “prints nothing,” do you hear the printer wake up at all (feed noise), or is it totally silent?
3) Any pop-up warning that appears briefly and disappears (permission, “printing failed,” etc.)?

“Totally silent” strongly suggests the printer never receives a real job. That points more to the viewer/hand-off step than the printer’s mechanics.

In urgent situations, the best diagnostic is to change only one variable at a time:
Variable to isolate: preview vs downloaded file vs different app.

Without changing your printer setup, here are safe “is it the file or the path?” checks you can report back on:
• If you download the same PDF (save to Downloads) and print it, does the printer react? (Even if it fails, does it at least wake up?)
• If you open the same saved PDF in a different viewer (not a browser preview), does the print dialog behave differently (paper size, “Print as image,” etc.)?

Also, one more quick question: are you printing in black & white or color, and does the printer show any supply warnings (even if it still says Ready)?

It can be, yes — not always, but often enough that it’s worth isolating. Email/web previews are essentially a mini-viewer inside the browser, and the “print” action can behave differently depending on how the PDF is rendered and what permissions it has.

The reason I’m leaning that way in your case is: other PDFs printed, Notepad printed, the printer stays silent, and Windows acts like the job completed. Those are classic signs the job didn’t make it past the preview layer.

One more angle (just to avoid missing an obvious blocker): when you print, does the document show up under recently printed or printer history anywhere, or is it like the job never existed?

And do you have more than one “Brother MFC-Jxxx” listed in Windows (sometimes one is the actual device, another is an old/offline instance)?

That’s a very realistic cause of “printer won’t print” with no error: Windows can keep multiple printer instances after updates or reconnects, and one of them may point to an old port/IP. From your side it looks like it printed, but the job effectively goes nowhere.

I’m not going to walk you through deleting/reinstalling printers here — that’s the kind of change that can backfire under time pressure — but as a pure diagnosis, this is what I’d conclude from your symptoms:
• The printer and supplies are likely fine (other prints succeed).
• The failure is likely in the print path (preview + which queue you’re targeting).
• Duplicate printer entries are a strong signal of a queue/port mismatch possibility.

If you can tell me which of the two entries shows as “Ready/Online” consistently, and whether the failing job targets that exact entry, we can confirm if the issue is the printer queue selection vs the PDF preview behavior.