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.)

[nevermind1]

Same situation here, we have a good-old Xerox, works like a charm on it's old stock drivers and software which came from the box. Works after all Windows 10 updates.

I killed another 4 hours of my life to solve the problem. No progress at all. It simply doesn't work.

[charlie95722]

I am running the latest CanonMF Toolbox 4.9 on Canon's website (for my Canon Imageclass D1150), and I ran the patch they suggested to run.  After the latest Windows 10 update, I couldn't scan again.  So I just ran the patch one more time and now it runs just fine again.

For me, Canon has kept the drivers working for my D1150 with Windows 10.  I just had to follow the instructions to the letter. And keep trying until I got it right.  But, I have a lot of patience.

[reba]

Still no reply from Canon to me.

On another note I had problems with my card readers, both internal and external, after upgrading to Win10.  After six months of hair pulling I took it to a pro shop.  After they tried for two full days, and failed, they came back to me and said that the problem was that Win10, when updated, or even booted, automatically replaced any drivers that it didn't think belonged there with the MS signed and approved driver that was already in Win10, from its first release.  So, no matter how many times the shop put the correct driver in for those card readers Windows 10 replaced them each time it booted or updated with the one that didn't work.

I don't know if this has any bearing on all of our problems here, but maybe the do-nothings at Canon could look into that.  I almost choked with laughter after I typed that line because it was such an oxymoron: Canon actually doing something to help their customers.

[nevermind1]

Canon, WTF?! Please fix your god **bleep** drivers. Our office started loosing clients due to problems with scanners.

[dchang0]

I guess the best solution is to diversify across brands and models within each brand.

I got hit because our office had mostly the exact same model of Canon MFP (MF4690). But, we have other brands: one Xerox (drivers no longer updated but hardware is awesome), several Panasonics (on the biggest one, the rollers keep generating false "needs replacement" errors, but the others are solid), one OkiData (worst MFP I've ever seen--no one will use it), several HP (drivers absolutely refuse to install on Win10 for a handful of them, and these are BRAND NEW HP MFPs, bought after Win10 came out!!). Our office was able to get by with the Canon users asking the other users for help. We simply returned the brand new HP MFPs that wouldn't install.

Strangely, the Canon DR-C125 and DR-C225Ws we have work fine and had no trouble with the Win10 upgrade. So it's a total crapshoot. There is no way of knowing which specific model from which brand will be solid and fully-supported. The Canon MF4690s were awesome through WinXP/Win7, so we bought tons of them, but they all died as soon as Win10 hit. We were fooled by their reliability into buying a big batch. We won't be doing that again--we'll diversify on purpose.

For the software, I blame the hackers who have caused Microsoft to secure all the underlying drivers which left the hardware makers scrambling to hire driver developers. Bad hardware = no excuse.

[sferrell615]

i was wondering what the reason was for recently receiving multiple notifications about this 'old' issue...

scanner was working until latest windows 10 update 28084 on 9/27/2016, which i read others have been receiving for previous month.

i checked canon site for printer / scanner model (for me mf4370dn) and there is a new update available as of 9/23/2016 (previous update was 7/7/2016) for the Toolbox (Ver.4.9.1.1.mf18) and patch for USB scanner. note: the drivers have not been updated (latest update available is 7/7/2016).

i followed steps pasted below and USB scanner works again.
also, i pasted a link below to full steps that i've performed in the past as well.

personally recommended steps to update canon SW:

1. disconnect canon USB from PC
2. reboot
3. uninstall canon mf toolbox ####.mf##
4. reboot
5. install canon mf toolbox ####.mf## (double-click to extract files to Toolbox folder, double-click Toolbox\Setup.exe)
6. reboot
7. install patch for USB scanner (double-click to extract files to NetworkUSBScanPatch folder, double-click NetworkUSBScanPatch\UpdateProgram\UpdateProgram.exe)
8. reboot
9. connect canon USB to PC
10. scan (note: you'll have to update your preferences e.g. PDF vs. JPEG)

link to full steps that i've performed in the past (in case you still have problems):
http://community.usa.canon.com/t5/Office-Printers/MF-Toolbox-doesn-t-work-on-Windows-10/m-p/180725#M...

[reba]

Thank you for posting your solution to your problem.

However, the reason for additional entries on this "solved" issue is that for many of us it is not solved and nowhere close to being solved.  The reason it is marked 'solved' is that one person managed, on their own, to get the problem fixed FOR THEM.  For the rest of us we have have issues that encompass many different issues all revolving around scanning and MFToolbox.  For isstance, it took me over four months to uninstall and reinstall Toolbox and that only got me back to my original problem of Toolbox not recognzing my scanner (not on a network).  It has been three or more months now since then and no new communications from Canon.  Others have similar issues revolving around scanning, scanner recognition, networking, etc. 

Clearly Canon has not allocated any resources, to my knowldege, to fix this vexing interaction with Windows 10, and like most tech companies they refuse to communicate with their customers about progress, if any, on issues important to the customer.  The clear lesson is that once you buy a Canon product you are on your own.  Period.

Call me delusional but I still fantasize that somehow, some day, Canon will have the blinding epiphany that if they want to have return customers they might, actually, just a little, pay some attention to their current one.  But, as I said, I'm delusional.

[sferrell615]

hi reba
i was referring to 'old' problem because it was working until the latest windows update. i understand that some people might be in different situations. as far as i'm aware, all of the steps that are needed to fix this issue are included in my previous post. i wish you luck.

[Handyman]

You need to call Canon's support phone number. They will walk you through the process. I have 2 Canon printers that had this issue, but no more since they helped my over the phone.

[reba]

The last time I called Canon phone support they swore up and down that my problem was that I was using a 6 foot USB cord and not a 3 foot USB cord.  I challenged that thinking but the guy doubled down saying that it was ll over their database that this was the problem with Windows 10.  Much against my better judgement, but willing to try anything, I tried that.  Of course it didn't work.  I have no faith in Canon.