Ricoh Scanner Not Working on Windows 11, Not Detected, Scan to Folder Not Working, and USB Scanner Problems

Ricoh scanner problems on Windows 11 usually show up in a split state. The device may still appear in Printers & scanners, yet the actual scan utility still says no scanner is found. A multifunction Ricoh may still print normally, yet scan to folder fails only on Windows 11 PCs. 

On USB-connected fi and SP models, the scanner can even stay physically connected while Windows 11 24H2 changes the way the device is identified and the scanner name no longer appears correctly in capture software. That is why these cases often get mistaken for generic scanner not detected on Windows complaints when the actual break is much narrower.

Problem: The scanner does not appear correctly after Windows 11 24H2

What users observe: USB-connected Ricoh fi and SP scanners can stop appearing correctly after Windows 11 version 24H2 or Windows 11 LTSC 2024. In the reported cases, the scanner is still attached, but the capture software shows “WIA No Friendly Name” or fails to display the scanner name properly. This is one of the clearest not detected on Windows branches because the scanner is not fully gone, but the device identity path is broken enough that the scanner becomes unusable.

What was tried: Users typically restart the scanner, reconnect USB, rerun the same capture utility, and reinstall the ordinary Ricoh software path. Because the device still appears partly present, the first instinct is often to keep treating it like a simple connection problem.

How this played out: The scanner path only stabilizes after the Windows 11 24H2 branch is handled directly. On this branch, the useful fix is bringing Windows onto the corrected update level and then restoring the Ricoh scan path from there, instead of repeatedly reinstalling the same older path on the broken 24H2 state. 

Problem: The scanner appears in Windows, but the software still says no scanner is found

What users observe: Windows still lists the scanner under Printers & scanners or Imaging devices, yet PaperStream or the scan utility still reports that no scanner is found. That makes the scanner feel only partly installed, which is why users often keep chasing the wrong layer first. This branch overlaps closely with scanner detected but cannot scan, not just scanner not detected.

What was tried: Users reinstalled the software, rechecked the USB connection, restarted Windows, and retried the same Ricoh capture path. Because the scanner still appears somewhere in Windows, they often assume the driver is already correct and keep working in the application instead.

How this played out: The cases that recovered did so after the Windows device path was rebuilt more directly. Updating the device driver from Device Manager using the correct Ricoh/PaperStream driver path was the step that restored actual scanning in these cases. 

Problem: Scan to folder does not work on Windows 11

What users observe: A Ricoh multifunction device may still print normally and still scan locally, yet scan to folder fails only when the destination is a Windows 10 or Windows 11 computer. In one solved case, the same Ricoh scanned to a Windows 7 computer without trouble, but would not scan to a newer Windows machine. That makes the device look selective or inconsistent when the real issue sits in the SMB support path.

What was tried: Users usually begin by rebuilding the share, checking permissions, re-entering credentials, and even retrying SMB1 because the destination PC looks like the variable that changed. They also commonly assume the copier firmware is already current because the firmware update tool reports success quickly.

How this played out: The solved cases only changed once the Ricoh side was brought up to the SMB level Windows 11 actually expected. In the reported MP 4054 case, the working fix was a proper firmware update that finally exposed the Advanced Settings section for SMB v2/v3 and port 445. 

Problem: The scanner stops working because Windows security software blocks the scan path

What users observe: Some Ricoh scan failures on Windows 11 look like copier-side problems even though the copier settings are fine. Printing still works, the device is reachable, and the address book is correct, but scanned files do not arrive. This is one of the branches that gets mislabeled as a Ricoh problem when the real block is sitting on the Windows PC.

What was tried: Users often continue adjusting the Ricoh side first — rechecking SMB settings, recreating the folder, and retrying the same scan destination — because the copier is the visible device in front of them. In the reported Windows 11 cases, those attempts did not change anything.

How this played out: The working fix was on the PC side: security software was blocking the scan path. Once that software allowed the scan connection again, the Ricoh resumed scanning normally. This matters because it turns what looks like a scan not working or scan to folder not working copier failure into a Windows-security issue instead.

Problem: The scanner works on one Windows 11 machine, but not on another

What users observe:The same scanner or MFP works from one Windows 11 system but fails from another. That usually means the device itself is not the real problem. In the reported Windows 11 scan cases, differences in the destination PC — especially network profile, SMB support, driver binding, or security software — were what separated the working machine from the failing one.

What was tried: Users re-entered the same Ricoh settings repeatedly because the copier was the one shared piece between the working and non-working setups. They also retried the same login and folder details on the failing PC without changing the Windows-side environment around it.

How this played out: The real fix was to treat the Windows 11 destination as the variable, not the Ricoh. In the solved cases, that meant correcting SMB support and firmware on the copier where needed, but also correcting the Windows-side profile, folder environment, or security block on the specific PC that was failing.