Menu

#948 Scanning Almost Always Fails on Windows 11 - Epson v600

6.X
open
nobody
None
6.1.2.25879
Support
Medium
TWAIN
2022-07-30
2022-07-29
dbareis
No

On Windows 10 I never had issues, on Windows 11 it almost always fails saying it can't communicate.

The only thing logged is:
2022-07-29 15:58:31.4298 TWAIN Transfer Error. Return code = Failure; condition code = OperationError; data = 0.

The logging needs improvement as the message shows more (and not less than the log):

To try to overcome this problem I installed the latest Epson drivers as some people said that it would fix this issue.

If I boot the computer, NAPS will work for a short while...

I can scan using "Paint.Net" (File->Aquire)

1 Attachments

Discussion

  • Christian Clavet

    For me the logging is good: it said that there is a communication error with the scanner, the problem lies in the data transfer process as no data was received.

    So if no data was received, windows is blocking something. Surely it have to do with Windows 11 security measures. You will need to investigate and find why Windows is blocking the communication with the application.

    There is something in Windows to allow an application to "passthru" and communicate.
    Perhaps the Paint.NET created a rule when installing the application. I don't know why this one work out of the box.

     
  • dbareis

    dbareis - 2022-07-30

    The log doesn't show the error code that is in the popup, if it doesn't mean anything it shouldn't be displayed, if it means something where do I look for it? Apart from that I'd like to suggest all error messages should be logged in "error.log"...

    I'm using BitDefender, I have turned it off, restarted NAPS 2 and it still fails.

    The Epson Scanner works also, so far it's only NAPS2 that fails to scan. Is it working for anyone on Windows 11? Your response suggests not.

    If I am to investigate for you I need to be told how to do that, what tools you use to investigate would be a good start.

     

    Last edit: dbareis 2022-07-30

Log in to post a comment.

MongoDB Logo MongoDB