Forum Discussion
Trying to MSIX package LOB application that needs TWAIN access
We have some applications packaged with App-V where scanning stopped working after September 2025. Win11 24H2. It turned out that the September Win11 update was the culprit. Newer updates have the same error. Further troubleshooting with ProcessMonitor showed that if we added twain files from Win10 to the App-V packages, scanning worked again with our App-V packages.
I have previously not gotten scanning to work when I have packaged these applications as MSIX packages.
After I got scanning to work with the App-V package, I tried sequencing these again with the MSIX Packaging Tool. In the same way as with the App-V packages, I added the twain files from a Win10 computer and changed the AppXManifest.xml file.
Added section to AppXMainifest.xml
Success!
Now scanning works in our applications packaged as MSIX on Win10 and Win11 24H2 with the latest Microsoft update.
Let me clarify a bit. The only thing that is sequenced and that can be found in the MSIX package is the application itself and the 3 twain files from a Win10 machine. The scanner drivers are installed thick on the machines that use this MSIX package. The problem occurred on Win11 machines now that these received the September -2025 update and then scanning no longer worked. Solutions were to include the 3 twain files from a Win 10 machine in the MSIX package and change the appxmanifest file so that the application used these 3 files instead of the ones that are now found on the Win11 machines. Hope this can help you.
Thank Peer,
I will give that another go and see. I have a Win10 machine here that I can pull the files from. It would be a much more elegant solution.
