Around the second week in July we started having issues where our ImageClass MF247dw, MF267dw, and others would hang during a scan job to the connected computer, and eventually time out. I've followed all the recommended fixes I can find, and still several of the effected pc's have this problem on a daily basis, forcing me to uninstall and reinstall the printer/scanner again before they will function. Has anyone been tracking this, and has someone found a fix yet? Included are a couple of links explaining the problem.
We would be happy to assist further with the issue. To provide some feedback or some troubleshooting steps, we would need some additional information. If you could reply to this message with the information below, we can provide some assistance. For a more immediate resolution, you can contact support at 1-800-652-2666.
Yes, we are able to scan using the utility, and even the scan buttons, when the computer recognizes the scanner/printer. And they are both (effects 2 workstations) connected via usb. I'm having to uninstall/reinstall the Canon MF scanner/printers probably 2 or 3 times a week. Since this was apparently caused by a bad Microsoft patch, I was just wondering if Canon had gotten with Microsoft to find a fix, or come up with a permanent fix of their own?
If you are able to scan from the utility and the devices are connected via USB, you can try restarting the Windows Image Acquisition service on the computer to see if it starts working instead of reinstalling the drivers.
If that does not resolve the issue, you can try turning off any security software that is running on the computer and trying to scan again.
If you continue to have the same issue after restarting the WIA service, I would suggest contacting support over the phone so they can check what service or connection is dropping and causing that issue.
Hector - Thanks, I'll try that in the morning. Out of the (3) Windows 10 workstations that scan on a daily basis, (2) of those have been behaving normally of late, and just the (1) is still having issues on a daily basis. I wish Microsoft would address this, but sadly I have seen no evidence of that. Thanks again.