Windows Twain Driver
Ernest Babin
The Windows 10 is (Build 1903) and after the upgrade the software that interfaces with the Camera via Twain no longer connects to the camera despite the camera having a driver and showing up in the list of hardware:
TWAIN itself is deprecated in Win10, and replaced by WIA (Windows Image Acquisition). Windows 10 still has a Twain driver dll present - BUT - if your inPhoto software has its own driver, make sure that the windows file is gone/renamed first. When you select the TWAIN source, it should says WIA-Canon PowerShot or something similar.
TWAIN itself is deprecated in Win10, and replaced by WIA (Windows Image Acquisition). Windows 10 still has a Twain driver dll present - BUT - if your inPhoto software has its own driver, make sure that the windows file is gone/renamed first. When you select the TWAIN source, it should says WIA-Canon PowerShot or something similar.
I looked for the .dll file and it was there, but also was a directory C:\Windows\twain_32\ and inside of that are an inPhoto ID PS directory with an inPhoto.ds file and in the root of twain_32 a wiatwain.ds file.
I have three scanner drivers installed in my Windows 11 Pro 22H2. I use two other programs (NAPS2 and Paint) and both of them recognize both sources / drivers without any problems and can scan images from these sources.
And the story returned back to point 5th. IrfanView sees neither this new scanner nor two older ones, while Windows 11 Pro and all other image-related software (Paint and NAPS2 in my case) sees all three drivers and is able to scan from all these TWAIN sources without any problems.
There's also a chance that the above story has nothing to do with this and that IrfanView stopped seeing any TWAIN source after recent update to (the newest) Windows 11 Pro 22H2. As these two events (Windows update and scanner access lost in IrfanView) happened in the fairly the same moment of time.
I signed up here, because I had the same issue, and I actually managed to fix it. It's actually caused by an incorrect copy of the twain selector .dll (TWAINDSM.dll) that some scanner drivers add in the system folders. Irfranview then ends up loading it instead of the correct twain_32.dll that comes bundled with Windows.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
I have one computer who has only wiatwain.ds in this folder at it fails to work with WebTwain app for web applications (No drivers found).Also there is one another computer where folder has a lot of files and everything worked fine.But after folder was cleared (now there is only wiatwain.ds) WebTwain doesn't see scanners.Can anyone tell me about this problem more deeply and how to fix it? Because everything I found in interned mentioned that this folder must be just ok.
When you start your scanner program to scan from some device,It will internally call "Data Source Manager"(DSM).This DSM is already in your windows PC.(You don't need to install it.)This DSM will find all scanner drivers available in your "C:\Windows\twain_32 folder" by finding "Data Source"(.ds) file.It will find all folders and its sub-folders.After finding all ds files, It will give list of all installed scanner driver to your Scanner Program which will show you the list of scanner driver installed in your Windows PC.
I have loved my R40 scanner, but now it won't work. I use the Canon-supplied software, both the driver and the CaptureOnTouch software. Recently, when I've tried to use it, I get "An error has occurred with the TWAIN driver. [Error: 80FF0001]" and that's it.
I've tried re-installing the driver. I've tried uninstalling it and re-installing it. I've tried uninstalling all the Canon software and re-installing the whole software package. Nothing has made it work. Someone, please help! Thank you.
Yes, it's a new problem. I'm not aware of anything changing, which is why this is particularly puzzling. The computer says it's a 64-bit operating system, x64-based processor, running Windows 11 Home, version 21H2, OS Build 22000.469. The driver is what I was able to download from Canon. The computer says it has a driver date of 5/10/2019 and Driver version 1.0.0.0 It says Digital Signer "Microsoft Windows Hardware Compatibility Publisher"
Long ago. They're not in the same timeframe. But with Microsoft's constant updates, that could be related. With that said, how do I get a driver that works so my R40 goes from paperweight back to being a working scanner?
If you are a getting a driver error, you can try downloading and installing the twain scanner driver using the link HERE. We would be happy to assist 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.
Honestly, I don't know if there was an update right before this started. It seems like Microsoft is always doing another update, but I'm not actually aware of one having happened before this issue started.
We have this same issue. We have half a dozen of these devices. They all fail in the same way on every Windows 11 computer we have. Our service tech's have tried everything we can think of. What we find is we have to uninstall the drivers and unplug the scanner. There's a TON, crazy plugins for apps we don't have too. Then reboot and re-install and the scanner will work for a day or two, then again, twain error. Both the Canon scan app and the windows scan app fail once this happens. Not a single R40 works with Windows 11 for us, not even fresh loaded Windows 11 computers, they fail in the same way.
I tried changing the Windows Image Acquisition setting, too. I think I've read all the suggestions online. No luck. I'm very frustrated. I wish the Canon people would get on this. Yes, Windows changed. That's the world we're in. No reason that means the scanner should stop working forever. It needs some kind of patch. I wish you luck getting your scanners up and running!
Emails and calls to Cannon technical support have not helped. After two rounds of the typical "reinstall...", they sent some patch, which did not help. This seems to be a known problem in user reports and the Cannon support staff, but no solutions.
It works until the next reboot. I keep the Services app pinned to my task bar with Name sorted in reverse order so I can quickly get to the WIA service. I have uninstalled/reinstalled with the latest drivers and software and nothing else works for me.
Same issue here after moving a Canon scanner from a stable Windows 10 desktop computer to a new Windows 11 computer. Worked for a couple days, then got the 80FF0001 Error, re-installed the driver, worked for a couple of days, and got the error again. Any other suggestions would be appreciated.
I have the same issue. It popped up for me at the last Windows update. Based on JayC1's comment, I just tried to deactivate Windows Defender Firewall, and all of a sudden I can scan again. This is clearly not a longterm solution and Canon must work with Microsoft to update their driver to work through the firewall
I called Canon support after having this problem following an upgrade to Win 11. They instructed me to run the "Restoration Tool for Windows Registry" found on the Drivers and Downloads page under the Utilities tab. The "Readme" file included explains that it solves a Windows registry inconsistency that can keep the scanner from being recognized by Windows.
As reported earlier - this is their standard (FAQ) response to this. I had also done this, it reported an error and fixup, and as always, things worked for a short time, and then back into the failure until-reboot loop.
I made another discovery regarding this recurring issue this week. There are two computers with the software suite installed in our office. When one has the twain driver error, connecting the scanner to the other computer, performing a scan, then returning to the other computer then the error is resolved. This seems like a driver problem in communicating with the scanner, performing a scan with the other computer seems to wake the scanner up and it operates normally. So many folk seem to have this issue Canon ought to be able to reproduce it and fix it.
For quite some time the LIDE 70 scanner worked well with Windows 10, Paperport 11 and using the TWAIN driver. Recently, I suppose caused by a Windows update, the scanner is attached with the WIA driver. It works, but the WIA Canoscan Lide 70 interface offers less choices than the TWAIN interface. Uninstalling and reinstalling everything, LIDE 70 driver with Win 8 compatitility as suggested in -us/windows/forum/all/canoscan-lide-70-and-windows-10/440c49e5-3ff2-... or adding the path to the drivers as suggested elsewhere ended up with the WIA driver working with Paperport 11 always. Is there any way to force the TWAIN driver to be used with the scanner and not WIA?
I don't know who the villain is in this scenario, Microsoft or Canon. Perhaps both companies working in cahoots. However, I do know that the old Windows 7 drivers for my Canoscan scanner work just fine in Windows 10 when I use a special program (which will remain unnamed) to access the scanner. Microsoft suddenly decided to stop using Twain drivers and only allow WIA though, so I'm now unable to access my scanner from my favoriter image editing programs. My scanner has special capabilities that Canon for some bizarre reason no longer includes in any of the scanners it sells but then, why should I have to replace a perfectly functioning scanner? And in any event, I will never purchase another Canon product as long as I live. I will also do whatever I can to convince others to avoid Canon products as well. Planned obsolescence has its downsides and angering a customer like me is one of them. I can assure you, by far I'm not the only Canon scanner who is furious at not being able to use my scanner because of artificially imposed regressions in functionality imposed by Microsoft AND Canon.
c80f0f1006