Recent Posts

Pages: [1] 2 3 ... 10
1
Bug Reports - CIS / Re: Comodo Firewall systray icon invisible [M2419]
« Last post by Lasse88 on Today at 02:41:05 PM »
It is listed in the "turn system icons on or off" i don't know about the other one, as the cis icon is in the tray atm..

but i tried to go to the Classic Notification Area Icons and turn off cis from the notification area, and when i turned it back on, the cis tray icon was still missing, it came back when i logged out and in again, as with the other times the cis tray icon is gone.
2
Thanks for testing!

Difference might be these:
- My R: is about 900MB and S: is only 128MB (and full according to Explorer)
- RAM disk utility, I use I-O DATA RAM Phantom EX
- Viruscope is enabled for all processes (not only contained one)
4
I have >400 blocked applications, all of which are in chinese (Kanji characters), I am unable to purge/remove or otherwise. I am using the latest release of CIS. Is there a way to remove these entries manually outside of the program or some other utility. I suspect the filename length & characters are causing an issue with the program when trying to Purge/Remove

Regards
Howie
5
I doubt it's anything to do with the Ram Drive in particular . . . .

Similar setup on a machine here:
Same OS version
Ram Drive R: at 2GB
All Temp / Tmp variables set to R:\Temp
FF, Opera & IE Explorer cache & Temp files all set to R
Print Spooler set to R

Only obvious difference is CIS 7036 running in a Modified Safe Mode on this one

Ok now I got an interesting one. Process Monitor shows cmdagent.exe is repeatedly trying to access R:, which is a RAM drive.
R: has environment variable TMP, TEMP and Internet Explorer cache directory.

Anyone anything rings a bell?
6
R: is writable, but I have another RAM drive S:, which is considered full by explorer. (I use NTFS compression so it indeed has some more spaces to use)
I disabled "USN journal logging" on S: via Everything (I don't know exact meaning of this, but I don't care as S: is just a temporal log drive) and CPU usage dropped instantly. :o

As for your question, it says "INVALID PARAMETER".

It seems high CPU usage is caused by some I/O problems, but S: is created just a few days ago (i.e. problem started before creation) so S: must not be a root cause. I'll keep an eye on this.
7
Just some wild guesses...

Is R: read-only perhaps?
How about set permissions on R: for System applications or CIS itself?
Maybe try to logon as admin and set admin permissions to R: to see if that lowers CPU load.


Looking at your Process Hacker screenshot, what's the full text of INVALID PAR... in the Result column?


8
Ok now I got an interesting one. Process Monitor shows cmdagent.exe is repeatedly trying to access R:, which is a RAM drive.
R: has environment variable TMP, TEMP and Internet Explorer cache directory.

Anyone anything rings a bell?
9
Thanks, I always use Process Hacker and have both tools on hand so I'll check I/O and other things when it returns.

IIRC there is no major I/O measured by Process Hacker when CPU usage is high, but tools you suggested (especially Process Monitor) might shed light on it.
10
You could use SysInternals' great tools "Process Explorer" and "Process Monitor" to try to figure out what causes cmdagent.exe high CPU load. Maybe cmdagent.exe is trying to read or access something on your system but something is preventing or blocking it from doing that. With the mentioned tools it would be possible to find out what cmdagent.exe during high CPU load is trying to do on your system. That information would very be helpful to know.
Pages: [1] 2 3 ... 10
Free Endpoint Protection
Seo4Smf 2.0 © SmfMod.Com Smf Destek