MF Toolbox doesn't work on Windows 10

[mj1856]

I have a MF4570dn, and recently upgraded from Windows 8.1 to Windows 10.

I can no longer scan using the MF Toolbox utility.   I had MF Toolbox 4.9 installed before the upgrade, and it worked just fine.  After the upgrade, I get "Cannot communicate with the scanner" error dialog:

I thought I would try to reinstall the MF Toolbox utility, but there are two problems.

1) The downloads page shows no downloads for Windows 10 for this printer. This should be updated.

2) I downloaded the one for Windows 8.1, and tried to reinstall, but it just hangs at the "Processing Installation" screen:

I've also tried to uninstall the existing MF Toolbox first, and it also hangs at this same dialog.

I've also tried various other things without success:

- Connecting via USB instead of Network.  It detects the scanner, and MF Toolbox can switch to that device, but it still gives a communications error.

- Trying the built-in Windows Scan app instead of MF Toolbox.  It uses the WIA driver.  It barely starts to scan, then immediately cancels.

Please Canon - forward this to your engineers and provide a fix asap.  I cannot use my scanner on Windows 10.

(I can use the printer functionality just fine.)

[adventurept]

THANK YOU!

[greatimes]

Thank you so much for your solution. It works immediately! To think I almost uninstalled / re-installed, bought new software etc.

You saved me a lot of needless aggravation.

[wcklypc]

Thanks, worked for me on Image Class MF4350d even after reboot. Only issue is Windows Fax Scan doesn't work, but I'll use MF Toolbox instead.

[sferrell615]

had this issue.  windows 10 started getting worse... store apps no longer opened, etc.  i did a re-install of windows 10 from microsoft (not laptop manufacturer).  all was working for weeks until windows update (as this issue occurred before)... microsoft visual c++ 2010 x86 redistributable 10.0.40219 kb2565063.  

this time, i just uninstalled and re-installed in this order with reboots in between each and scan is working.  thought i tried this before and it didn't work but might not have done reboots in between (too long ago to remember!).  

reboot

uninstall mf###-###

reboot

uninstall canon mf toolbox ####.mf##

reboot

install mf####-###

reboot

install canon mf toolbox ####.mf##

reboot

if it stops working again, before uninstalling / re-installing, also try:

powering off your pc and printer

unplug the usb from your printer to your pc

powering on your pc and waiting until it's been up a minute or 2 (for services to finish starting)

powering on your printer and waiting until it's been up ~ 10 seconds

plug the usb from your printer into your pc

open the canon mf toolbox #.# manually

switch the printer to usb scan (if desired)

press the start button on the printer

[gnocchi]

Does Canon not realize how many customers they are losing and the extent of negative word of mouth publicity it is getting? How long can Canon make its customers jump through loops before coming up with a fix to this problem?

[danrentonwa]

Make sure that the LCD display shows "USB SCANNING."    Press the "SCAN" button above the display to select.  

[kjv]

On i-sensys MF8350Cdn (German device name) I had the same problem with not functioning scanner after upgrading to Win 10. Using the guidance of Piers_A  from 08-19-2015 the scanner is working properly. Many thanks for the perfect solution!

[LAR1]

Outstanding thanks kjv for refering us to Piers_A on 8-19-2015.  I too was having this problem and this fixed it.  Kudos to you and Piers_A.  This needs to be broadcasted to everyone that has responded with this problem.

[procket52]

This is absolutely the right fix for the problem......was driving me crazy since the print function was fine.....Canon community is a big time help.

[Stormforge]

This solution works on my MF4270.   Called Canon tech support twice, and all they do is uninstall/re-install drivers (which only fixes the problem until you reboot your computer and the fix is lost again).  Canon tech support should really have pointed this fix out in the first place.