Multi-page ADF completes but PDF starts with last page. A partial failure matters: one capability still functions, while a closely related step does not. This guide focuses on isolating that difference in printers and scanners, not on indiscriminate resets. Use the known-good behavior as your control, change one variable at a time, and retest the original scenario after each intervention.
First, reproduce the difference
Baseline test: Scan three numbered sheets to separate image files as a baseline. Record the current device model, OS or firmware version, and whether this occurs with one file, account, network or source. A reproducible contrast is more informative than a vague message such as “not working.” If the control fails too, stop treating this as a feature-specific problem and investigate the shared dependency first.
Why it can happen
| Hypothesis | Evidence worth checking | Next decision |
|---|---|---|
| ADF face-up/face-down load orientation | Repeat the same action under a controlled alternate state and record the exact difference in outcome. | If the control still works, focus on the affected path rather than resetting the whole device. |
| Reverse-order option in scan software | Record the installed firmware or app version, then compare behavior before and after a supported update or clean reopen. | If this condition is not present, leave the associated setting unchanged. |
| PDF merge setting reverses stack | Repeat the same action under a controlled alternate state and record the exact difference in outcome. | Only escalate to this branch if the simpler comparison did not explain the failure. |
Before any changes
Protect your setup: Keep source files until merged PDF is verified. Check the model guide before opening covers, cleaning parts or changing consumables. Let hot printer components cool and keep original documents available.
Three repair routes
Route A — Correct the observable mismatch
Load pages per ADF diagram and choose correct page sequence in scan utility. Start only after capturing the baseline. When the recommended control is not present on your model, look for its supported equivalent in the product documentation rather than following screenshots from another version.
Return immediately to the failing task and check whether the outcome changed. If it did, preserve the working setting and avoid piling on additional changes. If it did not, undo the change where appropriate before moving to deeper checks.
Route B — Test the underlying dependency
Compare simplex and duplex scan order and application merge rule. This advanced comparison is worthwhile only if the simple check did not resolve the problem. The first two possibilities to separate are ADF face-up/face-down load orientation and reverse-order option in scan software. Do not interpret their presence as proof of a diagnosis; a compatible device and a partially failed service may coexist.
Route C — Handle a limitation or persistent fault
A third explanation is PDF merge setting reverses stack. Check whether the feature requires particular hardware, account privileges, region settings or source formats. When a feature is unsupported, there may be no legitimate settings-only fix; use the vendor-documented alternative rather than an unsafe workaround.
Step-by-Step Troubleshooting
Follow the Beginner steps first. Advanced steps are for isolating hardware, application or network-specific causes after a safe baseline test.
Confirm the boundary
Multi-page ADF completes but PDF starts with last page. Do not assume this is a complete outage. Scan three numbered sheets to separate image files as a baseline. Keep the account and connections unchanged between attempts.
Capture a useful baseline
Write down the affected model, software version, active input and when this started. Scan three numbered sheets to separate image files as a baseline. A working comparison tells you which part of the chain is still healthy.
Use the least disruptive correction
Load pages per ADF diagram and choose correct page sequence in scan utility. Apply one supported change at a time; stop if your model uses a different setting or does not advertise the feature.
Confirm the expected outcome
Resulting PDF opens in 1-2-3 order with page contents intact. Try the original failing action again, not an unrelated easier test; retain the old setting until you know the change helped.
Test the first dependency
Investigate whether ADF face-up/face-down load orientation. Specifically, repeat the same action under a controlled alternate state and record the exact difference in outcome. Compare the result with the working baseline from the beginner route.
Separate another possible cause
Assess whether reverse-order option in scan software. For this branch, record the installed firmware or app version, then compare behavior before and after a supported update or clean reopen. Do not change that configuration unless the evidence supports it.
Inspect the third branch
Compare simplex and duplex scan order and application merge rule. Also consider PDF merge setting reverses stack. Record the exact point of failure and check product-specific support limits.
Validate and plan a rollback
Resulting PDF opens in 1-2-3 order with page contents intact. Keep source files until merged PDF is verified. If the last change made matters worse, restore it and request supported assistance with a redacted troubleshooting summary.
Verify the result
Success looks like this: Resulting PDF opens in 1-2-3 order with page contents intact. Run this check on the same device and account that originally failed. A different device passing is useful as a comparison, but it does not prove the original issue is fixed.
What to check if it still fails
Before contacting support, collect the exact model and version, the outcome of the baseline test, and whether the controlled correction changed anything. Keep passwords, private media, account identifiers, serial numbers and network keys out of screenshots or shared logs. Keep source files until merged PDF is verified.
Solution Checklist
Frequently asked questions
Should I reset the entire device?
Not at this stage. Scan three numbered sheets to separate image files as a baseline. A reset can erase useful state and is not justified when a specific path can still be isolated.
Which detail should I give support?
Report the exact symptom and the outcome of the targeted test: Resulting PDF opens in 1-2-3 order with page contents intact.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.