Unable to open TWAIN source

CanoScan LiDE60 yes its old but you can still buy them new. Its been working well on my new Dell XPS8700 running Windows 10 for over 6 months. Suddenly I get "Unable to open TWAIN source Please check connection Then re-start Toolbox" Unplugging and plugging the connection the computer gives the little beeps acknowledging the connection. However I still get the same error message and the associated "Toolbox" software doesn't recognize the scanner. Re-boot the computer no help. What does "fix" it is System Restore (one of Windows great features). The most recent restore point even has the same Win 10 update status so the problem doesn't seem to be an update. I checked scanner operation each day since the previous "fix" and it worked well for 3 days, now it doesn't. The scanner works fine on my 4-year old Dell XPS8100 running Windows 10 and the exact level of update.

There are no new drivers. Cannon says the scanner doesn't need a driver, its included in Win 10. I can delete the driver, reboot and the driver is back so I guess that's true.

Any suggestions about kick starting TWAIN would be appreciated.

Have you changed USB ports lately? Canon scanners can be quite picky about usb3 for instance. Try USB2.

When its working it is normally plugged in to USB3 ports. When it isn't working using a USB2 port doesn't help. Both port types clearly recognize when is it plugged or unplugged per the Device Manager.

Was it working before on this same hardware? I had to select MANUAL option for XHCI (USB3) in BIOS for my LiDE 210 to properly work. Is your USB3 Intel?

Hi there

TWAIN is now "deprecated" in W10 -- if you still need TWAIN you'll have to either install W7 / XP / VISTA Virtual machine and run your scanner from there. Windows now uses WIA for "acquisition" type stuff -- i.e getting image from scanner etc.

TWAIN Compatibility (Windows Drivers)

Alternatively there's a piece of Paid software that still keeps these old scanners running --haven't used it for agaes but it was very good from what I remember

VUESCAN

VueScan Scanner Software for Windows, Mac OS X and Linux

If you managed to get that scanner working before on W10 you must have been quite lucky or the driver was still working. TWAIN as scanner technology is not supported any more by Ms. The software is using WIA in some sort of compatibilty mode -- which *might* or *might not* work depending on all sorts of factors.

If you like the scanner the VUESCAN option seems to be the best - for most normal functions it will cost you USD 35 or so -- or around 22 GBP / 30 EUR.


Cheers
jimbo

jimbo45 said:

Hi there

TWAIN is now "deprecated" in W10 -- if you still need TWAIN you'll have to either install W7 / XP / VISTA Virtual machine and run your scanner from there. Windows now uses WIA for "acquisition" type stuff -- i.e getting image from scanner etc.

TWAIN Compatibility (Windows Drivers)

Alternatively there's a piece of Paid software that still keeps these old scanners running --haven't used it for agaes but it was very good from what I remember

VUESCAN

VueScan Scanner Software for Windows, Mac OS X and Linux

If you managed to get that scanner working before on W10 you must have been quite lucky or the driver was still working. TWAIN as scanner technology is not supported any more by Ms. The software is using WIA in some sort of compatibilty mode -- which *might* or *might not* work depending on all sorts of factors.

If you like the scanner the VUESCAN option seems to be the best - for most normal functions it will cost you USD 35 or so -- or around 22 GBP / 30 EUR.


Cheers
jimbo

This is very confusing. I've been using this scanner on various computers for years, XP, Win 7, Win 8 and now Win 10. It is presently working again on this Win 10 computer and has never failed on another computer running Win 10 that was upgraded from Win 7. When I deleted the driver Win 10 happily installed the same driver dated 10/2/2006. I guess "deprecated" doesn't mean "won't work".

CalBear37 said:

This is very confusing. I've been using this scanner on various computers for years, XP, Win 7, Win 8 and now Win 10. It is presently working again on this Win 10 computer and has never failed on another computer running Win 10 that was upgraded from Win 7. When I deleted the driver Win 10 happily installed the same driver dated 10/2/2006. I guess "deprecated" doesn't mean "won't work".

Hi there.

Are you running 32 or 64 bit windows -- my guess is that the W7 driver was from a 32 bit version of Windows which may well work still on W10 - 32 bit --not always though.

It won't work on a 64 bit version of W10 though - I'm pretty sure of that.

Cheers
jimbo

jimbo45 said:

Hi there.

Are you running 32 or 64 bit windows -- my guess is that the W7 driver was from a 32 bit version of Windows which may well work still on W10 - 32 bit --not always though.

It won't work on a 64 bit version of W10 though - I'm pretty sure of that.

Cheers
jimbo

Hi,
Its a brand new computer running 64-bit windows. The scanner was working well since purchased several months ago but first stopped about a week ago. After the last system restore I used a different USB2 port. Its still working perhaps it will continue.

The older computer is also running 64-bit Windows 10 upgraded from Windows 7. The same driver is used in both installations.

Regards,
CalBear

Thank you Fabrizio!

This had been driving me nuts. My LIDE 60 scanner had been working perfectly with my HP Envy laptop until I upgraded Windows 10 to build 1607, and then I got the error message about Twain. The Windows troubleshooter insisted that it was a USB3 problem. I do not have USB2 on the laptop, but easily disproved that theory by using the scanner on a desktop running the same operating system, with no difficulty under both USB2 and USB3. Reinstalling the drivers made no difference, but editing the Path variable as you suggested solved the problem instantly. It is disappointing that the troubleshooter should have missed something so basic - yet so obscure for people not familiar with DOS.

grisu70 said:

Hi,
don't know if you still solution for original thread, anyway you can solve adding to PATH variable, the location of twain folder (in my case C:\Windows\Twain32\CNQ4803)

Probably some program deleted/modified your settings.

I would suggest to update both user environment variable and both computer environment

Let me know if it solved

Bye
Fabrizio