awfull huge load of hdd by cmdagent.exe and cfp.exe

I have problem:

huge load of hdd.
used filemonitor and process monitor from winternals to check:
result:

  1. cmdagent.exe scan all disk for exe, dbg, jar etc files at background…
    and i dont command it scan disk…

one small problem: i have about 720 GB disk and alot of software…
so at result of this all time hdd is loaded

  1. cfp.exe all times opens C:\WINDOWS\system32\MSCTF.dll

16:08:21 cfp.exe:3444 OPEN C:\WINDOWS\system32\MSCTF.dll SUCCESS Options: Open Access: 00100020

again and again…
this file has only 240 kb, but it reads it all time…

  1. i have ISP free version

product version 5.10.228257.2253
virus signature database : 13061

Question:
How hdd reads can be decreased???

The resident shield will react to all sort of things that happen in the background. Do you have an indexer indexing files on your computer? That will have any AV scan a lot.

2) cfp.exe all times opens C:\WINDOWS\system32\MSCTF.dll

16:08:21 cfp.exe:3444 OPEN C:\WINDOWS\system32\MSCTF.dll SUCCESS Options: Open Access: 00100020

again and again…
this file has only 240 kb, but it reads it all time…

I am not a programmer or developer so I cannot comment on this.

3) i have ISP free version

product version 5.10.228257.2253
virus signature database : 13061

Question:
How hdd reads can be decreased???

Setting the AV to stateful is the only solution I can think of.

the DLL is associated with Text Services Framework - Wikipedia

I suspect because you are using CIS in a different language that is why it is accessing the dll.

Great question Eric regarding indexing. Personally, I turn indexing off. Some say that is improper due to performance issues, but I do it for the very reason you stated Eric, it sure adds a lot of scanning, etc. and use of resources after indexing is done. I also adjusted “Prefetch” options in registry to just fetch boot files and this has tamed the “Superfetch” service. Performance issues have not really been noticed at least for me.

Just a thought its123, as Eric mentioned about the indexing…a few months ago when I stopped this service, made a big difference in background activity. Disk reads will be reduced if indexing is turned off, and also as Eric mentioned, adjusting AV scanner to stateful. I use ‘on access’, but that is my choice. In your case, Stateful may be best in addition to stopping indexing.

Also, here is some info. regarding the file you mentioned:

Hope this helps in some way!
Jim

Hi, thanks for reply

  1. indexing service stopped, specailly stop this
  2. av scans all files that are possible executable, all of them are not started…
  3. AV set to “Stateful” mode

thanks, may be…

just question why it uses it all time, Comodo just sits at background… frontend closed…

I am not sure what you are trying to say. Could you rephrase?

2) av scans all files that are possible executable, all of them are not started.. 3) AV set to "Stateful" mode
Other than an indexer a defragmentation program could be a possible cause.

The Stateful mode only lasts for the Windows session. Each time you restart Windows the AV stateful scanner starts with a clean slate.

I thought its state was based on virus definition updates.

ok, fixed issue by:

  1. fully removing comodo internet security
    (after this computer begin live!!! difference at speed of load was 5-10 times for different tasks )

  2. and install comodo free antivirus from fresh

after this right now dont see hdd loads… so speed of work is normal

settings:

  • antivirus: state
  • defence:safe
  • sandbox - off ( i place it on by hand when need)

ps. previous version of comodo was installed about year before,and was only updated…
i think this was source of degrading of speed…

You’re right. My bad…

I don’t know, I reinstalled comodo to last version and I still get this message about MSCTF.dll, there is any solution? (I see threads dating as old as 5 years ago on this issue)

edit: I managed to “fix” this by a workaround adding it into hook exception of some sort, but it created more problems with other applications than I was willing to fix so in the meantime and until this bug gets sorted, I’ll be using Private Firewall, I hope Comodo gets back soon, because I like it.