1. What actually happened or you saw:
Whe we run a file thats not recognized by CIS it gets sandboxed automaticly so we dont have much control over it, except if we open main cis gui, goes into sandbox and mark the files as trusted or not.
2. What you wanted to happen or see:
Add the option to NOT AUTOMATICLY SANDBOX unrecognized files.
3. Why you think it is desirable:
If we install a software thats not recognized by CIS it will be sandboxed by default. If this software installs child processes they will be automatic blocked or sandboxed by cis. This behavior is not good for production and usability. If we could mark the files as trusted before it gets sandboxed could be a pro for all users of CIS.
4. Any other information:
An example of the mentioned situation is with the game called “CrossFire”. When we try to install the game the installer will install “X-Trap” togheter. CIS will automaticly sandboxe the CrossFire executable and will do the same with X-Trap. Even if we click on “not sandbox it next time” for CrossFire executable, it will sandbox the X-Trap. With this sandboxed the game will open but errors will occour and the game will be terminated or will freeze. Some cases the game will crash and the user will have to reinstall it and then trust the x-trap executable and the x-trap .txt file used by the app itself. This is an example but this can be reproduced in a wider situations with softwares that are used for work, production, etc, like LightWorks. So please, consider the possibility of introducting the option to stop every unrecognized files but not sandbox these files automaticaly. Instead, give us the possibility of truste the files before they gets sandboxed or even before they run on system.