Scanner Detected but Cannot Scan, Unavailable Workflows, and Partial Device Failures

A scanner does not need to disappear completely to become unusable. In many of these cases, the device still showed up in Windows, still powered on normally, and in some situations even launched the scanning software when a hardware button was pressed. That partial visibility made the failure especially confusing. From the system side, the scanner looked present. From the user side, it still could not actually scan.

What made these cases difficult was the split between detection and real functionality. Sometimes the scanner was visible in Windows but rejected by the capture software. Sometimes printing continued while the scanner portion of a multifunction device effectively vanished. In other cases, the flatbed worked while the feeder path failed, or the scanner could still be found but another process had already locked it. 

The examples below focus on those in-between states where the scanner had not disappeared entirely, but the scanning workflow still broke down.

Problem: Scanner detected but software reports “no scanner is connected”

What users observed: On the Ricoh fi-8170, the scanner appeared in Windows settings and pressing the physical scan button launched PaperStream Capture as expected. Even with that level of system response, the software still reported that no scanner was connected. To the user, the device looked close to working, which made the rejection inside the software seem contradictory.

What was tried: The USB connection was confirmed, the expected software was installed, and normal setup checks were repeated. Nothing in the visible setup suggested the scanner had failed to install or had lost power.

How this played out: The scanner only became usable after it was switched to a compatible driver path from a closely related Fujitsu fi-series model. Once that change was made and the system restarted, PaperStream Capture recognized the scanner correctly. The device had not been absent. The active software path simply had not matched the way the capture software expected to bind to it.

Problem: Scanner detected but cannot scan after Windows 11 Update

What users observed: On the Fujitsu fi-7160 and Ricoh fi-8170, Windows 11 24H2 could leave the scanner in a state where it had previously worked but now could not be used properly. Systems began reporting that no scanner was available, even though the hardware itself had not changed and the installation path had already been working before the update.

What was tried: Users reinstalled software, tested different install variants, and repeated the same setup while the updated OS remained in place.

How this played out: The failure stayed tied to the updated Windows environment rather than clearing through ordinary reinstall attempts. In one fi-8170 case, scanning returned only after a later cumulative update. In fi-7160 cases, users were left with only a limited workaround tied to an alternate installed path and a stable USB connection.

Problem: MFP prints, but scanner option doesn’t work

What users observed: On the HP LaserJet 3055 and HP LaserJet M1005 MFP, printing could continue normally while Windows failed to expose the scanner portion to scanning applications. The multifunction device remained usable in part, which made the problem easy to misread as an application issue rather than a scanner-side failure.

What was tried: Users reinstalled packages, tried alternate software paths, and attempted to add the scanner manually. On the M1005, users also repeated setup after preparing software on another OS and bringing it over to the target system.

How this played out: On the HP LaserJet M1005, scanning only appeared after the full software was installed directly on the same Windows 10 system. On the 3055, the scanner often remained unavailable on Windows 10 even after repeated attempts, while printing continued to work. In both cases, the device had not fully disappeared. It had become partially functional.

Problem: Scanner detected but Scan-to-PC doesn’t work

What users observed: On the Ricoh IM 550, PCs that had previously received scans stopped doing so after a Windows 10 update, while the printer’s other functions remained available. This made the issue look highly selective. The machine still printed, and nothing about the basic device state suggested a total failure.

What was tried: Users shifted attention to Windows-side scan and sharing features rather than treating the device as fully broken. The environment around the scan workflow was checked more closely than the printer itself.

How this played out: The failure only moved once Windows-side feature dependencies were brought back into alignment. The device still existed and still communicated in other ways. What had broken was the specific scan-receive workflow.

Problem: Scanner is detected, but reports “Scanner Occupied”

What users observed: On the Fujitsu fi-7460, users saw “scanner occupied” or similar unavailable states even though the scanner was powered on and connected. Because the software trying to use the scanner was being denied access, the device could seem missing or broken from that program’s point of view.

What was tried: Early troubleshooting stayed focused on connection and detection because the scanner appeared unavailable to the application.

How this played out: The scanner only became available again after closing PaperStream ClickScan, Button Event Manager, or other open settings windows that were already holding the device. The scanner had not disappeared. It had simply already been claimed by something else.

Problem: Scanner detected and flatbed works, but ADF scan does not

What users observed: On the HP LaserJet MFP M234sdw, the automatic document feeder stopped scanning while the flatbed scanner, copying, and printing could still continue working. That left the scanner only partly broken, which made the device look less like a full scanner failure and more like a workflow-specific one.

What was tried: Users cleaned feeder rollers, checked firmware, and repeated single-page tests to see whether the feeder path would come back under lighter use.

How this played out: No confirmed recovery was documented. The scanner remained partly usable, but the ADF scan path did not return to normal operation in the case notes.

Problem: Scanner works in one application, but not in another 

What users observed: On the Fujitsu fi-7160, duplex scanning worked outside Laserfiche but not within it. Inside the application, the duplex option either disappeared or reverted to single-sided behavior. From the user side, the scanner looked capable and detected, yet still unusable for the one workflow that mattered.

What was tried: Users adjusted feeder and duplex settings inside the software and repeated the same scanning path under different configurations.

How this played out: No confirmed full resolution was documented. The scanner remained usable elsewhere, which made this a workflow-specific failure rather than a total loss of detection or hardware function.