How can I find out when this issue has been resolved?
Windows 24H2 issues with Scanning
![](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)
Anonymous
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***
Windows for business | Windows Client for IT Pros | User experience | Print, fax, and scan
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.
80 answers
Sort by: Oldest
-
Anonymous
2025-01-16T22:37:46+00:00 -
Anonymous
2025-01-17T00:24:50+00:00 Check for Windows updates and install them all. Then do a restart. After the restart, go to the search box and type in wiaacmgr, It is a run command. if your scanner shows up as no friendly name, it is still not fixed. I have done this and it is still broken. Microsoft seems to be very unresponsive in addressing this issue.
-
Anonymous
2025-01-17T21:09:05+00:00 Having the same issues with Xerox MFPs specifically. We have a LOT of legacy devices (printers, scanners, etc) that were working fine until we started replacing some Windows 10 desktops with new Windows 11 24H2 computers. These new computers will print, but they refuse to see the scanner on MFPs. I thought that it was a USB specific issue until I tried to network one and had the same issue. I had read that MS stopped pushing the 24H2 update to computers with a USB printer/scanner installed until they get a fix for this. That doesn't help with new computer deployments though. This has thrown a wrench into some workflows to say the least. You would think that they would have made sure nothing was this wrong since they scrapped 24H1 because of some of these bugs.
-
Anonymous
2025-01-21T15:52:15+00:00 We are using a pretty expensive Fujitsu scanner that we have spent so much time(money) troubleshooting as to why it isn't working.
Doing the same sort of things as described in this thread.
Get your act together Microsoft, you have been so messing up so much lately, so lame!
Fix it.
-
Anonymous
2025-01-22T16:26:34+00:00 We have three Brother MFC-L8900CDW printers on a print server and workstations directly connected, with drivers installed on each workstation. However, all of the workstations have lost the scanner function, which hinders our day-to-day business, as we need to scan documents into customer accounts.