Scanning with Epson L3250/L3256 fails at ≥300 DPI with HRESULT 0x800706BE in Scanner app

[mamadaevv]

Describe the bug
When using the Scanner app with an Epson L3250/L3256 Series device, scans fail with an error as soon as the resolution is set to 300 DPI or higher. The app shows a red error banner stating that scanning failed due to an unknown error, with an exception message like “Exception from HRESULT: 0x800706BE”. No image is produced and the page list remains empty.

To Reproduce

1. Open the “Scanner”.
2. Select the device “EPSON L3250 Series” as the scanner.​
3. Choose “Flatbed” as the source.
4. Set “Save as” to JPG (the same happens with other formats).​
5. Select any color mode (Color, Grayscale, or Monochrome).​
6. In the “Resolution” dropdown, select 300 DPI (for documents) or any higher available value.​
7. Click the “Scan” button.
8. Observe that the scan fails and a red error message appears at the bottom: scanning failed due to an unknown error, with “Exception from HRESULT: 0x800706BE”.​

Expected behavior
Scanning at 300 DPI and above should succeed without errors and produce a scanned page in the list, in the same way as at lower resolutions and as with the vendor tools for this device.

Screenshots
A screenshot from the Scanner app is attached, showing the selected “EPSON L3250 Series” device, 300 DPI resolution, and the error banner with the HRESULT 0x800706BE message.

Log data
No dedicated log files from the Scanner app are available on this system. The issue is reproducible every time with the steps above, even after reconnecting the device and restarting Windows.

Additional information / Feature request
The same physical device works correctly in WinScan2PDF when selecting the source “EPSON L3250 Series 6.7 (32-32)” or “WIA-EPSON L3250 Series 1.0 (32-32)”, including at 300 DPI and higher.​​
It would be very helpful if Scanner exposed an option to choose the scanner interface/driver explicitly (e.g., WIA vs vendor/TWAIN), so a working mode similar to WinScan2PDF can be selected when a specific interface causes errors.

[Magnetarman]

+1 Windows 24H2 is a disaster, constantly getting worse and has irreparably broken support for my Canon Lide 110 scanner via the WIA driver. Canon has obviously decided not to cooperate and not to change its codebase to fix the problem, so a perfectly working device becomes virtually useless. If it is possible to add support to the app to force the use of TWAIN instead of the main driver via WIA, that would be great.

In fact, when trying NAPS2, which allows this choice, the scanner magically came back to life even on Windows 11 24H2. Thank you so much for developing this fantastic app.