Check the scanner separately under Windows Printers & scanners, then compare one simple scan using Windows Scan or the manufacturer’s supported app. If printing works but scanning does not, verify scanner software, connection type, ARM support, and Protected Print compatibility before reinstalling anything.
“Scanner not found” can mean Windows does not discover the device, a particular app cannot use it, or a printer's scan-to-computer button cannot locate its destination. Begin by recording where the message appears. Treat those as separate tasks so a working printer does not conceal a scanner compatibility problem.
Define one scan you can verify
Use a plain, non-sensitive page and start with the flatbed if the device has one. Record the exact model, USB or network connection, Windows version, computer architecture, and app name. Note whether scanning ever worked on this PC and what changed immediately before it stopped.
For example, a multifunction device may print invoices but fail to scan a receipt from a Windows app. Printing success establishes a print route; it does not demonstrate that a scanner driver, network scan protocol, or app is available. Avoid reinstalling the working printer before checking the scanning side.
Choose the correct branch
| Observation | Check next | Keep in mind |
|---|---|---|
| No device appears in Windows | Power, connection, and Add device | Discovery must work before app settings help |
| Printer appears without scanner settings | Model support and scan installation route | Print-only discovery is not full support |
| Windows Scan works, vendor app fails | Vendor app version and selected device | The scanner can work through at least one route |
| PC scanning works, device button fails | Manufacturer's scan-to-computer setup | Push scanning is a separate workflow |
| Failure began on a new ARM PC or after a print-mode change | Architecture and Protected Print support | Older software may not apply |
1. Inspect the connection without resetting the setup
Wake the device and resolve any displayed mechanical or paper error using its manual. For USB, inspect both ends and compare a supported direct computer port rather than a dock. For a network scanner, confirm the intended network name on both devices.
Do not join the printer's Wi-Fi Direct network accidentally when your normal workflow expects the household network. If the device uses a work network, ask IT about discovery and permitted scan methods instead of disabling a firewall. Our connection guide explains the distinctions.
2. Check what Windows has actually installed
- Open Settings, Bluetooth & devices, then Printers & scanners.
- Find the exact device, including any multifunction printer entry.
- Open that entry and look for scanner-related settings.
- If the device is absent, use Add device while it is powered on and connected.
- Allow discovery to finish before retrying an application.
Microsoft's scanner installation guide explains this route and notes that an all-in-one scanner may appear under its printer name. When the automatic process does not identify it, use the documented manual or manufacturer-supported setup rather than guessing a device type.
3. Compare a basic scan with an appropriate app
If Windows detects the scanner, open Windows Scan or the manufacturer's supported application. Choose the exact device, the appropriate source such as Flatbed, and a destination you can find. Preview when available, then scan the test page and reopen the saved result.
Windows Scan's documented output choices are image formats including JPEG, PNG, TIFF, and Bitmap. Do not confuse failure to create a multipage PDF with failure to detect a scanner. A particular output format or document-feeder feature may require a different supported app.
HP's scanner connection guidance illustrates alternate scanning routes when its app does not work. Those instructions are for HP devices. If one route succeeds, record the app and source that worked before changing software.
4. Check newer compatibility boundaries
On an ARM-based Windows PC, consult the manufacturer's architecture-specific support statement. Brother's Windows 11 ARM page says software varies by model and identifies a USB limitation for its scanner driver and iPrint&Scan. That is a specific vendor statement, not a rule for all scanners.
If Windows Protected Print Mode was enabled, check scanning separately from printing. Microsoft's FAQ states that not every scanner is compatible and links to certification information. Review our change checklist; on a managed device, let IT decide any policy change.
5. Distinguish scan-to-computer from scanning on the PC
A scan started from the device's panel needs a supported destination workflow. If scanning from the PC works but that button fails, check the manufacturer's instructions for the panel feature and selected computer. Do not treat it as proof that Windows needs a replacement scanner driver.
Likewise, scan-to-email and scan-to-network-folder are separate device features. Their configuration belongs to the specific model and organization. Do not enter account credentials into an unfamiliar setup utility simply because it promises to make every scan mode work.
Verify the saved result, not only the progress window
If the scan finishes, open the selected destination and inspect the saved image. Confirm that it contains the test page and is not an earlier file with a similar name. A scan that completes but saves somewhere unexpected is a file-location problem; report that separately from a device the app cannot discover.
Common mistakes and when to stop
Common mistakes include selecting a stale duplicate, choosing a document feeder while the paper is on the flatbed, and expecting all apps to expose the same formats. Save successful comparisons so a later software update does not erase what you already learned.
Contact the manufacturer when its support list does not cover your model and architecture, or when no supported app detects a connected device. Contact IT for managed network scanning. Include exact error text, connection, architecture, working print results, and whether any scan app succeeded.
Editorial note: This guide is based on official documentation and does not claim hands-on compatibility testing. Support lists and scan app interfaces can change after the review date.
Keep these in mind
- Record where the scanner-not-found message appears before troubleshooting.
- Printing, PC-initiated scanning, and panel-initiated scanning are different workflows.
- Check model, connection, ARM architecture, and Protected Print support together.
Common questions
Why can I print but not scan?
Printing and scanning use separate software and capabilities. Check whether Windows exposes scanner settings and whether the model supports your app, connection, computer architecture, and print mode.
Does Windows Scan save directly to a multipage PDF?
Microsoft documents image output formats for Windows Scan. If multipage PDF is your requirement, check a manufacturer-supported application rather than interpreting a missing PDF option as a detection failure.
Should I disable Protected Print to restore scanning?
First verify the model’s scanning compatibility and the timing of the change. On managed devices, ask IT; a policy change should follow a documented compatibility decision, not guesswork.
Sources & further help
Prepared with AI assistance from the linked documentation. This is a source-led explanation, not a claim of hands-on testing across every device. Read the editorial policy.