Unable to Scan after Windows 24H2 upgrade

[s4sythe]

We have multiple computers that were upgraded to Windows 24H2 and have Brother MFC type printers that are connected to a network and have IP address assigned to it. The printers have the scanning capability and since the update to 24H2 we are unable to scan but can still print. Any ideas? We uninstalled and reinstalled the full package brother software and still no luck.

 

[s4sythe]

Did the following steps: installed KB5048667 , then uninstalled both the print/scan driver and the iPrint&Scan software, then deleted the leftover files and folders, rebooted the computer, and installed the full driver and iPrint&Scan. Still having the same issue, computer does not see the scanner

 

[KenVic]

I did the same with no success (I have the Brother MFC-9340CDW.) I went to 'Settings > Bluetooth & devices > Printers & scanners' and removed the Brother printer. Then I clicked the 'Add device' button and readded it. And then the scanner was available again. Hope this works for you.

 

[davew]

I did the same with no success (I have the Brother MFC-9340CDW.) I went to 'Settings > Bluetooth & devices > Printers & scanners' and removed the Brother printer. Then I clicked the 'Add device' button and readded it. And then the scanner was available again. Hope this works for you.

I had no luck.

 

[GaryS1964]

I had the same problem with my MFC-L2740DW. I could print wirelessly but not scan. My computer would not recognize the scanner. I deleted and reinstalled the printer several times using both the original CD that came with the printer and the latest full version downloaded from the Brother website. Nothing worked. On the page for my printer under Printers and Scanners in Settings there were separate setting for the printer and scanner. i tried clicking on the scanner settings and nothing happened. One thing I tried which may have been the solution was to run the printer installation software with Run As Administrator. That seems to have been my solution but I'm not sure. Very frustrating three days but it's working now.