Why BlindScanner module is not visible for applications under Terminal sessions
In terminal sessions, Windows redefines the path to the Windows system folder, that is why it's necessary to make changes to the Windows registry
to make BlindScanner work correctly in terminal sessions.
Create a key named like the executable file of the host application in the registry nodes specified below.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\]
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\]
For instance, if you need to scan from Adobe PhotoShop, you need to create a key called PHOTOSHOP and create a Flags key with the following value:
Additional information on application execution management flags: http://support.microsoft.com/kb/186499
If you can't change application execution flags or the application is functioning incorrectly, copy the twain_32.dll file and the twain_32 folder to the personal Windows catalog of each user (C:\Users\<User_Name>\Windows).