On my system the behavior initially reported remains the same.
The one reported on the video I posted on one of the initial posts:
I’ve red the release notes of the versions that have been released and nothing (publicly available) there explicitly relates/solves/addresses this issue.
And if there isn’t a direct post to the issue on this thread (or other related thread that i’m unaware), then I assume that this issue is still untouched/unsolved.
So, for me it is a surprise seeing that you notice some improvement.
Nevertheless for me any number above 5000 handles is a warning sign.
I can not reproduce this issue on 8.2.0.4703 I don’t have the AV installed but I enabled all other components of CIS (HIPS=Safe,Firewall=Safe,Auto-sandbox=Enabled,Viruscope=Enabled for all processes)and my peek handle count so far is 1,425 and I only have two open handles to HKLM\SYSTEM\ControlSet001\services\CmdAgent\CisConfig\1 whereas the video posted shows an increase of handle count to that registry key path.
Last time I checked it wasn’t fixed. (I’m not joking.)
This issue occurs on a PC that is on another home and it isn’t easily remotely accessible.
I’ll do what you ask probably next weekend.
Regarding the dead link I think I saved that zip on that PC. But its better to record the data again since the Comodo version has advanced since then.
I’ll upload the dumps from procdump as-well.
Meanwhile maybe wasgij6 still has the file?
It’s a beta version that you may test to verify if this issue is fixed with your system. Do note that you could wait for stable version.
Please check Comodo Internet Security CIS V10.0.0.5144 Beta !! for additional information.
More info:
I updated after downloading the EXE from the site.
Didn’t uninstall the version 8 before installing v10.
After installing the v10 imported the firewall definitions that exported previously of the v8.
I verified the leak happening before the import of the definitions.
And continues after the import.
‘cmdagent.exe’ process, I’m guessing. Come to think about it, while reading your older comments, using Windows Performance Toolkit might be a good idea for devs. Hmm!
Well I attached WinDbg and the PC became completely unresponsive. Did a reset of the PC and the rest was a complete mess…
So thoroughly detailing: 1- After reboot COMODO was corrupted.
The following image appears:
3- Thinking I was only being amazingly unlucky did the following: 3.1- Used IObit Uninstaller to do thorough uninstall of COMODO Internet Security, COMODO Essentials, COMODO Secure Shopping 3.2- Downloaded the COMODO installer, Installed, restarted when asked, updated definitions, was notified to install program updates :-TD on a SUPER fresh installation that is installed after the installer downloads what is installed from the site. 3.3- Fresh reboot after that not much understandable update and guess what… Corrupted again… :-TD
The following image appears: