WIA driver error 8021000b (WIA_ERROR_INVALID_COMMAND) "The device doesn't support this command"

[CJ-Wagner]

While requesting scanns from HP scan (or similar, eg NAPS2) system responds with error 8021000b (WIA_ERROR_INVALID_COMMAND) "The device doesn't support this command".

Even though the TWAIN driver works, only one (1) page is transmitted. But that is probably an other issue.

I have tried scanning from two different computers with different OS minor versions. Same scanner driver though.

Got to be the WIA driver from HP that is malfunctioning.

Scanning from an other HP PageWide Pro MFP 477dw works perfect from both tested computers. I assume it uses a different driver, given it worked before the MFP 586 was installed.

[Andcr]

Hello CJ-Wagner;

You can try different scanning apps like HP Scan and capture (found in Microsoft Store), HP Scan (part of full software solution driver found on HP website), HP Smart (MS store as well), Windows scanning software or even Universal Scan Driver. You can find that last option below your printer's drivers on the HP website

If your printer is still under warranty, you can call tech support for further help. 

[CJ-Wagner]

Well, that is all good, and that is exactly what has been tested. Different scanning applications, different windows-systems, universal scanner driver. It all comes down to the same problem: the WIA driver from HP.

To be clear, this error is related to the universal driver for HP PageWide Enterprise Color MFP 586.

The same systems with the same scanning applications works fine with a different HP PageWide Pro MFP 477, which has a different driver.

My theory, after dug in to the error message naps2 received (invalid command), it seems reasonable to believe that it is the WIA-driver that is the cause. HP Scan, MS scanning support, NAPS2, they all stop with the same error message, expressed in different forms (with a debugger one can extract that it is the same message the WIA driver exits with. Actually, it is Windows WIA system that delivers the error message to any Scanner application.)

This message, "invalid command" must have been issued by the scanning application and on behalf of the api windows connects the scanner-application to the WIA driver the conclusion is that is has to do with the WIA-driver. This is based on the facts that other scanner/driver works fine. The only thing that differs is the WIA-driver. The rest is the same. If the error would be caused by Windows, it would either be earlier in the process and made all scanners connecting to the WIA to fail, or later in the process where the scanner would have the issue, and therefor would not work at all, or at least not for windows. But it does.)

Now, the same systems and various scanner programs successfully delivers perfect scans from another HP PageWide 477 that has a different WIA driver. Works on different versions of Windows.

The same systems do deliver scans from the TWAIN-driver, but that makes sense, since it is a different approach and has different driver. Here, with the TWAIN-approach, there seems to be another problem with scanning, since only the first scanned image is delivered, regardless of used scanning application. But I am here going to remain with the WIA problem.

Scanning from Linux/NAPS2/Sane works fine. So there is no problem with neither scanner nor scanner applications.

Windows error? Doubtful, but possible.  See above.

How do we escalate this matter to whom that can confirm the error or point in a better direction?

/Carl

[CJ-Wagner]

What would be of some interest could be to try out the driver version that was included with the first shipping of the product. This version should at least be functional enough to produce enough functionality to prove the product working. I am not aware of old the printer is, but if it is older than Win 10 there may be other reasons for working/not working.

Maybe I should say the first driver version for Win 10.