Purge files in HIPS crashes config window [M17]1[v6]

OS: Win7 x64
CIS: 2013

I can’t seem to be able to purge files anymore after upgrading to the new version. When I do it to the Firewall program rules it’s fine but when I purge the HIPS program rules the config just freezes for a bit then closes, without displaying any error. Config file attached.

[attachment deleted by admin]

I would be very much appreciate it if you could report this in standard format. The format is here.

Many thanks in anticipation

Mouse

Thanks very much for your issue report. We have moved it to the non-format bugs board for the moment, because too much of the information we normally need to replicate a problem and fix it is missing, or it is not in the format we request.

We realize some people may not have the time to do bug report in standard format, and therefore offer the option of a non-format report instead. But the problem is much more likely to be fixed promptly if you edit your first post to create an issue report which meets all criteria in the Checklist and Format. (You can copy and paste the format from this topic). The general reasons why are summarized in that post, the reasons we ask for specific pieces of information are given in this detailed post.

You can get your report moved to the format verified issues board simply by ensuring that it is correctly formatted and all criteria are met, and PM’ing a mod who is active on the bug board.

Best wishes

Mouse

Same problem happened. Do “purge” in “hips rules” will crash the CIS window, leaving an non-responding window which can only be killed by killswith

Please create a bug report for this, in the correct format, so we can pass it on to the devs.

Thank you.

TOPIC TITLE Selecting purge files in HIPS crashes or freezes config window


A. THE BUG/ISSUE:Purge files in HIPS crashes config window

  1. What you did:Open advanced settings in CIS clicked on HIPS rules then clicked purged
  2. What actually happened or you actually saw: HIPS rules configuration windows got frozen, now I cannot get in to CIS advanced settings at all,
  3. What you expected to happen or see: HIPS rules to get purged
  4. How you tried to fix it & what happened: able to kill the frozen menu with a killswitch than open advance settings click HIPS rules open and click purge but it gets frozen again,reinstall CIS, it helps for a while then it happens again
  5. If a software compatibility problem have you tried the compatibility fixes (link in format)?: no
  6. Details & exact version of any software (execpt CIS) involved (with download link unless malware):no
  7. Whether you can make the problem happen again, and if so precise steps to make it happen:unpredictable
  8. Any other information (eg your guess regarding the cause, with reasons):no

B. FILES APPENDED. (Please zip unless screenshots).:yes
0. A diagnostics report file (Click ‘?’ in top right of main GUI) Required for all issues):attaching, reports everithing is ok

  1. Screenshots of the 6.0 Killswitch Process Tab (see Advanced tasks ~ Watch Activity) or 5.x Active Process List. If accessible, required for all issues::attaching
  2. Screenshots illustrating the bug: attaching,
  3. Screenshots of related CIS event logs: attaching defense log
  4. A CIS config report or file:non
  5. Crash or freeze dump file:non
  6. Screenshot of More~About page. Can be used instead of typed product and AV database version:attaching

C. YOUR SETUP:

  1. CIS version, AV database version & configuration: proactive
  2. a) Have you updated (without uninstall) from a previous version of CIS:yes however the installation first installed the previous version
    b) if so, have you tried a clean reinstall (without losing settings - if not please do)?:yes just to be sure,
  3. a) Have you imported a config from a previous version of CIS:no,
    b) if so, have U tried a standard config (without losing settings - if not please do)?:
  4. Have you made any other major changes to the default config? (eg ticked ‘block all unknown requests’, other egs here.):no, but using proactive config,
  5. Defense+/HIPS, Autosandbox/BBlocker, Firewall & AV security levels:D+/HIPS=Safe, ASB/BB=Enabled, Firewall=Safe AV=Max,
  6. OS version, service pack, number of bits, UAC setting, & account type:windows 8 Pro 64 with media center, all updates, UAC + account=windows default
  7. Other security and utility software currently installed:nop,
  8. Other security software previously installed at any time since Windows was last installed:nop,
  9. Virtual machine used (Please do NOT use Virtual box)[color=blue]:nop,

[attachment deleted by admin]

Thank you very much for your bug report in standard format. We very much appreciate the effort you have made to document this bug.

We are sorry to trouble you further but there are some items of information missing or unclear in your post

There are quite a lot of things missing so please check through your report and add any missing information including appended files to your report.

The reasons we need these items of information, though they may not seem directly relevant to the issue are explained here.

We would be very grateful if you would add these items of information so we can forward this post to the format verified board, where it is more likely to get fixed. You can find assistance using red links in the Format and here. If you need further help please ask a mod. If you do not add the information after a week we will forward this post to the non-format board. If this happens we will tell you how to rectify this if you wish to.

In the current process we will normally leave it up to you whether you want to make a report which includes all necessary information or not. We may remind you if we think a bug of particular importance.

Many thanks again

Mouse

UPDATE!
For now I was able to get the purge in HIPS rules to work. Here is what I did . Disabled HIPS in the HIPS settings also disabled create rules for safe applications. Than restarted PC and in HIPS rules I 've removed couple applications. I am attaching pic of objects removed. Than re-enabled HIPS and create rules for the safe app. For now it is working. I will keep update you if any changes.

[attachment deleted by admin]

This suggests some form of deadly embrace, so I’ll forward to format verified.

Thanks for adding the info

Best wishes

Mouse

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.

Many thanks again

Mouse

The reason I don’t do this is because the bug report form is horrid! It is huge and takes a long time to complete for simply reporting an issue. I am not a QA tester and I am not bound to submit bug reports in a specific format! I can understand your need for info but PLEASE simplify your process! Here’s a formatted report:

A. The bug/issue

  1. What you did:

Clicked the Purge button in the HIPS Application Rules window.

  1. What actually happened or you actually saw:

The configuration window closes suddenly and does not save the settings.

  1. What you expected to happen or see:

A window containing the list of entries that are no longer valid should appear.

  1. How you tried to fix it & what happened:

No attempt. Cannot fix. Always happens.

  1. If its a software compatibility problem have you tried the compatibility fixes (link in format)?:

No. The config window just crashes silently.

  1. Details & exact version of any software (execpt CIS) involved (with download link unless malware):

http://imageshack.us/a/img849/5421/58921666.jpg

None.

  1. Whether you can make the problem happen again, and if so exact steps to make it happen:

-Open the CIS interface.
-Go to Open Advanced Settings.
-Load the configuration file provided in the first post and set it as active.
-Save the settings and open Advanced Settings again.
-Go to Defense+ → HIPS Settings → HIPS Rules.
-Right-click any entry and select Purge.

  1. Any other information (eg your guess regarding the cause, with reasons):

None.

B. Files appended. (Please zip unless screenshots).

  1. A diagnostics report file (Click ‘?’ in top right of main GUI) Required for all issues):

Config contained in the first post. The config GUI crashes silently, closing suddenly without producing any error.

  1. Screenshots of the 6.0 Killswitch Process Tab (see Advanced tasks ~ Watch Activity) or 5.x Active process list.

http://imageshack.us/a/img189/7915/56325989k.jpg
http://imageshack.us/a/img825/3401/17502679.jpg
http://imageshack.us/a/img705/7528/83925112.jpg

If accessible, required for all issues:

  1. Screenshots illustrating the bug:

Would you like me to upload a video of the bug to the entry in your bug database?

  1. Screenshots of related CIS event logs:

No events related to the bug.

  1. A CIS config report or file.

Included in first post.

  1. Crash or freeze dump file:

None available.

  1. Screenshot of More~About page. Can be used instead of typed product and AV database version.

6.0.260739.2674

C. Your set-up

  1. CIS version, AV database version & configuration used:

6.0.260739.2674, custom config

  1. a) Have you updated (without uninstall) from from a previous version of CIS:

Yes.

b) if so, have you tried a clean reinstall (without losing settings - if not please do)?:

No.

  1. a) Have you imported a config from a previous version of CIS:

Yes.

b) if so, have U tried a standard config (without losing settings - if not please do)?:

The whole point is to keep the current config! I did however try saving the config in v6 format, erasing it, and re-importing it.

  1. Have you made any other major changes to the default config? (eg ticked ‘block all unknown requests’, other egs here.):

The default configs do not appear to crash on purge.

  1. Defense+/HIPS, Autosandbox/BBlocker, Firewall & AV security levels: D+/HIPS= , ASB/BB= , Firewall = , AV =

HIPS: Safe Mode
Sandbox: Off
Firewall: Custom Ruleset
Antivirus: On

  1. OS version, service pack, number of bits, UAC setting, & account type:

Win7 SP1 64bit with UAC off and only 1 administrator account.

  1. Other security and utility software currently installed:

Avira Free.

  1. Other security software previously installed at any time since Windows was last installed:

Can’t recall.

  1. Virtual machine used (Please do NOT use Virtual box):

None.

Thanks for doing this anyway, much appreciated.

I agree and the format is somewhat simpler now.

We are talking to QA about automated data collection which will enable more simplification.

Best wishes

Mouse

I have good news and bad news with regards to the 2708 update. The good news is that now my D+ list properly purges and no longer crashes. The bad news is that the purge finds every single path where I used *s, displays them without the asterisk, and offers to delete them. The paths still have asterisks in the actual HIPS Rules list, just not in the purge window.

Thanks for the update. Very sorry this new problem has been introduced.

Could you please do a new report for this, as it is now a different bug. You can probably copy and paste most of the report from this one.

Best wishes and many thanks in anticipation

Mouse

Tracker updated with fix

It should be noted that this issue affects both HIPS and Firewall rules. If a rule looks like this “C:\Windows\Installer*”, the Purge function lists it as "C:\Windows\Installer" and offers to remove it. It would appear that the program no longer understands wildcards.

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.

Thank you.

PM sent.

Can you please check and see if this is fixed with the newest version (6.2.282872.2847)? Please let us know whether it is fixed or you are still experiencing the problem.

Thank you.

PM sent.

Actually, I just noticed that it appears that this is fixed.

Thus, I will move this to Resolved.