Why Is My Scanner Not Detected on Windows 10 and What to Check?

If Windows 10 cannot see a scanner, a common troubleshooting order is to check power, USB or network reachability, device recognition, driver, then app settings. Work through them in that sequence. If you skip ahead, you often waste time on the wrong fix and end up reinstalling software that was never the problem. This guide gives you a fast checklist for USB and network scanners so you can isolate the failure point and fix the right layer first.

Detection decision table

Symptom	Likely layer	Exact check	Next action
USB scanner is plugged in, but nothing appears in Windows 10	USB connection	Confirm power, try a different USB port, and avoid a front-panel hub if possible	Move to a rear motherboard port, then reopen Printers & scanners
Wi-Fi scanner is on, but discovery never finishes	Network discovery	Check the scanner IP address and whether the device answers ping on the same network	Confirm the router sees it, then add it by IP if discovery fails
Printer prints, but scan buttons and scan apps fail on an all-in-one	Scanner-only driver or imaging stack	Look for a separate imaging driver package or a warning icon in Device Manager	Install the manufacturer package for the exact model
Scanner should be local, but Windows gives no scan choices	Windows service	Check Windows Image Acquisition (WIA) and Shell Hardware Detection	Set both to Automatic and start them if stopped
Device appears in Device Manager with a warning icon	Driver	Open Imaging devices and check for yellow exclamation marks or an unknown device	Update or reinstall the correct manufacturer driver
Automatic discovery fails, but the scanner is known to work	Windows add-device flow	Use Settings > Bluetooth & devices > Printers & scanners, then Add device	Try the manual add link if Windows does not find it

📊 Windows 10 can use Settings > Bluetooth & devices > Printers & scanners to add scanners. Source: Microsoft.

Why is my scanner not detected on Windows 10 even though it is plugged in?

A plugged-in scanner can still fail for four different reasons: the USB path is bad, Windows cannot enumerate the device, the driver is wrong or missing, or the scanning service is stopped. Separate those layers before reinstalling software. The fix depends on where detection breaks.

Start with USB-local scanners

For a local scanner, begin with the physical path. Windows recommends plugging it in through USB and turning it on, and USB faults are a frequent cause of scanner detection problems. Try a different cable, then a different port. Prefer a rear motherboard port over a front panel jack or hub.

After that, open Settings > Bluetooth & devices > Printers & scanners and see whether the device appears there. If it does not show up there, the problem is still below the app layer.

Separate driver faults from service faults

If the scanner shows in Windows but cannot scan, the failure may be in the driver or the service path. Windows 10 and 11 scanner issues can be caused by a missing WIA driver, an incompatible driver, or a disabled scan service. Check Device Manager and Services before you open the scan app.

Separate network scanners from local scanners

Wi-Fi and Ethernet scanners follow a different path. Discovery depends on the scanner’s IP address, network reachability, and Windows finding it on the same network. Windows may take a few minutes to search for network scanners, so do not treat a slow search the same way you would a dead USB port.

Say your desktop printer-scanner combo prints from a USB cable, but the scan tab never appears. That often points to a scanner-side driver or service problem, while the print side still works because it uses a different stack. In that case, the printer being fine does not rule out a scanner fault.

Scanner not detected on Windows 10: quick checks

Start with power, cable, port, then Windows detection. That order catches the common physical problems before you spend time on drivers. If the scanner is local, a stable USB path matters more than software cleanup at the start.

1. Check that the scanner is powered on and ready.
2. Reseat the USB cable at both ends.
3. Try a different USB port.
4. Open Settings > Bluetooth & devices > Printers & scanners.
5. Look for the scanner or the all-in-one printer entry.
6. If it still does not appear, move to services and Device Manager.

Suppose a flatbed scanner is connected through a 6-foot cable into a front USB port on a dock. If Windows misses it, move the cable to a rear port on the PC itself before changing drivers. That single change often separates a dock or hub problem from a true scanner fault.

How do you check Windows services?

Two services matter most here: Windows Image Acquisition (WIA) and Shell Hardware Detection. Both should be running and set to Automatic. WIA is commonly used as the link between scanning hardware and applications, and it depends on Remote Procedure Call (RPC).

Check Windows Image Acquisition

Open Services, find Windows Image Acquisition (WIA), and confirm that its status is Running and its startup type is Automatic. If it is stopped, start it. If startup type is Manual or Disabled, change it to Automatic. A stopped WIA service can block scanning even when Windows sees the device.

Check Shell Hardware Detection

Find Shell Hardware Detection and verify the same two things: Running and Automatic. This service helps detect scanners and other imaging devices. If it is stopped, Windows may fail to react when the scanner is connected or powered on.

Check the RPC dependency

WIA depends on Remote Procedure Call (RPC). If RPC is broken, WIA will not help, even if it looks enabled. That makes WIA a useful checkpoint, not the whole story. If both services are already running and scanning still fails, move on to the driver layer.

How do you tell if it is a driver issue?

Use Device Manager to check Imaging devices and look for warning icons. A yellow exclamation mark, an unknown device entry, or a scanner that appears but will not initialize usually points to a driver problem, not a cable problem. That is the cleanest way to separate driver trouble from a dead connection.

Check Device Manager first

Open Device Manager and expand Imaging devices. If the scanner is listed with a warning icon, Windows has seen hardware but does not trust the driver state. If it is absent entirely, return to power, cable, port, network reachability, and services before you reinstall anything.

Know when Windows driver support is enough

Windows Scan, the Microsoft Store app, can handle basic scanning for some devices. That is often enough for a simple flatbed scanner or a model that supports standard Windows imaging support. If the device appears and scans in Windows Scan, the problem may be the vendor app rather than the scanner itself.

Know when the manufacturer package is required

The manufacturer driver package is often required for full functionality, especially for some multifunction printers. It should match the exact model and the Windows version. If printing works but scanner features, page feeders, or hardware scan buttons do not, the inbox Windows driver may be too limited for that device.

A common first-timer mistake is reinstalling every app before checking Device Manager. That can hide the real clue. A warning icon, a missing Imaging devices entry, or an unknown device gives you better evidence than a fresh reinstall does.

How do you add a scanner manually?

Windows 10 lets you add scanners from Settings > Bluetooth & devices > Printers & scanners. If automatic discovery fails, use the add-device flow first, then the manual add link. That path is the fastest fallback when Windows can see the network or USB path only after a prompt.

Use the Add device flow

1. Open Settings > Bluetooth & devices > Printers & scanners.
2. Select Add device.
3. Wait while Windows searches for a local or network scanner.
4. If the scanner appears, select it and finish the setup prompts.

Use the manual add fallback

If Windows does not find the scanner, choose the manual add link. Microsoft provides that fallback when automatic discovery fails. Use it for a local scanner that is already powered and connected, or for a network scanner whose IP address is known but not discovered on its own.

Confirm the scanner appears in Windows Scan

After the device appears in Printers & scanners, open Windows Scan. That gives you a simple test path that avoids vendor extras. If Windows Scan works, the core Windows imaging path is probably healthy.

Why does my printer work but the scanner is not detected?

Printing and scanning do not always share the same driver path. On an all-in-one device, Windows may detect the printer portion while the scanner portion fails because the imaging driver, WIA service, or manufacturer package is missing or stopped. This is a common split fault, not a contradiction.

Check the scanner side separately

Look for the device in Device Manager under Imaging devices, then check whether it appears in Printers & scanners. If print jobs succeed but the scan side is absent or broken, focus on the scanner driver and imaging services, not on the print queue.

Use button-initiated scan as evidence

One useful clue is whether the device’s own scan button works. If the hardware button starts a scan but Windows does not detect the device in software, the scanner path may be partly alive while Windows integration is broken. That often points to software, service, or model-specific driver support.

Network scanner checks

For Wi-Fi or Ethernet scanners, the main questions are whether the scanner is on the same network, has a valid IP address, and can the PC reach that IP. Discovery depends on the network stack first. A scanner that is powered and visible on its own screen can still be invisible to Windows if the network path is wrong.

Verify the scanner on the network

Check the scanner’s network status screen or front panel for its IP address. Then confirm the PC is on the same subnet or at least the same local network segment. If the scanner moved to a different band, VLAN, or guest network, Windows discovery may fail even though the device is on.

Use ping and router confirmation

If you have the IP address, use ping to see whether the scanner answers on the network. If it does not answer, check the router or access point list to confirm the scanner is actually connected. Windows may search for network scanners and take a few minutes, so give discovery time after the network check.

When to add by IP

If the scanner is reachable by IP but still not discovered automatically, use the manual add path in Settings. That is the clean fallback for network scanners because it bypasses discovery and tests direct reachability instead.

Frequently asked questions

What should I check first when Windows 10 can’t find my scanner?

Check power, the USB cable or network connection, and whether the scanner appears in Settings > Bluetooth & devices > Printers & scanners. If it is a local scanner, use a different USB port. If it is networked, verify the IP address and reachability first.

How do I tell if the problem is the scanner, USB cable, or Windows service?

If the scanner stays absent from Windows after a different USB port and cable, the physical path is suspect. If it appears in Windows but will not scan, check WIA and Shell Hardware Detection. If Device Manager shows a warning icon, the driver is the stronger suspect.

How do I manually add a scanner in Windows 10?

Go to Settings > Bluetooth & devices > Printers & scanners, select Add device, and wait for Windows to search. If discovery fails, use the manual add link Microsoft provides. After the device appears, open Windows Scan to confirm basic scanning works.

Do I need a manufacturer driver or is the Windows driver enough?

Windows Scan and inbox support may be enough for basic scanning on some devices. For many multifunction printers, the manufacturer package is needed for full features and should match the exact model and Windows version. If print works but scanning tools or buttons do not, install the vendor package.