If a duplex scan omits blank backs or creates unexpected empty pages, inspect both the scanner's duplex setup and PaperPort's profile processing. Hardware acquisition and post-scan page handling are different stages. A document that looks one-sided in the output may have been acquired differently or had pages removed afterward.
Use a disposable two-sheet sample with clear front-and-back labels. Include one intentionally blank side and record the expected output order. Keep the original paper nearby until you understand which stage changes the page count.
Define whether blank sides should be preserved
Some workflows want every scanned side represented, while others intentionally omit blank backs. Agree the requirement with the document owner before treating missing blanks as a defect. A deliberate omission can still be wrong for a process that uses page positions as references.
Write the expected sequence explicitly. For example, label the nonblank sides A-front, A-back and B-front, leaving B-back blank. This illustrative sample makes it easier to distinguish duplex acquisition from blank-page handling without exposing real business records.
Check the selected scan profile
Tungsten's scan-profile documentation describes profiles containing acquisition, image processing, OCR and output choices. Confirm which profile is selected in the Scan or Get Photo pane. A familiar profile name does not establish that its current settings still match the original purpose.
Inspect blank-page processing
The documented profile settings include image enhancement and blank-page handling. Record the current choice before changing it. A faintly printed page can be more important than a visibly dense one, so do not assume every page classified as blank is safe to discard.
Inspect where scanner settings are controlled
The documentation distinguishes using the scanner's interface from using PaperPort's available acquisition settings. Determine which route is active. Changing a setting in one place may not test the control you believe is governing the scan.
| Observed output | Question |
|---|---|
| Only front labels appear | Was duplex acquisition actually enabled and supported? |
| Blank side is absent but labeled backs remain | Is blank-page processing intentionally removing it? |
| Faint content is missing | Was a nonblank side treated as blank? |
| All sides exist in unexpected order | How does the scanner return duplex pages? |
Confirm the scanner's supported behavior
The scanning preparation guide explains the role of the device software and selected acquisition source. Use the manufacturer's official instructions for the exact scanner when checking duplex capability and driver settings. PaperPort cannot add a physical feeder feature that the device does not provide.
Avoid substituting an unofficial driver or following a procedure for a different scanner model. Record the model, connection and acquisition interface so support can identify the applicable configuration. A working printer function does not establish the duplex scanning setup.
Run one controlled comparison
Scan the labeled sample with the current configuration and record the page count and sequence. Then make one applicable authorized change and repeat. Keep both outputs distinct. Changing duplex selection, blank handling and output format together makes the result difficult to interpret.
Inspect the actual saved file, not only the preview thumbnails. Confirm whether every intended side is present and readable. For multipage output, verify boundaries and orientation as well as the total count.
Test faint and marked backs before a production batch
If blank removal is part of the intended workflow, include a side with a faint permitted mark in a separate sample. Establish the organization's acceptance criteria and review any available thresholds through the supported controls. Do not generalize from a clean blank sheet to all paper types.
Preserve required originals according to the organization's records policy. A successful sample does not justify discarding paper or source images before the full batch has been reviewed and accepted.
Save a profile with a clear purpose
Where your edition supports maintaining separate profiles, use names that describe the intended result, such as preserving every side versus a reviewed blank-removal workflow. Keep the main settings in a short procedure so another user can understand the choice.
If the error persists, report the scanner model, source, profile, duplex route and labeled sample result. Our PDF workflow comparison provides broader output context. For this issue, the useful outcome is an explained page count: every retained or omitted side follows the agreed acquisition and processing rules rather than an assumption about what the profile name means.
