I've been able to successfully get the ThinApp package to scan with our Fujitsu scanner. I've tested it with the Epic client, as well as the Fujitsu ScanDall application that is bundled with our scanners. I'm sorry for posting again, but I wanted to make sure that if anyone else ran into a similar problem, they would be able to find this resolution.
According to this article, a CLISD has to be added to the Wow6432Node in the registry to allow the ThinApp to see imaging devices, using the proper .dll files from C:\Windows\Syswow64 instead of C:\Windows\System32. The article doesn't explicitly state that this change needs to take place on the physical machine running the ThinApp (not the capture machine or the virtual registry of the package), but I figured that out after some testing. Of course, this raises the question of, "how do I go about making this change to every machine that launches this ThinApp, that also needs to scan?"
I answered that question in the following method.
- Open the HKEY_LOCAL_MACHINE.txt and add the following line to the bottom of the package, ensuring to leave a blank line above it.
isolation_merged HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{E5332A98-80FD-463C-80E4-A8E370752906} - Add the attached .vbs to the root of your ThinApp package. This script creates the needed registry values in the physical registry (since we previously made the isolation method merged) IF it's a 64-bit O/S and IF the keys don't already exist.
According to the kb article, the keys need to be added to HKEY_CLASSES_ROOT; however, there is not a HKCR.txt file for us to modify in the ThinApp package. Considering that HKCR\Wow6432Node is just a merged view of HKEY_LOCAL_MACHINE\Software\Wow6432Node\Classes and HKEY_CURRENT_USER\Software\Wow6432Node\Classes, I opted to use HKLM so that the change would be made for all users on the PC.
I hope this helps someone else, as it's been quite a battle for me over the past few weeks. Your mileage may vary, depending on the application and the scanner used.