Fujitsu fi-8170 Card Damage, Vertical Lines, PaperStream Capture Issues, and ADF Error Problems

Fujitsu fi-8170 Card Damage, Vertical Lines, PaperStream Capture Issues, and ADF Error Problems

The Fujitsu fi-8170 shows up in two very different kinds of problems. In office use, the complaints center on ADF errors and software behavior inside PaperStream Capture. In collector and resale workflows, the problems are much more specific: cards picking up pressure marks, thin vertical lines appearing on every scan, sleeves crinkling in the feeder, and setup changes that fix one issue while creating another. 

The cases below focus on how those failures actually played out once users stopped treating them as simple settings mistakes and started testing the scanner physically.

Problem: The scanner left pressure lines or imprints on trading cards

What users observed: Users scanning Pokémon and sports cards reported that the fi-8170 was leaving two visible pressure marks that matched the locations of the ADF guide components. These marks were not obvious straight on, but they could be seen under angled light and were treated as real damage on higher-value cards. The same thing happened even when cards were run in penny sleeves, which meant the sleeve was not providing enough protection to stop the imprinting.

What was tried: Users tested raw cards, sleeved cards, and repeated scans on lower-value cards to see whether the marks were random or consistent. Some also started looking at whether the wheel and guide assembly could be modified or removed. That did not begin as cosmetic troubleshooting. It began because the scanner was physically changing the cards.

How this played out: The issue did not disappear just because the cards were sleeved. In the reports that stayed unresolved, the scanner remained risky enough that some users considered returning it rather than trusting it with valuable cards. In other words, this was not just a bad image-quality case. It was a card-handling problem first.

Problem: Fujitsu fi-8170 leaving thin vertical lines or card marks

What users observed: Several users changed the top wheel or roller setup so they could run penny sleeves or top loaders more easily. After that, the scanner would take those items, but a thin line started appearing on the scans or the cards themselves. In one account, removing the spring-loaded guides simply moved the line from the middle of the card to the side instead of fixing it. In another, removing the wheels appeared to let the black plastic mechanism press directly into the card path.

What was tried: Users removed the top roller, removed the small black guide pieces, reassembled them, and tested different orientations for raw cards, penny sleeves, and top loaders. Some also changed feed behavior so the scanner would not try to pre-pick or pull cards aggressively, and instead fed cards one at a time.

How this played out: The most specific outcome reported was that taking the wheels out could actually make the pressure-line problem worse, while putting the wheels back in stopped the damage on raw cards. That created a tradeoff: raw cards scanned more safely with the wheels in place, but penny sleeves could no longer pass through cleanly because the sleeves crinkled or caught. The fi-8170 did not end up with one simple “correct” setup. The hardware change that helped one card format often created a different problem for another.

Problem: PaperStream Capture stopped allowing profile changes in the middle of a scanning process

What users observed: Users reported that after a recent update, they could no longer switch scanner profiles in the middle of an active PaperStream Capture job. The older behavior had allowed additional pages to be added under a different profile during the same process. After the update, the second Add action no longer offered a different profile and only reused the one that had started the batch.

What was tried: The first reaction was to look for a missing option inside PaperStream Capture itself. Once that no longer seemed possible, attention shifted to whether the software version or model-specific support had changed. Alternate capture software was also considered in place of PaperStream Capture for workflows that needed more flexible profile handling.

How this played out: No direct in-app restoration of the old behavior was documented in the material you provided. The issue stayed tied to changed software behavior after update, and the only concrete workaround discussed was moving to different software when that profile-switching workflow was essential.

Problem: F4:C2 error appeared on ADF front or ADF back and did not clear

What users observed: Users setting up the fi-8170 reported an F4:C2 error pointing to either the ADF front or ADF back. Power cycling the scanner and cleaning it did not make the error go away, which made the issue feel more serious than a simple feed hiccup.

What was tried: The scanner was turned off and on repeatedly, the visible feed path was cleaned, and the ADF area was checked for anything obvious. When that changed nothing, the next suggestion was to open the ADF fully and inspect for tiny scraps, dust, or sensor contamination deeper in the path.

How this played out: The reported direction here was that the error stayed tied to obstruction or sensor trouble inside the ADF path rather than to software setup. Once the visible cleaning and restart path failed, the problem had already moved beyond the normal quick-fix stage. In the material you provided, no confirmed self-service fix was reached after that point.