Your Printer Stopped Printing: A Triage Order That Saves an Hour

An office printer that refuses to print is a special kind of annoying, because nothing about the machine looks broken. The panel is lit, the tray is loaded, and the PC still behaves as if there is nothing to send. In a small shop that single fault can freeze invoices and delivery notes for half a morning.

What follows is a triage order, not a repair manual. Work down it and stop as soon as pages come out. Sections one to four cover the overwhelming majority of cases; hardware replacement sits at the very bottom for a reason.

1. Decide first whether the printer or the PC is at fault

Send a test page straight from Windows, not from the application you were using. Settings, then Bluetooth devices, then Printers scanners, pick the device, choose Print test page.

If that page appears, your printer and its driver are healthy and the fault lives in the document or the app you were printing from. If nothing appears, keep going.

While you are in that screen, deal with one setting that causes endless confusion: turn off Let Windows manage my default printer. When it is enabled, Windows promotes whichever printer was used last, and jobs quietly land on a machine that is switched off.

2. Symptom to first move

What you see	What it usually means	First move
Nothing happens at all	A dead job is blocking the line	Clear the queue, restart the spooler
Printer marked offline	Port or address moved	Rebuild a Standard TCP/IP port
Panel light blinking	Jam, open cover, empty cartridge	Clear it on the printer itself
Pages arrive blank	Tape left on a cartridge, dried printhead	Remove tape, run a nozzle check
Symbols instead of text	Driver language mismatch, failing cable	Install the right driver, swap the cable

3. One bad job can block everything behind it

A single corrupt job parks itself at the head of the line, showing printing or deleting forever, and every document you send afterwards queues up behind it. Open the queue from Printers scanners, then check the Printer menu and make sure Pause Printing and Use Printer Offline are both unticked, because either one silences all output.

Cancel everything in the list. When a job refuses to disappear, press Win + R, run printmanagement.msc, right-click the device under Printers and pick Cancel All Jobs. If the queue still will not clear, restart Print Spooler from services.msc, or from an administrator Command Prompt with net stop spooler followed by net start spooler.

The job files themselves sit in C:\Windows\System32\spool\PRINTERS. Stop the spooler, empty that folder, leave the folder in place, start the spooler again. A high, flat CPU load from spoolsv.exe or splwow64.exe in Task Manager points at a driver problem rather than a queue problem, which sends you to the next section.

4. Drivers: why the right page comes out as garbage

Windows will happily install a generic driver that detects a printer without printing reliably on it. Remove the device, then download the full package for the exact model using the number on the label at the back, because drivers for a neighbouring model install cleanly and then produce blank or scrambled output.

Two details decide whether the manual install works. Pick a Standard TCP/IP port instead of WSD, since WSD discovery is a well-known source of printers that flicker in and out of offline. And match the driver language to the hardware: sending a PostScript job to a device that only understands PCL produces the classic page of random symbols.

5. Network printers: the address that quietly changed

A network printer can drop off the map without anything being wrong with it, simply because the router handed it a new address overnight. Windows keeps posting jobs to the old one indefinitely.

Print a network configuration page from the printer panel to read the current address, then ping that address from Command Prompt. Replies mean the network path is healthy and the Windows port is stale. No replies mean a Wi-Fi or addressing problem.

Rebuild the port under Printer properties, Ports tab, Add Port, Standard TCP/IP Port, typing the address you just read. To stop it drifting again, add a DHCP reservation on the router that pins the printer's MAC address, which is safer than fixing an address on the printer itself.

Wi-Fi faults follow familiar shapes. Plenty of printers only speak the 2.4 GHz band, so a router publishing one name for both bands can be split temporarily. Guest networks isolate their clients from each other and block printing outright. Wi-Fi Direct is a decent emergency path when you need one page out the door, though you give up internet access on that device while connected. Phones can only reach a printer that shares their network, which is why a phone on mobile data never finds it.

6. USB printers: cable and port limits

Physical causes are more common here than most people assume. Plug straight into the machine, ideally a rear port, because unpowered hubs and dock stations often cannot supply enough current for reliable detection. A standard USB 2.0 cable is dependable up to about five metres; past that you need an active extension, and a long thin cable explains the intermittent detection that gets blamed on drivers.

Swap the cable before reinstalling anything, then open Device Manager with View, Show hidden devices and look for a warning triangle. If a second computer also fails to see the printer with the same cable, the fault is in the cable or the printer, not in Windows. Some models drop off the bus when they enter deep sleep; if that matches what you see, turn off sleep in the printer's own menu rather than changing Windows settings.

7. Habits that prevent most of these faults

Print one page a week. An inkjet left idle for a month or two dries its printhead, and a weekly page keeps the nozzles wet for almost no cost. Keep the unit covered and dust-free, and run the alignment and nozzle checks from the vendor utility when output starts looking faint.

Check the obvious setting before blaming hardware: faint office output is frequently just Draft or Economy mode left on, and Windows toner readings can lag behind the cartridge in the machine. When pages come out blank right after a cartridge change, look for the protective tape or vent strip first — that is by far the most common cause, and dried printheads come second.

And when a printer works from one PC but not another on the same network, leave the printer alone. The problem is local to that machine: a stale port, a corrupt driver, or a job stuck in the queue.

The short version

Test page first, to separate printer faults from application faults. Queue and spooler second, because one bad job blocks the line. Driver and port third. Physical cable, address and maintenance last. Most "printer won't print" tickets close somewhere in the first three, without a single part being replaced.

---

Originally published at tanit365.com.