"Scanner not working" covers a wide range of very different problems — a scanner that isn't found at all, one that's found but stuck on "busy," one that scans but won't save the file, and one that scans but produces a blank, dark, or skewed image. This guide treats each of those as the distinct problem it actually is, whether you're scanning to email, to a folder, to PDF, from a flatbed, or through an automatic document feeder (ADF), on Windows, on Mac, or over a wireless network.
Scanning looks like a single action — place a document, press a button, get a file — but like printing, it depends on several layers working together correctly. When you scan a document, the scanner's hardware captures the image and passes it through a driver stack, most commonly using a standard called TWAIN on Windows or a similar image-capture framework on Mac, which your scanning software then uses to bring the image into a usable file.
From there, the software has to know where to actually put the finished file: saved locally to a folder, converted and saved as a PDF, or sent out through an email account using the device's saved SMTP (outgoing mail server) settings. A fault at the driver level, the software level, or the destination-configuration level all produce very different-looking symptoms, even though the underlying document scanned successfully in every case.
Fig. 1 — A scan job passes through the scanner hardware, its driver, the scan software, and finally its saved destination — each a separate potential point of failure.
Because scanning depends on hardware, a driver, software, and a configured destination, the causes span all four layers. They're grouped below by where the fault typically originates.
Fig. 2 — Scanner problems generally originate in the network/USB connection, the driver or scan software, or the configured save destination.
Windows relies on TWAIN or WIA drivers and Mac uses its own image-capture framework; either one going out of date or becoming corrupted is the single most common reason a scanner stops being detected.
A wireless scanner depends on a stable network link just like a wireless printer does, and a weak signal can cause it to intermittently disappear from the device list — the same root cause behind many "scanner not found" and "scanner offline" errors.
If the scanner's network address changes — commonly after a router restart — the saved connection on your computer keeps trying to reach an address that's no longer correct.
For directly connected scanners, a loose cable, damaged port, or unpowered USB hub produces the same "not found" or "not connecting" symptoms as a network issue would.
Security software can block the specific network ports scanning uses, particularly right after a security suite update resets its rules.
Windows uses network discovery to locate scanners on the same network as it does for printers; turning this off can make an otherwise healthy scanner impossible to find.
Both Windows and macOS run a background service dedicated to image capture and scanning; if it's stopped or crashed, the scanner can appear completely unresponsive or stuck showing "busy."
Reinstalling scanning software without fully removing an older driver first can leave two conflicting entries, with the stale one continuing to cause errors.
If the scan destination path has been moved, renamed, or deleted, the software can report a generic failure without stating clearly that the destination itself is the problem.
A destination folder the scanning account doesn't have write permission to will silently reject the incoming scanned file.
Scan-to-email depends on correctly saved outgoing mail server details; an expired password, changed port, or security setting on the email account is the most common reason this specific feature stops working while local scanning still succeeds.
A destination drive or cloud folder that's run out of space will cause scans to fail to save, often without a clearly worded error message.
Selecting a file format the receiving application or destination doesn't support (an outdated PDF version, for instance) can cause the file to appear corrupted or fail to open.
The automatic document feeder has its own rollers, separate from the print paper path, which wear down independently and cause misfeeds or jams specifically during scanning and copying.
Dust, fingerprints, or debris on the flatbed glass or inside the ADF sensor path commonly causes blank sections, streaks, or shadows on an otherwise successful scan.
A resolution set too low, or a color mode mismatched to the original document, produces washed-out, overly dark, or low-detail scanned images.
A document not aligned against the flatbed's corner guide, or fed slightly crooked into the ADF, is the most common cause of a skewed scan image.
A Windows or macOS update can reset a default scanning app, break a driver association, or change a previously working destination setting without clear warning.
A scanner that simply doesn't appear in your scanning software's device list is almost always a connection or driver-detection problem rather than a hardware fault. For a wireless scanner not working, confirm it's joined to the same network as your computer, not a guest network or a different band. For a network scanner not found specifically after a router change, the scanner likely needs to be manually reconnected, since its previous network address no longer applies. A scanner not detected on Windows often resolves by removing the device entirely from Devices and Printers and re-adding it, which forces a clean driver reinstall; a scanner not detected on Mac responds the same way through System Settings → Printers & Scanners.
A "scanner busy" message when nothing else is actively scanning usually means a previous scan job didn't fully close out, leaving the scan software or driver in a locked state. Closing the scanning application completely, restarting the scanner's background service, and restarting the scanner hardware itself typically clears this. A slow scanner — one that takes an unusually long time to start or finish — is often related to a high resolution setting, a large color scan of a photo, or a wireless connection with limited bandwidth; switching to USB or lowering resolution for routine document scans usually restores normal speed.
Fig. 3 — Each scan destination fails for a different reason, which is why the same scanner can succeed at one and fail at another.
This feature depends entirely on the scanner having correct, current outgoing mail server (SMTP) details saved — an expired password, a changed port number, or a security setting like two-factor authentication on the email account will block it even though the scan itself completes normally.
If the destination folder was renamed, moved, deleted, or the scanning device lost write permission to it, the scan can complete but never actually land where you expect it.
A failed or corrupted PDF output is often caused by a mismatched PDF version setting, an oversized multi-page scan exceeding a size limit, or specific compression settings not supported by the destination software.
ADF scan problems most often come from worn or dirty feed rollers specific to the document feeder — separate from the printer's own paper tray rollers — which cause misfeeds, double-feeds, or jams partway through a multi-page scan job. Stapled pages, folded corners, or paper outside the feeder's supported thickness range make this worse. Flatbed scanning avoids feed issues entirely but is more sensitive to how the document is physically placed — not squared against the corner guide is the leading cause of a skewed flatbed scan — and to any dust, dirt, or fingerprints sitting on the glass surface itself, which show up directly in the scanned image.
A completely blank scanned page usually means the document was placed face-down instead of face-up (or vice versa, depending on the scanner), the wrong scan area was selected, or a hardware sensor issue is preventing the image sensor from capturing anything at all.
An unusually dark or high-contrast scan is often a brightness/contrast setting left at an extreme value in the scan software, or a color mode mismatched to the original document type.
A crooked scan image traces almost always back to how the physical document was placed — not squared against the flatbed's corner guide, or fed at a slight angle into the ADF.
Most scanners include a built-in calibration routine that corrects for color drift or sensor inconsistency that develops over time; running this periodically, especially after moving or extensively using the scanner, keeps colors and contrast accurate.
Windows Scan and third-party scanning software both rely on the WIA or TWAIN driver stack. If a scanner isn't detected, removing it entirely from Settings → Bluetooth & devices → Printers & scanners and reinstalling the driver fresh resolves most detection and "busy" errors.
macOS manages scanning through the same Image Capture framework used for printers. Removing the device from System Settings → Printers & Scanners and re-adding it resets a corrupted scan profile faster than troubleshooting it in place.
This points to a connection or driver-detection issue — a dropped Wi-Fi connection, a loose USB cable, or a corrupted driver — rather than the scanner itself being broken. Reinstalling the driver and confirming the network connection resolves most cases.
Printing and scanning use separate driver components even on an all-in-one device, so one can fail independently of the other. Reinstalling specifically the scanning driver, not just the printer driver, usually resolves this.
This usually means a previous scan job didn't fully close out, leaving the software or driver in a locked state. Closing the scan application fully and restarting the scanner clears it in most cases.
A high resolution setting, a large color photo scan, or a limited-bandwidth wireless connection are the most common reasons; lowering resolution or switching to USB for routine document scans usually restores normal speed.
Check whether the saved destination folder still exists at its expected path and that the scanning device has permission to write to it — a moved or renamed folder is the most common cause of this.
Scan-to-email depends on saved outgoing mail server (SMTP) credentials; an expired password, changed port, or new security setting like two-factor authentication on the email account is the most common reason this specific feature stops working.
This usually comes from a mismatched PDF version or compression setting, or an oversized multi-page scan exceeding a size limit set by the destination software.
Remove the scanner driver completely rather than reinstalling on top of the old one, then install the latest version directly from the operating system's built-in device setup.
Confirm it's joined to the same network band as your computer, not a guest network, and reconnect it manually if your router was recently restarted or replaced.
This is usually caused by the document being placed face-down instead of face-up (or the reverse, depending on the model), the wrong scan area selected, or occasionally a sensor issue.
Check the brightness and contrast settings in your scan software, and confirm the color mode (color, grayscale, black-and-white) matches the type of document you're scanning.
This almost always comes down to how the document was physically placed — not squared against the flatbed's corner guide, or fed at a slight angle into the automatic document feeder.
Worn or dirty feed rollers specific to the ADF, stapled pages, or originals outside the feeder's supported paper thickness are the most common causes.
Calibration corrects for color drift or sensor inconsistency that develops over time. Running it periodically, especially after moving the scanner or heavy use, keeps colors and contrast accurate.
This points to a setting or driver issue specific to that computer — an outdated driver, wrong destination folder, or scan software configuration — rather than a fault with the scanner or network as a whole.
Yes — firewalls and antivirus software occasionally block the specific network ports scanning uses, particularly right after a security suite updates and resets its default rules.
A new router typically means a new network name and set of assigned IP addresses; the scanner needs to be manually reconnected rather than assuming it will rejoin automatically.
Yes — use a soft, lint-free cloth, lightly dampened if needed, to clear dust, fingerprints, or debris from the flatbed glass, which otherwise shows up directly as streaks or shadows in every scan.
Photos typically need a higher resolution and a full-color mode to capture detail accurately, while documents scan faster and smaller in grayscale or black-and-white; using the document-appropriate setting for a photo produces noticeably lower quality.
If the driver is freshly reinstalled, the network or USB connection is confirmed stable, the destination settings are correct, and the scanner still fails identically on more than one computer, a genuine hardware fault — such as a failing image sensor — becomes more likely.
Still can't get a scan through? Check the related guides above for network, driver, or print-side issues.
"Scanner not working" is rarely one single problem — it's a label covering connection failures, driver errors, scan software glitches, and destination misconfigurations that each need a different fix. Confirming the connection, reinstalling the scanner driver, and checking exactly where the scan is supposed to end up — a folder, a PDF, or an email inbox — resolves the overwhelming majority of scan errors, whether you're scanning from a flatbed or an automatic document feeder, on Windows or on Mac, over Wi-Fi or by USB.