What you did: Installed CBU Beta2 on production machine, and rebooted when requested
What actually happened or you actually saw: Rebooting after install, got appended error message saying command agent not started. Looked in Services and Cmdagent.exe was started. Used diagnostics, it said nothing wrong (file attached).
What you expected to happen or see: No error message, CIS starting normally
How you tried to fix it & what happened: Used system restore to restore to point well prior to CBU Beta installation, same error message occurred afterwards. Tried re-install of CIS (without uninstall) - this was unsuccessful: CIS.exe failed to invoke. Rebooted again, then CIS tried to invoke and crashed. Dump file attached.
If a software compatibility problem have you tried the compatibility fixes (link in format)? : Should not be compatibility issue as CBU is Comodo software
Details & exact version of any software (except CIS) involved (with download link unless malware): Comodo Backup 18.104.22.168 Beta 2
Whether you can make the problem happen again, and if so precise steps to make it happen: Not yet able to resolve it, so I cannot attempt replication.
Any other information (eg your guess regarding the cause, with reasons): Although preceded by Comodo Backup install, possibly not directly due to CBU software. More likely CBU install caused some form of one off interruption in normal CIS boot process, and this has resulted in corruption of some temp or cache file not restored by system restore.
B. FILES APPENDED. (Please zip unless screenshots).:
0. A diagnostics report file (Click ‘?’ in top right of main GUI) Required for all issues): Appended
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:: Appended
Screenshots illustrating the bug: Appended
Screenshots of related CIS event logs: Inaccessible
A CIS config report or file: Inaccessible
Crash or freeze dump file: Appended
Screenshot of More~About page. Can be used instead of typed product and AV database version: Not appended
C. YOUR SETUP:
CIS version, AV database version & configuration: CIS 6.0 Build 2674, Database version inaccessible, Internet security
a) Have you updated (without uninstall) from a previous version of CIS: No bare metal install using normal CIS 5.0 uninstaller then forced uninstaller tool
b) if so, have you tried a clean reinstall (without losing settings - if not please do)?: N/A
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
Have you made any other major changes to the default config? (eg ticked ‘block all unknown requests’, other egs here.): No
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.
I have experienced this is 2847. It appears to be a dynamic thin. IF cmdagent start is delayed for any reason CIS does not detect it when it tries to start. But restarting CIS will often mean it is detected.
I have not observed this specific bug in 7.0 4117, so it is rightly marked fixed in the tracker. There is another bug report for cmdagent not started errors without the CIS crash, so this can probably be safely retired. Best wishes. Mike.