On 5/25/2024 10:59 AM, John C. wrote:
I have a Canon Canoscan 8400F scanner which is still mechanically
functional. However, I'm pretty much unable to use it in Windows 10 and
my understanding is that problem started for others Canon scanner owners after a Windows 10 update. The update dropped support for Twain drivers
and now W10 will only allow WIA scanners.
Have any of you figured out a way around this problem?
TIA
PS. I already know that I can use NAPS2:
https://www.naps2.com/
It only allows me to scan one page at a time before it closes the module though.
It has likely received an error of some sort, which tossed it out
of a multi-page scan.
There seem to be some multi-page options. The project offers an SDK
for others to use, so perhaps not all these options are exposed in a
GUI on the main project.
https://github.com/cyanfish/naps2/issues/111
There is mention of a Batch Scan window.
https://github.com/cyanfish/naps2/issues/76
It seems to be written in C# (.cs) . The SDK has
logging, but only by adding a short routine manually
to the code.
OK, it has a Documentation page.
https://www.naps2.com/support
"NAPS2 works with Windows 7 SP1, 8, 8.1, 10, and 11.
On Windows 7 and earlier, you may need to install the .NET Framework 4.6.2 or later.
The last versions of NAPS2 that support Windows XP (SP3) are 6.1.2 and 5.8.2. "
You're supposed to be able to press the "Scan" button a second time, to
scan pages one-at-a-time. It would appear the module is not supposed to exit.
https://www.naps2.com/windows-scanning
If it is throwing errors, then the options here might not work properly.
https://www.naps2.com/doc/batch-scan
One source of blowing up, might be a .NET version bump.
Note that Microsoft is dealing with a driver exploit issue, and Windows Defender could also
be involved. Certain drivers have been blacklisted. I ran into a driver
I didn't even know was on the Insider disk I use, and this was related
to my Insider starting so many years ago, I had tried Asus Probe II or so
(on the Test Machine), when the machine was relatively new. Removing the program, did not happen to remove the driver it deposited at the time.
And that driver is exploitable somehow. This doesn't match your symptoms though, because only a "suspicious activity", the TWAIN driver accessing something it should not try to access, would get a Windows Defender response, and you would also get some sort of prompt (or even, damage). Driver blacklisting,
you would have received zero scans and no forward progress at all.
Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)