HIPS picks up wrong ruleset whch was copied from another ruleset frst [V6][M649]

A. THE BUG/ISSUE (Varies from issue to issue)
[ol]- Summary - Give a clear summary in the topic subject, NOT here.
HIPS picks up the wrong ruleset which was copied from another ruleset first.

  • Can U reproduce the problem & if so how reliably?:
    Yes. It happens every time.
  • If U can, exact steps to reproduce. If not, exactly what U did & what happened:
    The reproduce steps are :
    Steps of wrong result 1:
    Step 1. Create a ruleset named “RulesetA”.
    Step 2. Set rules copy from “Limited Application” first, then change them for needed.
    Step 3. Launch an unknown application.
    Step 4. Check “remember my answer”, when alert window popups,
    then click “Treat As” and choose “RulesetA”.
    Step 5. Check it in HIPS Rules.
    Step 6. “Limited Application” was applied. ( Not “RulesetA” !)
    Steps of wrong result 2:
    Step 1. Create a ruleset named “RulesetB”.
    Step 2. Set rules copy from “Isolated Application” first, then change them for needed.
    Step 3. Launch an unknown application.
    Step 4. Check “remember my answer”, when alert window popups,
    then click “Treat As” and choose “RulesetB”.
    Step 5. Check it in HIPS Rules.
    Step 6. “Isolated Application” was applied. ( Not “RulesetA” !)
    Steps of correct result :
    Step 1. create a ruleset named “RulesetC”.
    Step 2. Set all rules manually.
    Step 3. Launch an unknown application.
    Step 4. Check “remember my answer”, when alert window popups,
    then click “Treat As” and choose “RulesetC”.
    Step 5. Check it in HIPS Rules.
    Step 6. “RulesetC” was applied finally !
  • If not obvious, what U expected to happen:
    The ruleset which was selected in HIPS popup window should be pick up.
  • If a software compatibility problem have U tried the conflict FAQ?:
    It does not look like a software compatibility problem.
  • Any software except CIS/OS involved? If so - name, & exact version:
    No.
  • Any other information, eg your guess at the cause, how U tried to fix it etc:
    Guess : it is a(n) bug/issue of CIS.
    Try to fix it : Set all rules of ruleset manually.
    [/ol]

B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
[ol]- Exact CIS version & configuration:
6.3.294583.2937, Firewall

  • Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
    Firewall only, HIPS=safe, Firewall=Safe
  • Have U made any other changes to the default config? (egs here.):
    Uncheck : program auto updates, show desktop widget
    Check : alerts verbose mode
  • 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:
    Windows XP, SP3, 32bit, admin & limited, No virtual machine was used.
  • Other security/s’box software a) currently installed b) installed since OS:
    a = Avira Free Antivirus 13.0.0.4042 2013/08/30
    b = No
    [/ol]

[attachment deleted by admin]

Thank you for reporting this issue.

Please attach the diagnostics report and a list of the processes running on your computer to your first post. If you have any questions, or need any assistance, please feel free to ask.

Thanks.

PM reminder sent.

Sorry for the late.
I take some time to find out what the "diagnostics report" is, and how to get it.
I can't install Killswitch, so the "processes list" comes from ProcessExplorer(*), is that ok ?

(p.s For private reason, the computer name and user name have removed from the capture picture.)

* http://technet.microsoft.com/en-us/sysinternals/bb896653

That’s fine. All that was really needed was a list of the processes. I just mentioned KillSwitch specifically because it’s more likely that most users will have that on their systems.

No problem.

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 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.

Many thanks again.

The devs have informed me that they believe that this is fixed for CIS version 7.0.313494.4115. I will therefore move this to Resolved.

If this is still not fixed for you please both respond to this topic and send me a PM (including a link to this bug report).

Thank you.