11-21-2015 05:23 PM
A third party VueScan utility works great and is more comprehensive than ToolBox 4.9.. Costs $40. Canon has better shape up and fix its sofware instead of blaming the problem is with the customer's computer.
11-25-2015 07:03 PM
Hello Cannon support team,
I have the same of similar issue after downloading MF Toolbox Version 220.127.116.11.mf127 for Windows, it does not work on my MSFT Surface running Windows10.
When I open the MF Toolbox program it diesplay an error message window with the following:
"A supported scanner is not installed" "Please install a supported scanner and restart Toolbox"
My scanner is supported in my other computer running Windows7 Professional, SP1. This is a Dell PC (64bit OS) and its been working fine for a couple of years.
Is there a solution to this problem of incompatibility with Windows10 OS? On the forum it seems to be a very common issue.
Can you help me?
11-25-2015 07:09 PM
Welcome to the Canon Forums and thanks for your post!
To have a better understanding of your issue, please let everyone know the model of the product you have. That way, the community will be able to assist you with suggestions appropriate for your product.
If this is a time-sensitive matter, our US-based technical support team is standing by, ready to help 24/7 via Email at http://bitly.com/CanonEmail or by phone at 1-800-OK-CANON (1-800-652-2666) weekdays between 10 AM and 10 PM ET (7 AM to 7 PM PT).
11-26-2015 01:18 AM
4 calls to Tech support has no solution and claimed it was a customer PC problem, but a 3rd party VueScan has no issues and is more comprehensive than the Canon Toolbox 4.9.
11-26-2015 04:22 PM
Since behavior seemed to be some inter-process lock, I tried to stop as many background processes at notification area as possible, and some of those unlocked setup.
Processes I closed were:
and several more.
one of these processes dead-locks toolbox setup.
after exiting/quiting/stopping all of these I was able to finally successfully install ToolBox_4911mf17_Win_EN.exe on windows 10 (current version on Nov 26, 2015)
12-02-2015 03:05 PM - edited 12-02-2015 03:56 PM
I have the latest version of Windows 10 that came out in fall 2015. I used to be able to scan, but after the update, it didn't work. Here is my list of things to get the scan function working...
This means to me that Microsoft has hidden or obfuscated the old, tried-and-true WIA scanning interface. It is apparently still available somehow to the older programs that use this. I think WIA is actually newer than the older TWAIN driver, but I am not sure. Anyway, try the programs I mentioned and see if they can work for you.
One more thing: I have my Canon printer on the network and connected to USB. I am assuming the scanning happens over USB, but I have heard WIA works over a network.
12-12-2015 05:44 AM - edited 12-12-2015 05:54 AM
SORRY - this reply was intended for Piers_A and Captret.
Many, many thanks. I entered the changes you recommended and it worked not only the first time but I’ve been using it for the past week without a problem.
12-13-2015 03:34 PM - edited 12-13-2015 03:34 PM
"Start> in the run box type. Services.msc
Scroll down to Windows Image Acquisition (WIA)
Right click, select Properties
Check that Startup type is set to Automatic
Click Log On Tab
Check that Local System account , and Allow service to interact with desktop is checked. Hit apply.
Click Recovery...Click on window next to First Failure, Scroll to Restart the Service. Hit apply."
This was posted awhile back(msg 23) in this thread. PiersA, and originally somewhere by Captret.
I wish people would just do their research and take time to read through a thread instead of just repeatedly asking a question and expecting it to be handed to them on a plate.
The response above has helped ALOT of people. Its SIMPLE, its EASY, it WORKS for many people- including me.
Try it, and if it works, thank(kudos) PiersA and Captret. That way when others go through the thread they can see that post got lots of kudos and therefore is a good bet.
In this way you also help others instead of just yourself.
Rant over.... :-/