Printing and scanning are handled by separate software components inside the same printer, which is exactly why one can work perfectly while the other does nothing at all.
Most manufacturers publish two different driver packages for the same printer — a "basic" or print-only driver, and a "full feature" or "full software" package that adds scanning, ink monitoring, and maintenance tools. Auto-installers and some Windows/Mac built-in driver detections often grab the smaller, basic package by default, since it's faster to install and less likely to fail. The printer works for printing immediately, and scanning simply doesn't exist as an option anywhere — not broken, just never installed. Reinstalling the driver from the manufacturer's site and explicitly choosing the full package resolves this more often than any other fix on this list.
Before troubleshooting further, confirm whether a scan app even exists on your system. On Windows, search for "Windows Fax and Scan" or your printer brand's own utility (HP Scan, Canon IJ Scan Utility, Epson Scan 2, etc.). On Mac, open Image Capture, or Preview's File → Import from Scanner. If your printer doesn't appear as an available scanner in any of these, that confirms the driver's scan component isn't installed — see above.
Windows uses a background service called Windows Image Acquisition (WIA) specifically for scanning. If this service has stopped or hung, printing continues working normally (it uses a separate service entirely) while scanning fails silently or times out. Search for "Services" in the Start menu, find "Windows Image Acquisition (WIA)", and restart it.
Many Wi-Fi and network printers ship with the ability to scan directly to a computer turned off by default, as a security measure — printing works over the network fine, but scan-to-computer needs to be explicitly enabled, usually through the manufacturer's own printer utility software rather than the printer's physical control panel. Check your printer utility's settings or scan tab for this option.
For network scanners specifically, some firewalls and antivirus tools block the specific traffic scanning uses while leaving print traffic untouched, since they use different network protocols. If nothing above resolves it, temporarily disabling your firewall to test (then re-enabling it and adding a specific exception if that was the cause) will confirm whether this is the culprit.
Less commonly, the scanner hardware itself can get stuck reporting "busy" after an interrupted job (a power blip, a USB disconnect mid-scan), even though the print mechanism is entirely unaffected since they're physically separate systems. A full power-off for 30 seconds, then back on, clears this in most cases.
Our troubleshooting handbook covers scanner-specific fixes in more depth, alongside the other most common printer issues.
Get the Troubleshooting HandbookThe specific sequence that resolves most failed installations.
Read the article →The four categories almost every printer error falls into.
Read the article →Why each step matters and the mistakes that cause most first-time setup failures.
Read the article →