I can confirm the behavior described by Reszjor and Naren, and append diagnostics and process list. The process list illustrates the behavior.
Could we have feedback please on whether this is intended?
B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
[ol]- Exact CIS version & configuration: 6.0 2708, IS config
Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV: All at default settings for config
Have U made any other changes to the default config? (egs here.): No
Have U updated (without uninstall) from a CIS 5?: No
[li]if so, have U tried a a clean reinstall - if not please do?:
[/li]- Have U imported a config from a previous version of CIS:No
[li]if so, have U tried a standard config - if not please do:
[/li]- OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used: Win 7 x64 SP1, UAC=off, Admin, Vmware Player
Other security/s’box software a) currently installed b) installed since OS: a=no b= no
[/ol]
Thank you very much for your report in standard format, with all information supplied. The care you have taken is much appreciated by Comodo, and will increase the likelihood that this bug can be fixed.
Developers may or may or may not communicate with you in the forum or by PM/IM, depending on time availability and need. Because you have supplied complete information they may be able to replicate and fix the bug without doing so.
Can you please check and see if this is fixed with the newest version? Please let us know whether it is fixed or you are still experiencing the problem.
I have received feedback from the devs that apparently this is normal behavior. If the option to detect installers is disabled it is not expected that trusted installers will work correctly.
That option is to run Unknown Installers not sandboxed i.e give popup when enabled & run sandboxed i.e automatically sandbox Unknown Installers when disabled.
So logically, either way it shouldn’t affect trusted installers as its for Unknown Installers only.
Devs are confusing us. If I remember correctly, Devs replied to Rejzor that it will be fixed in one of upcoming updates & now you got this feedback.
Rejzor have brought up this issue many times, sometimes he was little harsh & I understand the harshness.