MJRegWatcher vs COMODO D+ crash

Comodo Internet Security - CIS Resolved/Outdated Issues - CIS
#1

(Sorry. i little know english. so i recorded the screen.)

MJRegWatcher is registry monitoring tool (Goodware)- Mark Jacobs' Free 32-bit Windows Software

Virustotal - VirusTotal

COMODO D+ Config

  1. Proactive Security (default, not edited).

  2. Treat unrecognized file as ‘Partially Limited’ ’ Limited’ ‘Restricted’ view Error

  3. ‘Untrusted’ ‘Blocked’ not view Error

  4. happen real PC and virtual PC environment.

[Video] MJRegWatcher vs COMODO D+ crash - - YouTube

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

A. The bug/issue

  1. What you did: after run RegWatcher.exe and continue re-run RegWatcher.exe, not stop.
  2. What actually happened or you actually saw: system down.
  3. What you expected to happen or see: sandboxed RegWatcher.exe or not execute RegWatcher.exe state
  4. How you tried to fix it & what happened: config Treat unrecognized file as ‘Untrusted’ ‘Blocked’ state. not execute RegWatcher.exe
  5. If its a software compatibility problem have you tried the compatibility fixes (link in format)?: N/A
  6. Details & exact version of any software (execpt CIS) involved (with download link unless malware): N/A
  7. Whether you can make the problem happen again, and if so exact steps to make it happen: See Video
  8. Any other information (eg your guess regarding the cause, with reasons): N/A

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

  1. Screenshots of the Defense plus Active Processes List (Required for all issues): N/A
  2. Screenshots illustrating the bug: See Video
  3. Screenshots of related CIS event logs: N/A
  4. A CIS config report or file: everything is default
  5. Crash or freeze dump file: N/A
  6. Screenshot of More~About page. Can be used instead of typed product and AV database version. See Video

C. Your set-up

  1. CIS version, AV database version & configuration used: v5.10.228257.2253 (Cloud scanning enable other AV settings are default)
  2. a) Have you updated (without uninstall) from from a previous version of CIS: No
    b) if so, have you tried a clean reinstall (without losing settings - if not please do)?: N/A
  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)?: N/A
  4. Have you made any other major changes to the default config? (eg ticked ‘block all unknown requests’, other egs here.): No
  5. Defense+, Sandbox, Firewall & AV security levels: COMODO - Proactive Security Config
  6. OS version, service pack, number of bits, UAC setting, & account type:
    Microsoft Windows XP Pro Edition 32-bit Sp3 (lasted version), Administrator
  7. Other security and utility software currently installed: None
  8. Other security software previously installed at any time since Windows was last installed: None
  9. Virtual machine used (Please do NOT use Virtual box): VirtualBox (v4.1.18 r78361)

[attachment deleted by admin]

#2

Thank you for your report in standard format.

Was this test run in a Virtual Box virtual machine? Unfortunately if it was then it will probably not be considered a bug by devs because CIS does not work with Virtual Box. You could try it in a Vmware VM instead, perhaps.

If it was not run in your virtual machine, please add to your bug report:

  1. Active process list from CIS ~ D+
  2. Your UAC setting
  3. Your D+, Firewall and AV security levels (The slider settings in each module)

Red links in the standard format explain these where appropriate.

Happy to help if you cannot understand any english explanations.

Best wishes

Mouse

#3

If it was not run in your virtual machine, please add to your bug report:

  1. Active process list from CIS ~ D+ : Windows default setting
  2. Your UAC setting : N/A (Windows XP)
  3. Your D+, Firewall and AV security levels (The slider settings in each module) - . CIS config is Proactive Security(Default).
#4

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