imageCLASS MF4770n will not scan on new Windows 11 installation

[Bill_W]

I have several Windows 11 machines running the  24h2 version. I have a venerable MF4770n. Two Windows machines were upgraded from Windows 10. Two have fresh installs. I can scan fine on the upgraded machines but not fresh installs. This is thru the local network not USB. I get the “can not communicate with the scanner” error. I can print just fine. I suspected a firewall problem. If that’s it, it is too subtle for me.  I tried installing with the firewall down. I opened the firewall for every Canon app I can think of. 

My inconvenient Epson flatbed scans fine. 
Thought / Suggestion?

[LietotajsLV]

Same issue with every Canon MF office printer in our company too. Something legacy/security related changed with 24H2. We have tons of interruptions, as we have 100s of Canon MF devices on our network and none of them can scan with 24H2..

[shadowsports]

See this post.

https://community.usa.canon.com/t5/Office-Printers/Microsoft-Releases-Fix-For-Scanning-Issues-After-...

[LietotajsLV]

I am well aware of the post and those updates, but it did not fix anything regarding Canon issues with MF Scan Utility and every printer that tool supports. We have 100s of them and none are currently working on clean installed 24H2 PCs. Tried both personal, work PCs and even some VMs - identical system on 23H2 works, but on 24H2 cannot communicate. 

[Bill_W]

Ditto here. I tried the KBs without success. I have one machine with an upgrade rather than a fresh install. I guess that if I need to scan I can use it.

Here’s an oddity:  The old win10 app SCAN would not detect my Epson scanner. After -667 it would. Other can programs like NAFS worked regardless. 

[Dale_1973 · Accepted solution]

I have been frustrated by this issue also. I bought a new desktop machine and it immediately updated and installed Win11 24H2 on it. I then installed my Canon software for my printer MF750C and the MF Scan Utility would fail with the message mentioned many times in this thread.

I have installed all the latest updates and including the one Microsoft released 12/10/2024, KB5048667, but none of that made the scanner software work.

Now today I reinstalled just the drivers for the MF750C under the Imaging devices in Device Manager, and it started working, and has kept working as I think I have tested after rebooting at least 10 times today.

So bring up Device Manager, (right click on the Start Menu), expand Imaging devices, then right click your device, mine says Canon MF750C Series, (2 times). Now this part is important as I checked it twice and if you don't Disable the device first it doesn't seem to work right. So right click on the device and click Disable Device. My MF750C is listed twice here in Imaging devices, so be sure to Disable Device for both of them. Then right click on it again and select Browse my computer for drivers, then select Let me pick from a list of available drivers on my computer. Your printer/scanner should be in the list, make sure it is selected, then click Next.

Mine then came back and said Windows has successfully updated your drivers. Make sure you do this for BOTH of the devices listed there, at least if it lists two of them. Windows does say it updated the device driver. I'm not sure what it did for sure but it did something.

It doesn't say you have to, but I then rebooted my machine before I tried the software, but then the MF Scan Utility works! It has kept working for 2 days now, and after many reboots!

I don't know if this will work for everyone but so far it has worked for me. I have no ideas what made it work today.  Microsoft and Canon, (and apparently HP and Brother), need to talk and get this resolved for people!

[Bill_W]

Your general approach worked. I deleted the first device. Mine was listed twice too. When I went to properties on the remaining device it was disabled!  I enabled it and I could scan. 

[jlin101]

Thanks so much for this tip.  I've been racking my brain trying to make my MF465dw scan after updating to 24H2.  Installing KB5048667 didn't help and I had to scan via USB, which defeated the purpose of a network printer.  After following the above advice, I can now scan via LAN.