A physical scanner button can be assigned a different PaperPort profile from the one selected on screen. If the same scanner produces a different format or naming pattern depending on how you start the job, compare the two routes before replacing the driver.
The procedure below is based on PaperPort 14.7's documented button assignment. Its legacy Windows examples do not establish support for every current operating system or scanner. Use the manufacturer's supported event controls and the help appropriate to your installed environment.
Compare two small scans
Use one harmless page and an approved test folder. Scan once from inside PaperPort using the selected profile, then once using the physical button. Record format, destination, filename and page appearance. The point is to identify a route-specific difference without changing acquisition settings in several places.
The official Scanner Buttons options lists scanner, button and assigned profile. A multi-button device can have more than one assignment, so inspect the exact button pressed rather than only the device name.
Confirm which application receives the event
A physical button may launch a manufacturer's utility or another application instead of PaperPort. Establish what actually opens when it is pressed. Changing a PaperPort profile will not control a separate utility that owns the event.
Keep the on-screen profile label
Write down the profile shown in the Scan or Get Photo pane. Do not rely on memory after switching windows. A name such as “Document” can hide different settings across installations, so inspect its actual output options when comparing results.
Review the two-stage assignment
Tungsten's button assignment instructions describe first assigning PaperPort to the scanner event, then choosing a scan profile. On managed equipment, ask the administrator to review the supported event configuration rather than following an obsolete Control Panel screenshot literally.
Change only the intended button
If a device has separate scan, copy and email buttons, do not redirect all of them casually. Other staff may rely on their current behavior. Record the previous assignment and agree the one that should invoke the PaperPort workflow.
Match the profile to the business task
Select the intended format and filing behavior. A button configured for single-page images is unsuitable for a process expecting one searchable multi-page PDF, even though both paths successfully acquire the paper. Check the profile rather than treating any visible scan as success.
| Difference between routes | Where to inspect |
|---|---|
| Different application opens | Manufacturer-supported button event mapping |
| Same application; different format | Button's assigned PaperPort profile |
| Different names or separation | Profile Output and SET options |
| Both routes fail to acquire | Scanner connection and supported acquisition setup |
Preserve working device configuration
Avoid reinstalling software when a confirmed assignment difference explains the result. If an updated driver is genuinely required, obtain it only from the manufacturer's official support route for the exact model and supported operating system. Do not use a third-party driver repair package.
Note the scanner dialog's role
If the manufacturer's acquisition dialog appears, review which settings it controls in the installed workflow. PaperPort's profile and the scanner's own interface are not necessarily interchangeable sources of acquisition settings. Keep a note of which one was used in each sample.
Avoid changing shared profiles silently
A profile may be used by an on-screen operator as well as a button. If you change its output settings, both routes may be affected. Where supported and appropriate, use clearly named task-specific profiles instead of repurposing a shared one without notice.
Verify the final button operation
Repeat the harmless sample with the physical button. Open the resulting file and confirm format, page count, legibility and destination. Then perform the on-screen route again to make sure its intended behavior remains available.
Our OneDrive OCR guide covers a separate mobile capture workflow. It can help compare output requirements, but it does not configure the physical scanner event.
Repeat the check after an approved scanner software update, because an event assignment may need review even when ordinary on-screen scanning still works.
The physical scan button can select a different naming profile. See the companion guide on PaperPort Scan Names: Dates and Sequential Counters.
Keep a concise operating note with device model, button, receiving application and profile. The useful outcome is predictable behavior whichever authorized route staff use, with the button's purpose clear before an important batch is scanned.
