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.
The same scanning problems that everyone else has described here continued even after KB5048685 installed in Windows 11 24H2.
The Canon MF Scan Utility keeps showing this message in Windows 11 24H2 26100.4602:
I have greatly detailed my scanning problems with the Canon Color imageCLASS MF654Cdw unit here.
I restored my systems back to Windows 11 23H2 for the Canon scanner to work with the Canon MF Scan Utility.
Microsoft still has not corrected the eSCL bug causing these scanning issues.
I have the same issues with a Canon MF753cdw. What has worked for me is to use NAPS2, https://www.naps2.com/ to scan instead of the MF Scanner. NAP2 offers sufficient settings for PDF creation, OCR, emailing, etc. to meet my needs for now. I haven't tried other scanner replacements, but seeing as you can scan natively from Paint, the issue seems to be related to the scan software specifically. Maybe other commercial software like Adobe can be an alternative, especially for those in corporate settings who need to clear these applications through IT. Hope this helps others.
I have the same issues with a Canon MF753cdw. What has worked for me is to use NAPS2, https://www.naps2.com/ to scan instead of the MF Scanner. NAP2 offers sufficient settings for PDF creation, OCR, emailing, etc. to meet my needs for now. I haven't tried other scanner replacements, but seeing as you can scan natively from Paint, the issue seems to be related to the scan software specifically. Maybe other commercial software like Adobe can be an alternative, especially for those in corporate settings who need to clear these applications through IT. Hope this helps others.
I installed NAPS2 in Windows 11 23H2 and I think this is better than the Canon MF Scan utility.
I read somewhere, lost the web site reference, that Microsoft implemented the eSCL protocol (Refs: Mopria eSCL Specification and/or Mopria eSCL Specifications) to make all printers and scanners driverless. This is similar to how Linux and macOS CUPS interface handles printers. If such device requires additional support, the driver and/or interface must be Morpia specific or compatible. However, if this is true, then all printer manufacturer's needs to update their scan utilities. That would big a major impact because many old scanners are still using TWAIN support.
Great suggestion! Thank you for the suggestion on using NAPS2.
We are still troubleshooting as it seems nothing still works after the December 10th Windows Update.
As for NAPS2, it works but it's not something we can utilize for a large number of staff throughout the state.
This has been quite troublesome and HP Level 3 still just says they are working with Microsoft.
I think Microsoft needs to release a downgrade to 23H2 that will bring everyone back and dump 24H2 until it is fully tested and working. They sure put the cart before the horse on this one. This is about as big of SNAFU as I have ever seen from Microsoft with the exception of Windows ME. This sure gives Microsoft a black eye.
