Printers and scanners are the hardware category Windows treats worst. The OS ships with a generic driver, a “Scan” app that discovers your device maybe half the time, and a print queue that jams on a deleted job with no way to flush it. If your Epson won’t scan over Wi-Fi or your Brother prints garbage after a driver update, you already know the stock tools aren’t enough.
Get the driver right before anything else
Most “broken printer” problems are driver problems. Windows Update pushes a basic driver that handles printing fine and scanning poorly, or worse, picks the wrong model in a family of lookalike devices.
Two approaches that actually work:
Use the manufacturer’s vendor driver when the device is current and you want full features (duplex, scan-to-PDF, ink levels). Use the plain Microsoft IPP class driver when you just want reliable network printing and the vendor software is a 400 MB bundle full of tray icons you’ll never open.
Download the driver from the vendor’s own site, not a third-party “driver updater.” I’ve said it before in our driver guide and it’s worth repeating: the only safe sources are the hardware vendor and Windows Update. Those driver-scanner utilities that promise one-click updates are how people end up with a webcam driver from 2011 installed on a laptop that never had a webcam.
One detail worth knowing: if the device is USB-only and you’ve moved it to a new machine, uninstall the old driver first under Settings > Bluetooth & devices > Printers & scanners, then reinstall. Leftover driver packages are a common cause of “printer offline” that survives reboots.
The utilities that are actually worth installing
1. Vendor scan tools (Epson Scan, HP Smart, Canon IJ Scan Utility)
Annoying? Yes. Necessary? Often. Windows’ built-in scanner support through WIA (Windows Image Acquisition) tops out at basic flatbed captures. If you want to feed from an ADF, set a custom DPI, or batch-scan to multipage PDF, you need the vendor bundle. HP Smart is the heaviest of the three and insists on an account for cloud features you can ignore. Epson and Canon are lighter. Install the scan component only, and skip the “photo printing” and “creative” downloads if the installer offers a custom path.
2. NAPS2 (Not Another PDF Scanner 2)
This is the one I’d recommend to anyone scanning more than once a month. NAPS2 is a free, open-source document scanner front end for Windows that talks to your existing WIA or TWAIN driver. You point it at the device, hit scan, and it produces multipage PDFs with OCR via Tesseract, auto-crop, deskew, and batch profiles.
It does not replace your driver. It sits on top of it. That’s the point: your scanner works the way Windows expects, but the interface stops fighting you. Scan twenty pages from an ADF into one searchable PDF and you’ll wonder why you ever used the vendor app. No account. No telemetry I could detect. It runs from a portable folder.
3. IrfanView for image cleanup
Scans come out crooked, grey, and 600 dpi when you wanted 200. IrfanView has been the fastest image viewer and quick editor on Windows for years, and it’s the tool I reach for to crop, straighten, adjust contrast, and re-export a scanned page at a sane file size. Batch conversion handles an entire folder of scans at once. It won’t annotate or sketch, so for signing documents you’ll still want something else, but for cleanup it’s near-instant even on old hardware.
4. 7-Zip or PeaZip for scan archives
If you scan in bulk and email the results, you’re shipping huge PDFs. Compressing a folder of TIFFs into a 7z archive can cut the size substantially before sending. Both tools are free and covered in our compression roundup; neither needs a printer to exist, but they belong in the same workflow box.
5. PrintFlush / print queue tools
Windows’ print spooler is fragile. A single stuck job can block every subsequent print, and the Cancel button does nothing because the job is wedged in the spool. The reliable fix is stopping the Print Spooler service, deleting the files in C:WindowsSystem32spoolPRINTERS, and restarting the service. You can do this by hand, or use a small utility that wraps the same steps into one click. These tools are thin wrappers, but when you’re in a hurry they save the manual trip through Services.msc.
Wireless printing: the part nobody warns you about
Wi-Fi printers are the single largest source of “it worked yesterday” support requests. The failure mode is almost always the IP address. Your router hands the printer a new one after a reboot, the driver keeps pointing at the old one, and Windows reports the device offline while the printer sits there perfectly happy.
The fix is a DHCP reservation in your router, or a static IP set on the printer itself. Once the address stops moving, most wireless printers become boring, and boring is what you want.
For scanners specifically, some models only offer scan-over-network through the vendor’s own service, not WIA. If NAPS2 can’t see your scanner across the network, that’s usually why. Plug in USB for scanning and keep Wi-Fi for printing. It’s a compromise, but a stable one.
What to skip
- Third-party driver updaters. Unsigned, frequently bundled, and capable of breaking a working device. Use Windows Update or the vendor site.
- “Printer cleaner” and “ink saver” utilities. Ink levels are reported by the cartridge chip. No software can refill or extend it, and most of these are adware with a printer icon.
- Vendor cloud print services. If you don’t print from your phone away from home, disable them. They add background services and want an account.
- HP Smart’s full install if you only print. The IPP class driver plus the vendor scan utility is a smaller, faster combination.
Quick troubleshooting hierarchy
When something breaks, work in this order and stop when it’s fixed:
- Check the physical layer first: paper, cable, power, Wi-Fi light.
- Reboot the printer, not just the PC.
- Run the built-in troubleshooter under Settings > System > Troubleshoot.
- Clear the spool folder and restart the Print Spooler service.
- Reinstall the driver from the vendor.
- Try the IPP class driver to isolate whether it’s the driver or the device.
The pattern in all of this: Windows’ native tools are a floor, not a ceiling. They’ll get a document out of most printers. They will not give you a clean, searchable, batch-scanned archive, and they will not tell you why the queue is stuck. A four-app stack (vendor scan utility, NAPS2, IrfanView, and a spool fix) covers everything the OS leaves on the table, and none of it costs a cent unless the vendor forces a paid tier, which so far none of the scan utilities here do.