Windows 10: Some Cowboy deleted my post about Windows 11 blocking Twain drivers and Fujitsu scanner

I'm having problems with Window 11 preventing my Fujitsu Fi-5530C from using Twain drivers. As in, it won't even install them.It's telling me that my scanner has the maximum page size of A3, but I have documents 490mm long.There must be a way to change the Windows 11 settings to override the Windows file that prevents Twain drivers from being used, and prevents the Fujitsu scanner from scanner longer than A3.But someone deleted my post, which suggests that they don't know, and don't have a clueNot impressed, and still need to stop Windows 11 from blocking Twain driversMarkBecause Twain driver

:)

 

Scanner Twain driver for Windows 11 - or how to make Windows 11 allow custom sized paper in scanner

I'm running Windows 11. I have a Fujitsu Fi-5530C document scanner.

I want to scan some wiring diagrams that are longer than A3. Paper size is around 297mm by 479mm.

Despite setting the custom paper to 479mm long, Windows is only letting the scanner scan to 420mm long.

I went into Windows settings, and changed the standard paper from A3 to Tabloid, which is 430mm. So now I can scan to 430mm long whilst the scanner software (NAPS2) is set to 479mm.

Whilst Windows sees the scanner, I'm convinced that it's not fully set up. The Fujitsu Fi-5530C is from around 2005 perhaps, and so program software is for Windows ME and 7.

I have read that if I change from WIA drivers to Twain drivers, then it will work ok. I've tried installing modern Fujitsu Twain drivers, but Windows is blocking that. When I use the NAPS2 scanner program and search for the scanner as a Twain scanner, the program can't see it.

So how do I get Windows 11 to accept and use Twain drivers. Or, how do I get WIA drivers to accept none standard paper sizes to scan?

Thanks

And also -

Why does Windows group Printers and Scanners together, but then stop support/instruction for installing stand alone scanners?

 

Windows 10 TWAIN drivers and GPO (.ds file)

Hello,



I was wondering if anyone run to this issue. We are having problems with installing drivers for Fujitsu scanners in our Windows 10 Enterprise environment. Looks like this might be related to our GPO policy but we can't pin point it. Here is the issue:



Just installed approved TWAIN drivers for fujitsu scanner (PaperStream IP) on Windows 10 device . After plugging the scanner to the USB port the system should detect and create a model specific .ds file in C:\Windows\twain_32\Fjicube - unfortunately nothing
happens.

• We already ruled out antivirus settings and permission settings.
• We did run ProcMon but unfortunately nothing happens after we plug in the scanner to the USB port. Just a note – the WIA drivers are installing correctly and we can see the scanner in Device Manager.
• The WIA, Shell Hardware detection and Remote Procedure Call (RPC) services are up and running
• We already tried local admin account – same issue

We moved our test Windows 10 device to “No GPO” AD group (no group policies applied), plugged the scanner into an USB, the system picked it up, created the model specific .ds file in C:\Windows\twain_32\Fjicube and now our TWAIN software is working as a
charm.



Any idea what can block this very specific procedure on windows 10?



Thanks

Marek

 

Renewed Scanner unable to obtain twain source

I'm running Windows 10 Pro 64 on PC. Do you also need full version? 1903 (OS Build 18362.476)

I read an old thread with suggestions and explanations, and a forum suggestion the thread was very old and I might start a new one.

I've had my Canon Lide 25 scanner running perfectly for years. The Canon Toolbox software was for Windows 7 and 32 bit but has run all along on my 64 bit installation without problems. I don't recall but I think I installed it to run in compatibility mode.

I know Windows has caused this. I read an article in their Hardware Dev Center on twain of them announcing in 2017 that they no longer ship twain data sources with Windows and saying they only accept WIA drivers for scanners. Full dropping could not be far behind.

This was working until days ago. Someone in the old thread found that rolling back updates got their scanner to work.

Before reading that depressing Microsoft news in the Hardware Dev Center, I tried updating the driver, setting the path to make sure it's located, disabling, enabling, re-installing, everything.

Can anyone help with this NOW?

After my attempted re-installation, in the events for the device properties there are three events all with the same timestamp. They seem to be in this order:
ID 430 from Kernel-PnP
Device USB\VID_04A9&PID_2220\5&2effdc72&0&10 requires further installation.
ID 20003 with task category 7005 from UserPnp
Driver Management has concluded the process to add Service usbscan for Device Instance ID USB\VID_04A9&PID_2220\5&2EFFDC72&0&10 with the following status: 0.
ID 20001 Task Category 7005 from UserPnp
Driver Management concluded the process to install driver cnql25.inf_amd64_c16af4b8fc1a4b7f for Device Instance ID USB\VID_04A9&PID_2220\5&2EFFDC72&0&10 with the following status: 0x0.

None of them are Errors or Warnings. They're all Information Level events.

I'm assuming the driver installed. Am I wrong?

When I unplug and plug the scanner I hear the USB connection chime. and the usual whirring sounds like the scanner is initializing.

But when I click to scan something, I get the immediate popup:





Please any help?

- - - Updated - - -

OK, I finally got it to work. I tracked down the file locations and found that I had gotten the path wrong (added a directory that didn't exist). When I fixed that, everything worked again. It's hard for me to definitively say that was the problem though, because I had changed no path before it stopped working. Maybe a Windows update did that, I don't know. I went through so many steps with nothing working. I still don't see the latest driver that I got from the Canon site. Its information had a file version of 11.0.1.1a and a date of 12/20/2011 but the one installed says 11.0.1.1 and 9/11/2006. That's not the one I just installed. But it's working, so if it ain't broke, don't fix it.