Thanks for your great product, for some reasons after month of use i had to uninstall CIS …
i’m on windows 10, uninstalled cis using the defaullt windows uninstaller … rebooted … etc …
everything went fine …
now it seems that my connection still passing throught comodo firewall, using anothter firewall it always say : “COMODO ConnectV4” outgoing or “COMODO ConnectV6” outgoing
it seems that the comodo firewall interface is still here ! i"ve checked the registry all is clean, the lan adapter / interface properties are ok !
re-installed the re-removed … i also tryed to uninstall then reinstall the lan adapter … renew and flushed connections dns etc … , nothing to do…
I Suppose that CIS as modified a file that didn’t go to its original state after uninstalling …?
Please how do i remove this comodo interface from my connection ?
Thanks you per advance…
What other Firewall are you using? “COMODO ConnectV4” outgoing or “COMODO ConnectV6” outgoing do not ring an immediate bell. Do the alerts of the other firewall point to a specific application (cis.exe, cmdagent.exe, cavwp.exe, cmdvirth.exe …)?
I’m still investigating, i was able to reproduce the issue in a vm…
Perhaps a conflict between my firewall and the cis post uninstaller dunno really for now.
i’ve already done all steps discussed on your collegue’s thread and i’m pretty sure that there isn’t any trace left by cis :
registy seems clean, all folders programdata/ AppData /program files / program x86 etc… are clean, no geekbuddy/chromodo/av left
system32 seems ok too … that’s just weird to see my firewall tell me these comodo outgoings each time a connection is allowed.
i’m currently using my old frend firewall ‘windows10firewall from sphinx software’ wich is just a gui for the windows core firewall.
To be clear, my intention was to use the comodo antivirus that i like a lot and switch off the comodo firewall to continue using my old friend wich i know well.
but perhaps it’s have done some conflicts…
anyway, imo everything is clean … i’ve used process explorer, process monitor, autoruns etc also reinstalled my firewall… no trace about cis that’s just crazy something didn’t go back properly.
maybe the Windows Firewall wasn’t turned off properly as the Comodo Firewall was installed so the Windows Firewall made rules about the Comodo Firewall.
I don’t know the Windows Firewall (it’s the first thing I turn off after installing windows) but can you see any rules about Comodo?
Can you set the Windows Firewall back to default (flush all rules and start over again)?
When you go into “C:\ProgramData”, are there traces of Comodo (you have to turn hidden files ON to see that folder)?
Lord thanks for your comments… i had the same idea at first, so i’ve checked all rule from windows firewall, reseted to defaut and also removed all rules to test and nothing changed.
i also checked all rules form sphinx firewall into the software and into the windows registry nothing found.
yes i’ve enabled display of hiden files and also protected system files that’s the first thing i do and nothing from comodo is left.
strange isn’t it ?
to reply to you sphinx firewall didn’t show any alert for any cis executable. in fact it’s in the log file and also in the pop up balloon, that it tell me each time a connection is allowed:
“datetime dns/ip protocol processname |WindowsFirewall: COMODO ConnectV4 Outgoing| executablepath” even after uninstalling and re-installing sphinx firewall multiple times"
The behaviour is the same for any software/process that is allowed to go out, so logically chrome is not involved,
anyway, in de boubt, I’ve already tried that few days ago I’ve removed chrome and firefox then used ccleaner to clean registry.
next rebooted and downloaded a portable chrome that i’ve launched from my desktop.
and as expected this “comodo outgoing” still appear…
i"ve done some tries, by installing “private firewall 7” from privacyware, wich is also a powerfull firewall
and according to its log files everything seems fine.
At first i thought the comodo interface was still here, but after all, i’m pretty sure that this is a rules that was made
by windows firewall like you said previously, but impossible to put my hand on it.
Did you ever find out how to stop this? Microsoft forum told me it’s a Comodo problem and comodo tells us its a MS problem. So please for the love of God and all that is Holy, let me know if you found a solution. Did you have to go back to Windows 7? I am starting to hate Windows 10.