Clean install after using the Comodo Uninstaller - everything is working well (Win10x64 1803 17134.254)
The the Unrecognised Files issue has gone
I have never had cmdagent.exe excessive CPU issues - but from what others have said, it may just appear now and again, so Ill keep a close eye on things
Killswitch still gives the the Corrupt File error but can be installed using the Test Server IP . . . . however this still screws up the Security Centre integration, necessitating a complete CIS re-install, but I will wait for the upgrade roll-out on the standard servers to see if that fixes it
Using the Beta Server IP in CIS, KillSwitch installs and works w/o a problem as long as the system is running
After a reboot however, the Protected instance of cmdagent.exe doesn’t start / and can’t be started, giving the old Security Centre error message of No Firewall
If i leave the AV service of Windows stopped and wait a few minutes, it gets auto-started. BUT also after a while it stops again. Probably Windows checks if the AV is stopped and starts it. And apparently Comodo stops it, but shouldn’t since i ONLY installed the FW !
Well I’ve tried everything . . . multiple reboots . . . cold starts . . . and I’m running a rather ‘complicated’ system here, but CIS is working flawlessly
Security Centre integration perfect and no errors anywhere