Scanner Usb Device Not Recognized

[Bridget Peral]

I have a Fujitsu scanner that shows up in my device list but my scanner software does not recognize it. Even Windows fax and scan does not see it. If I go to add a scanner it shows up but when I want to scan, it says no scanner found. If I try to scan from the scanner, it says no application is associated with it. I had to install it in compatability mode Win XP to get it to recognize the scanner. Is this why it is not working right??

If it is in the device list on device manager, it is definitely compatible with win7, but there could just be a lack of support with the driver and windows scanning applications you are attempting to use.

There is not a newer driver, I have checked. I am going to try another scanning program to see if I can get that to work. Is there anything else that I can try?? Different programs maybe and older program?? I tried running the program in compatability mode too but that did not help. Thanks for your help!!

I am running Win 7. The scanner is a discontinued model that was not compatable with Win 7. I ran the setup and did troubleshoot compatability and ran it in Win XP mode. That was the only way it would show up in my device list. It is a TWAIN scanner. I had to download the driver from the website because it did not come with any software but I thought windows fax & scan would work. When I bought it I thoughtI could make it work, but maybe its just too much trouble.

Darrin, I tried the chat while I was at home but they were closed. So I did send the email. They replied that the scanner does not work with Win 7 so I guess that is my answer. I think I will just send it back to the person I bought it from. Thanks for your help.

When you attach the scanner, via the USB cable, do you get a chime like the computer recognizes that you plugged something in? How about in the lower right hand corner, anything popping up down there?

So the hardware is seeing the scanner, which means John is correct that the driver did not install. Try just deleting those devices out of the device manager and then refreshing and see if you can get to prompt you for where the driver is. You could also try right clicking the device and trying the troubleshoot option. If all that fails, do a system restore back to before you installed anything or plugged anything in. For future reference, for USB devices, you almost always install the software first.

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

1/12/23 Update - Still fighting this every morning. The only thing that works every time is go into Device Manager, Imaging Devices, and uninstall the Canon scanner (making sure to check the box to delete the drivers) and then reinstalling the drivers for the Canon device.

If all 3 of the computers have the same version of Windows and only 1 computer still has the issue, I would suggest downloading the latest version of the drivers From our Canon USA support page and installing it on the computer with the issue or trying another USB cable/port to see if it resolves the problem.

Hector - Thanks, but I've done that already. Honestly, all signs point to a Microsoft patch causing this, and if Canon hasn't specifically identified the problem and come up with a fix of their own, all the standard troubleshooting steps in the world probably won't fix it for everyone. Thanks anyway though.

Well, hate to "beat a dead horse" but this last Patch Tuesday, this happened again. We have (4) users with MF240 series printer/scanners and every one of them says "Connect the Computer" when using the scan button, and the MF Scan utility doesn't recognize the scanner either. What I have done is 1) Completely remove the Canon drivers from Control Panel/Programs and Features and 2) Reboot the computer and 3) Reinstall the Canon drivers. After a few minutes, the scanner works from the scan button on the device, as well as the MF Scan utility.

I've run into situations where devices stopped working with WMDC/Active Sync.I've usually found success disabling "Advanced Networking Functionality" on the device. On your device, tap Start > Settings > Connections > USB to PC > Uncheck "Enable advanced network functionality".

The other thing that usually causes this is the device drivers. When you plug in the device it tries to install device drivers. You may end up with a ton of "Windows Mobile Remote Adapter #n" devices showing in Device Manager. You can clean these up because the device driver will be reinstalled next time you plug in the device. There is detailed information available about the process here. If the device driver is failing to install you should see a popup near the clock/system tray area.

In addition to all the other fixes you find on the web, I noticed that the Windows Mobile device will not connect to the Windows Mobile Device Center when I am accessing the Windows machine that runs WMDC through Remote Desktop. Had that problem on Windows 7 and 8.1. The fix for me was to login to the Windows machine first without Remote Desktop after which WMDC will show that the device is connected. Once the connection has been established I could access the machine using Remote Desktop and the Windows Mobile device stayed connected.

I got this working on Windows 10 (2019) after trying a lot of different things.What mostly worked was in services, there are 2 services called "Windows Mobile-based device connectivity" and "Windows Mobile-2003-based device connectivity".

Right click on each service and make sure they start automatically (delayed).Click the "log on" tab, change the access to be "local system account and enable "Allow service to interact with desktop"Apply and click ok.

After logging onto your desktop, give your computer a few minutes to start those services. When both are running, you will need to open the application "Windows Mobile Device Center" to initiate the connection. This had be to open for this to work in my case.

You should see connected. Now, windows tends to update itself without your permission so what happens sometimes is the "log on" credentials get reset so you will need to redo them as above. But for some reason yesterday for me, nothing would connect until I did

UPDATE (Jan 2020):

I had another issue every time I docked the scanner into the cradle, it would detect a USB device but immediately register it as 'unknown device' or sometimes, very rarely, it would list it correctly but disable the device because of a timeout. My problem here was the computer I was using has USB 3 connections, so I plugged in an old USB hub, connected the dock to that and it hey presto worked again.

On my MC92N0 scanner I went into Settings/Control Panel/USBConfig and I had to tap on the "USB Client Mode." It was previously selected to port mode "USB OTG Mode". After doing this I placed it in the doc again and it connected normally\launched Windows Mobile Device Center.

Also fyi you should also be able to find the scanner and access files once you're connected by looking underneath devices in "This PC", similar to how you would access a USB flash drive. I was able to do this on Windows 7 & 8.

I spend a couple of hours trying to make this work for a MC92N0. In my case, I have used windows 10 to configure MC9090s through WDMC with NO issues, however, when attaching an MC92N0 nothing was happening, I could not get the MC92N0 to connect (same results on a windows 7 machine ).

What worked for me was to use a USB hub to connect the cradle to the PC, insert the device into the cradle, then go to the device "control pannel" > "USBconfig" > and then switched the USB modes to "mass storage" and select any of the folders (at this point the windows machine recognized a storage device was attached, but still no WDMC connection) > then I switched the setting back to "ActiveSync Serial" and the WDMC showed a connection!

EDIT: Ok i have found a solution and that involves creating a batch file.. WMDC used to open fine for me until i upgraded to Windows 10 now it only does it when it wants to... See here for details

3a8082e126