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.
Thank you for posting this information.
I will give it a go and see how it works out.
From memory, I was able to load the twain_32.dll library OK from an MSIX container, and it was able to scan the C:\windows\twain_32\ folder for scanner drivers, but when it loaded the scanner *.ds drivers from their subfolders, they were not able to initialize because when it tried to load their own dll dependencies, it could not locate them because the C:\windows\twain_32\MyScannerDriver\ folder wasn't part of the search path.
So ProcMon would show it looking for its dependencies in the VFS\windows\twain_32\MyScannerDriver\ location instead of C:\Windows\twain_32\MyScannerDriver\
