This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Dear Microsoft,
Please before you push out a cumulative update do your due diligence and make sure it will not ruin critical functions. Many scanner products will not scan anymore and pop up with a WIA no friendly name error. Currently my company is having problems with Fujitsu scanners. We need this resolved quickly to avoid service disruption; what is your eta on a permanent fix for this that ISN'T rolling back the OS to the previous version. Due to vulnerabilities our security (rightly so) will not allow us to revert.
We do have a company that seems to be working (Epson) this may be a good place to start your troubleshooting as to why this isn't working with other companies (brother, ricoh to name a few). I am under the gun here from my CIO and this needs to be resolved or at least a workaround found asap.
To the community,
Have any of you ran into this issue and if so, did you find a workaround for it?
***Moved from Windows / Windows 11 / Windows update***
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
We shouldn't have to jump through all these hoops. Why can't Microsoft just fix the problem???
Microsoft needs to provide information on why this change occurred, there is a possible major change that seems like it is occurring, but Microsoft is greatly failing at it. Either way, Microsoft is failing, just need direction and get it all corrected.
We shouldn't have to jump through all these hoops. Why can't Microsoft just fix the problem???
I installed the TWAIN driver today for a fi-7160 in Windows 11 24H2 22631.4602 and the scanner works in the proprietary software used by the company. However, the scanner shows "No friendly name" for the scanner name. There are many others systems that this same scanner does NOT work at all, and it is greatly impacting business productivity.
After battling the fi-7160 scanners not working in Windows 11 24H2 26100.2605, including reloading Windows 11 23H2 to 24H2 via Windows Update, the scanner still would not scan. I had several computers experience problem.
This makes no sense to me, but it worked:
* Clean install Windows 11 23H2 and fully update it, keeping it on 23H2.
* Install a local or network HP printer. Other printer brands may apply, just been around HP Laserjet printers.
* Install the Ricoh PaperStream IP (TWAIN) 3.30.0 driver.
Options selected:
* Allow Windows Update install 24H2 26100.2605 (this may install during upgrade or you need to install the updates from Windows Update).
In my experiencing with the fi-7160 scanner with proprietary software needing to use the TWAIN driver, you have a greater chance on getting this scanner to work.
I did find that Pain in Windows 11 24H2 will find the scanner and actually scan. This includes Windows Scan from the Microsoft Store. This scanner supports eSCL. This can be a test for some users.
The fi-7160 scanners are expensive and great to use when they work in Windows 11.
For several days now I've been trying to install a fi-7160 scanner on a new unit with the Windows 24H2 update. I've installed the latest drivers and software. Installed all software available for that scanner from Fujitsu. The scanner is talking to the computer because it will scan manually, but the PaperStream Capture software that comes from Fujitsu and allows you to batch and\or edit the scans says it can't find the scanner.
I installed the TWAIN driver today for a fi-7160 in Windows 11 24H2 22631.4602 and the scanner works in the proprietary software used by the company. However, the scanner shows "No friendly name" for the scanner name. There are many others systems that this same scanner does NOT work at all, and it is greatly impacting business productivity.
Thank you for this post! I tried it and it works. I too do not have faith that Microslop will fix this major issue. They must have changed APIs without understanding the impact of the change. For what purpose? Major changes should be deprecated gradually, not immediately with the next release. Linux deprecates and informs.
