Scanner ADF Not Feeding, Paper Pull Failures, and Misfeed Problems

ADF problems can be misleading because the scanner itself often still appears installed, powered on, and partly functional. In some situations, the flatbed continues working while the document feeder stops pulling pages entirely. In others, pages enter the feeder but skew, misfeed, or behave inconsistently across a batch, which makes the issue look intermittent rather than fully broken. These cases usually do not start with a total failure of the scanner. Instead, they show up as selective feeding problems where the device can still scan in some ways but no longer handles feeder jobs correctly.

The examples below focus on situations where paper would not move through the feeder properly, where scanning from the ADF became unreliable, or where document handling stayed inconsistent despite cleaning, resets, or normal setup checks.

Problem: Automatic document feeder will not scan even though the flatbed still works

What users observed: On the HP LaserJet MFP M234sdw, the automatic document feeder would not scan pages, while the flatbed scanner, copying, and printing all continued to work normally. This made the problem feel isolated to the feeder path rather than to scanning as a whole.

What was tried: The feeder rollers were cleaned, firmware updates were checked, and single-page tests were attempted to see whether the failure only affected longer document runs.

How this played out: No confirmed result was reported. The feeder remained unresolved, while the rest of the device continued functioning.

Problem: Every other sheet feeds incorrectly during batch scanning

What users observed: On the Fujitsu fi-7160, every second page exited the scanner skewed at an angle, while alternating pages fed normally. There were no error codes, which made the pattern harder to classify as a full feeder failure.

What was tried: Attention shifted away from drivers and toward the paper path, rollers, and feed behavior. Cleaning and maintenance were suggested because the failure repeated in a physical pattern rather than a software one.

How this played out: No confirmed outcome was documented. The every-other-sheet misfeed pattern remained unresolved.

Problem: Scanner handling changes depending on feed speed or transport mode

What users observed: On the Ricoh fi-8170, scanned items consistently developed a thin line or surface marking on the same side, even when items were sleeved. The issue followed the way materials moved through the scanner rather than the file or software used to capture them.

What was tried: Cleaning with compressed air and extensive changes to scan settings did not stop the behavior.

How this played out: The behavior changed only after low-speed feed mode was enabled. Once transport speed changed, the marking stopped, which showed that document handling through the feeder path was the deciding factor.

Problem: ADF path behaves like a jam or obstruction even when the document enters

What users observed: On older multifunction HP models such as the LaserJet 3055, document feeder handling could become difficult enough that clearing jams felt mechanically risky. One side of the ADF cover released while the other side felt stuck, making feeder access itself part of the problem.

What was tried: Users attempted to open the feeder carefully and inspect the path without forcing the mechanism.

How this played out: The behavior was treated as mechanical rather than software-related. The device could still function, but feeder access and jam clearing remained awkward and inconsistent.

Problem: Scanner available but not feeding

What users observed: Across feeder-related cases, the scanner was still detected by the system, and in some situations the flatbed remained usable. That made the device look only partially broken, especially when print and copy functions also remained available.

What was tried: Users usually started with cleaning rollers, checking firmware state, and repeating feeder tests with single pages or light batches.

How this played out: These cases rarely changed through reinstalling software alone. When improvement happened, it came from feed-path changes, cleaning, or mechanical handling rather than from anything in the install state.