When opening Toad from AppLocker in a highly locked down environment, Toad does not run.
There are no admin rights allowed on the machine, and other directories, like the regular Windows Temp folders are also completely restricted.
From the Windows event viewer, Toad creates the following file on startup: %OSDRIVE%\USERS\username\APPDATA\LOCAL\TEMP\TMPE30F.TMP
This temp file seems to be an executable .dll file which is prevented from execution in this environment, because execution rights are not granted to this path to Windows users.
This is not an issue with Toad, and is just caused by such a heavily restricted environment. The creation of the temp file is by design and is normal behaviour of many Windows applications.
WORKAROUND:
Allowing access to a temp directory, whitelisting a specific path, or running Toad under a different security context if possible.
STATUS:
Enhancement request TDB-4637 has been submitted to Development for consideration in a future release of Toad for DB2.
