cmdagent.exe comodo frequent high HD activity

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

Comodo has a bug with cmdagent.exe since one of the latest versions. I can’t exactly say since when - max 1/2 ~ rather just a few months.

Comodo has been uninstalled a few weeks ago because of this issue, freshly installed today again - problem resists.

20:43:24,4166962 cmdagent.exe 988 CreateFile C:\ SUCCESS Desired Access: Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: None, AllocationSize: n/a, Impersonating: Sven-PC64\Sven, OpenResult: Opened
20:43:24,4167678 cmdagent.exe 988 QueryNameInformationFile C:\ SUCCESS Name:
20:43:24,4167992 cmdagent.exe 988 QueryAttributeInformationVolume C:\ SUCCESS FileSystemAttributes: Case Preserved, Case Sensitive, Unicode, ACLs, Compression, Named Streams, EFS, Object IDs, Reparse Points, Sparse Files, Quotas, Transactions, 0x3c00000, MaximumComponentNameLength: 255, FileSystemName: NTFS
20:43:24,4168242 cmdagent.exe 988 CloseFile C:\ SUCCESS
20:43:24,4169034 cmdagent.exe 988 CreateFile D:\ SUCCESS Desired Access: Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: None, AllocationSize: n/a, Impersonating: Sven-PC64\Sven, OpenResult: Opened
20:43:24,4169392 cmdagent.exe 988 QueryNameInformationFile D:\ SUCCESS Name:
20:43:24,4169594 cmdagent.exe 988 QueryAttributeInformationVolume D:\ SUCCESS FileSystemAttributes: Case Preserved, Case Sensitive, Unicode, ACLs, Compression, Named Streams, EFS, Object IDs, Reparse Points, Sparse Files, Quotas, Transactions, 0x3c00000, MaximumComponentNameLength: 255, FileSystemName: NTFS
20:43:24,4169787 cmdagent.exe 988 CloseFile D:\ SUCCESS
20:43:24,4170410 cmdagent.exe 988 CreateFile E:\ SUCCESS Desired Access: Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: None, AllocationSize: n/a, Impersonating: Sven-PC64\Sven, OpenResult: Opened
20:43:24,4170733 cmdagent.exe 988 QueryNameInformationFile E:\ SUCCESS Name:
20:43:24,4170925 cmdagent.exe 988 QueryAttributeInformationVolume E:\ SUCCESS FileSystemAttributes: Case Preserved, Case Sensitive, Unicode, ACLs, Compression, Named Streams, EFS, Object IDs, Reparse Points, Sparse Files, Quotas, Transactions, 0x3c00000, MaximumComponentNameLength: 255, FileSystemName: NTFS
20:43:24,4171112 cmdagent.exe 988 CloseFile E:\ SUCCESS
20:43:24,4171778 cmdagent.exe 988 CreateFile G:\ SUCCESS Desired Access: Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: None, AllocationSize: n/a, Impersonating: Sven-PC64\Sven, OpenResult: Opened
20:43:24,4172088 cmdagent.exe 988 QueryNameInformationFile G:\ SUCCESS Name:
20:43:24,4172278 cmdagent.exe 988 QueryAttributeInformationVolume G:\ SUCCESS FileSystemAttributes: Case Preserved, Case Sensitive, Unicode, ACLs, Compression, Named Streams, EFS, Object IDs, Reparse Points, Sparse Files, Quotas, Transactions, 0x3c00000, MaximumComponentNameLength: 255, FileSystemName: NTFS
20:43:24,4172459 cmdagent.exe 988 CloseFile G:\ SUCCESS

loop @ 20:43:34

loop @ 20:43:39

no ending

I have 2 SSDs and 2 HDs. (C,D & E, G)

Windows7 64Bit

Comodo causes wearing on the SSDs, Comodo causes the HDs to ALWAYS SPIN. :-TD This software causes the entire operating system to fail in power saving as well as wearing life of the HDs.

I will uninstall Comodo again and hope for a fix. Otherwise I’ll just ask for an alternative.
All of my friends I’ve asked have the same problem and do not wish this to happen.

here is a screenshot:
http://www.abload.de/img/comodobug3uw2.jpg

Please give this thread a reply once the bug is fixed or at least that you are now aware of the problem.

#2

Did you have your partitions checked using the chkdsk /f command from the command prompt?

#3

We would very much appreciate it if you would edit your first post to create an issue report in line with the bug forum guidelines and format here. You can copy and paste the format from this topic.

To understand the reasons why we ask you to follow these guidelines please see below.

WHY WE ASK YOU TO FOLLOW THESE GUIDELINES
Bugs/issues can be impossible or very time consuming to fix if developers don’t have enough information to reproduce them. Since CIS is free, development time is limited. So if you want your issue fixed, please use the format below to describe it.

To avoid clutter, issues not described in the format below your post will not be moved to the ‘moderator verified’ issues topic. This means that the developers may not look at it.

Best wishes and many thanks in anticipation

Dennis

#4

We really would very much appreciate it if you would edit your first post to create an issue report in line with the bug forum guidelines and format. You can copy and paste the format from this topic.

Thank you

Dennis

#5

Unfortunately we do need this issue to be reported in the full right format, and with all the information we have asked for, if we are to forward it to verified issues.

For the moment I am going to move it to the Orphaned/Resolved child board. If you do edit your post to create a complete issue report in standard format, and PM an active mod, we will of course consider moving it to verified reports.

The devs only look at the Orphaned/Resolved board if they have time, so please do edit the post and PM an active mod if you want it fixed.

Dennis