Cause #1: Paper Jams (and Why They Keep Coming Back)
If your printer's blinking a red light and the display says something like "Paper Jam" or "E1," the paper path is blocked. That's the most common printer error, full stop. But here's what most people miss: the jam you can see isn't always the jam that's causing the error. A tiny scrap of paper stuck near the rollers will keep triggering the same fault even after you've pulled out the obvious sheet.
I once had a user whose HP LaserJet Pro M404dn kept showing "Jam in Tray 2" every third print. He'd open Tray 2, find nothing, close it, and the error would clear for a page or two. The real culprit was a torn corner of a label sheet wedged behind the pickup roller. Took five minutes to find once we looked in the right place.
Here's how to clear a paper jam properly:
- Turn the printer off and unplug it. This releases the rollers so you're not fighting the motor.
- Open every access door. Front cover, rear door, duplex unit, and pull out all trays. Paper hides in the back where you can't see it.
- Look for scraps. Use a flashlight. Check behind the fuser (if it's a laser printer) and under the printhead carriage (if it's inkjet). Don't touch the fuser — it can be hot even after shutdown.
- Pull paper in the direction it feeds. If you yank it backward, you'll tear it and leave bits behind. Slow and steady.
- Check the rollers. Worn or shiny pickup rollers lose grip. If they look slick, clean them with a lint-free cloth dampened with distilled water. Replace them if they're cracked.
- Close everything, plug back in, power on. The printer should run a self-test. If the error clears, print a test page.
After you close the doors, you should see the control panel return to "Ready." If it still shows a jam, there's another scrap somewhere. Repeat the inspection — don't assume the sensor is bad yet.
Pro tip: Don't overload the tray. Most trays have a max fill line. Going past it causes misfeeds and jams. Also, fan the paper stack before loading. Sheets stuck together from humidity feed as two and jam every time.
Cause #2: Printer Shows Offline (But It's Plugged In)
Your computer says the printer is offline. The printer's on. The Wi-Fi light is solid. So what gives? Nine times out of ten, it's a stale print queue or a changed IP address. The computer is still trying to talk to the printer at an old address, and the printer's moved on.
This hits wireless printers hardest. If your router rebooted and handed out a new IP to the printer, Windows doesn't automatically update the port. The job sits there forever. You'll see "Offline" or "Error – Printing" in the queue.
Fix it in this order:
- Clear the print queue. Open Settings > Bluetooth & devices > Printers & scanners (Windows 11) or Devices > Printers & scanners (Windows 10). Click your printer, then Open print queue. Cancel every job. If jobs won't cancel, restart the Print Spooler service.
net stop spooler
net start spooler
Run that in an elevated Command Prompt. You should see "The Print Spooler service was stopped successfully" then "started successfully." The queue empties.
- Set the printer to online. In the print queue window, click Printer in the menu bar. If Use Printer Offline has a checkmark, click it to remove the check. That single toggle fixes more "offline" complaints than anything else.
- Check the IP address. Print a network config page from the printer's control panel (usually Settings > Reports > Network Configuration). Note the IP. On your PC, go to the printer's properties, Ports tab, and make sure the port matches that IP. If not, create a new Standard TCP/IP port with the correct address.
- Give the printer a static IP or DHCP reservation. Log into your router and reserve the printer's MAC address. That way the IP never changes. This is the real fix — everything else is a band-aid.
After setting the port correctly, print a test page. You should hear the printer wake up within a few seconds. If it stays silent, the firewall might be blocking the connection. Allow the printer's IP through Windows Defender Firewall on port 9100 (raw printing) or 631 (IPP).
Skip the "troubleshoot" wizard if you've already checked the queue and port. It rarely finds network port mismatches and just wastes your time.
Cause #3: Driver and Spooler Glitches
You've cleared the jam. The printer's online. But jobs vanish, print garbled text, or throw errors like "0x0000011b" or "Windows cannot connect to the printer." That's a driver or spooler problem. It's the third most common cause, and it's the one that makes people want to throw the printer out the window.
This error pops up a lot after Windows updates. The update replaces a driver with a generic one, or a security patch breaks RPC printing. I've seen it hit entire offices after a Patch Tuesday — every shared printer goes down at once.
Here's the fix that works:
- Remove the printer completely. Go to Printers & scanners, select the printer, click Remove device. Then open Print Management (search for it in the Start menu), go to All Printers, and delete any leftover entries.
- Delete the driver package. In Print Management, click Drivers. Find your printer's driver, right-click, and choose Remove driver package. Check the box to delete the driver files. If it won't delete, stop the spooler first (see command above).
- Download the latest driver from the manufacturer. Don't use Windows Update's version. Go to HP, Canon, Epson, or Brother's site and grab the full driver package for your exact model. For a Brother HL-L2350DW, for example, get the full driver and software package, not just the basic driver.
- Install the driver as administrator. Right-click the installer and choose Run as administrator. Follow the prompts. When it asks how to connect, pick USB or network — whichever you use. Don't let it auto-detect if you know the IP.
- Restart the spooler service. Even after a clean install, restarting the spooler clears any stuck jobs from the old setup.
After the install finishes, you should see your printer listed with a green checkmark. Print a test page. If it prints clean, you're done. If it's garbled, you likely installed a PCL driver when you need PostScript (or vice versa). Check the printer's specs — most modern lasers handle both, but older models are picky.
One more thing: if you're on a corporate network and see error 0x0000011b, it's a known RPC issue. The workaround is to edit the registry on the print server. Set RpcAuthnLevelPrivacyEnabled to 0 under HKLM\System\CurrentControlSet\Control\Print. Reboot the server. That's a temporary fix — patch both machines fully to close the security hole.
Quick Reference: Printer Error Cheat Sheet
| Symptom | Most Likely Cause | First Fix to Try |
|---|---|---|
| Red light, "Paper Jam" message | Scrap of paper in path | Power off, open all doors, inspect with flashlight, remove scraps |
| Status shows "Offline" | Queue stuck or IP changed | Clear queue, uncheck "Use Printer Offline," verify IP port |
| Jobs vanish or print garbled | Corrupt driver or spooler | Remove printer and driver, reinstall from manufacturer, restart spooler |
| Error 0x0000011b on network | Windows RPC security update | Registry fix on print server, or patch both machines |
| Ink cartridge not recognized | Dirty contacts or third-party chip | Remove cartridge, clean gold contacts with dry lint-free cloth, reseat |
| Print quality streaks or gaps | Clogged printhead or low toner | Run built-in cleaning cycle, check toner level, replace if needed |
That table covers 90% of what you'll see. Keep it handy. And remember: when a printer acts up, start with the simplest thing — paper path, then connection, then software. Work in that order and you'll fix most errors in under ten minutes.